-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when strting in HTTP mode, the service is not listening #83
Comments
same issue. |
+1 |
Same issue. |
+1 |
1 similar comment
+1 |
same here |
Any fix planned ? |
+1 |
+1 |
I'm not sure this is actually an issue. IME priori to the log message above, the service logs: After 120s, the port gets bound. About at the same moment this log line gets printed out: Then once the chit-chat with letsencrypt's servers is over, the port gets closed again. Seems like a reasonable behaviour to me. |
+1 |
maybe you should upgrade to |
Issue also happen with rancher (v1.6.10) the template version is 0.5.0 |
after updating the version I just needed to leave port 80 visible to the world and TADA, worked perfectly |
+1 |
+1 |
+1 I updated rancher from 1.6.10 to .1.6.12 and it does not work anymore.
But only 503 on http://domain.tld/.well-known/acme-challenge LOG: Error obtaining certificate: acme: Error 400 - urn:acme:error:connection - Fetching http://<domain.tld>/.well-known/acme-challenge/Rk_Zo0-TQsVZhFysd16Is8--oK__I9jcgyx634kyvjE: Connection refused any suggestions? !Confused... |
+1 !! /.well-known/acme-challenge, does not get routed properly by the load balancer. When accessing the URL manualy from a webbrowser, the original balancer rule beneith is applied. Rancher: 1.6.14 |
I have the same issue: But is workaround for this. 2/9/2018 6:37:40 PMlevel=info msg="Starting Let's Encrypt Certificate Manager v0.4.0 3c41d73" |
I started the service in a rancher (v1.6.2) the template version is 0.4.0
I configured it with HTTP mode
The service starts and prints:
I tried to see if it listens on that port,
so I exec to that container and I saw it doesn't listen on any port:
thanks
The text was updated successfully, but these errors were encountered: