search

DanielDent / docker-nginx-ssl-proxy

SSL Front-End Proxy With Automatic Free Certificate Management
https://hub.docker.com/r/danieldent/nginx-ssl-proxy/
Other
204 stars 68 forks source link

Error: simp_le #1

Closed R0GGER closed 7 years ago

R0GGER commented 7 years ago

Running this docker-image I get this error... How can I agree to a the subscriber?

Nginx has arrived.                                                                                                                    
2016-11-21 16:27:19,607:INFO:requests.packages.urllib3.connectionpool:805: Starting new HTTPS connection (1): acme-v01.api.letsencrypt
.org                                                                                                                                  
2016-11-21 16:27:19,837:INFO:requests.packages.urllib3.connectionpool:805: Starting new HTTPS connection (1): acme-v01.api.letsencrypt
.org                                                                                                                                  
2016-11-21 16:27:20,115:INFO:requests.packages.urllib3.connectionpool:805: Starting new HTTPS connection (1): acme-v01.api.letsencrypt
.org                                                                                                                                  
2016-11-21 16:27:20,415:INFO:requests.packages.urllib3.connectionpool:805: Starting new HTTPS connection (1): acme-v01.api.letsencrypt
.org                                                                                                                                  
2016-11-21 16:27:20,645:ERROR:simp_le:879: ACME server returned an error: urn:acme:error:unauthorized :: The client lacks sufficient a
uthorization :: Must agree to subscriber agreement before any further actions.
DanielDent commented 7 years ago

Hi, updated simp_le and fixed this issue in 49adfa416c37d05cfeed7a49b448c74b2919ed56. I've created a TOS_HASH with a default value that works at the moment. If Let's Encrypt updates their ToS, this image will need to be updated and/or users will need to pass the TOS_HASH variable with the current hash of the let's encrypt subscriber agreement.