-
Notifications
You must be signed in to change notification settings - Fork 4
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
Acme server clashes with redirect server on port 80 #284
Comments
Actually, this seems to work on acme staging, but for some reason fails on acme prod. |
Actually, I think the issue is that we are starting two servers at port 80
So, the acme CA is only able to access the acme server once in a while. And the other time it gets access to the redirect server. |
- Use one server to handle ACME challenge requests and normal application requests. Prior to this, we had an app server and an ACME server that were both listening on the same port. This used to cause the two to clash since requests for one might end up been handled by http handlers for the other. - Fixes: #284
I think it is because letsencrypt does not issue wildcards using
http-01
challengeong/server/tls_conf.go
Lines 185 to 187 in a8fba42
The text was updated successfully, but these errors were encountered: