Skip to content
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

Open
guydou opened this issue Jun 29, 2017 · 19 comments
Open

when strting in HTTP mode, the service is not listening #83

guydou opened this issue Jun 29, 2017 · 19 comments

Comments

@guydou
Copy link

guydou commented Jun 29, 2017

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:

level=info msg="Make sure that HTTP requests for '/.well-known/acme-challenge' for all certificate domains are forwarded to the container running this application"

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:

 # netstat -lntu
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
#

thanks

@laoshancun
Copy link

same issue.

@failedguidedog
Copy link

+1

@jeffreyces
Copy link

Same issue.

@gpmeenen
Copy link

+1

1 similar comment
@protheusfr
Copy link

+1

@farzeni
Copy link

farzeni commented Sep 4, 2017

same here

@protheusfr
Copy link

Any fix planned ?

@mostlyjason
Copy link

+1

@paprickar
Copy link

+1
Issue also happen with rancher (v1.6.2) the template version is 0.5.0

@mfournier
Copy link

mfournier commented Oct 3, 2017

I'm not sure this is actually an issue. IME priori to the log message above, the service logs:
level=info msg="Using HTTP challenge: Sleeping for 120 seconds before requesting certificate".

After 120s, the port gets bound. About at the same moment this log line gets printed out: level=info msg="Trying to obtain SSL certificate ([...]) from Let's Encrypt Production CA".

Then once the chit-chat with letsencrypt's servers is over, the port gets closed again.

Seems like a reasonable behaviour to me.

@Yiivgeny
Copy link

+1

@laoshancun
Copy link

maybe you should upgrade to janeczku/rancher-letsencrypt:v0.5.0,it works fine for me.

@anderson012
Copy link

Issue also happen with rancher (v1.6.10) the template version is 0.5.0

@anderson012
Copy link

after updating the version I just needed to leave port 80 visible to the world and TADA, worked perfectly

@olivierb2
Copy link

olivierb2 commented Nov 7, 2017

+1
update : seems to work now, but not sure why.

@achih
Copy link

achih commented Nov 18, 2017

+1
rancher(v1.6.0)
rancher-letsencrypt:v0.5.0

@Geo719
Copy link

Geo719 commented Dec 3, 2017

+1
rancher (v1.6.12)
rancher-letsencrypt:v0.5.0

I updated rancher from 1.6.10 to .1.6.12 and it does not work anymore.

  • I recreated the LB with domain.tld 80 /.well-known/acme-challenge 80 rancher-letsencrypt
  • /etc/letsencrypt is on NFS mounted and working (files are mounted)

But only 503 on http://domain.tld/.well-known/acme-challenge
or
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...
It just started working?! Weird... I did nothing...?!

@defcon8
Copy link

defcon8 commented Jan 22, 2018

+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
Lets Encrypt: 0.5.0

@pdanysz
Copy link

pdanysz commented Feb 9, 2018

I have the same issue:
Racher: 1.6.14
Lets: 0.5.0

But is workaround for this.
I downgraded to 0.4.0 and works, my certs created successfully.

2/9/2018 6:37:40 PMlevel=info msg="Starting Let's Encrypt Certificate Manager v0.4.0 3c41d73"

2/9/2018 6:40:25 PMlevel=info msg="Certificate obtained successfully"
2/9/2018 6:40:26 PMlevel=info msg="Updated Rancher certificate 'SSL Certs'"
2/9/2018 6:40:28 PMlevel=info msg="Updated load balancer 'DC-LoadBalancer' with changed certificate"
2/9/2018 6:40:28 PMlevel=info msg="Certificate renewal scheduled for 2018/04/20 12:00 UTC"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests