-
Notifications
You must be signed in to change notification settings - Fork 183
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
FYI #2
Comments
Hi, Same problem, sample doesn't work with latest No error on nginx logs, just 200/304 HTTP code. However problem also wasn't solved by changing image to |
It (eventually) worked for me on a new server using the latest images. It took more than 5 minutes (in addition to the initial DH generation) to generate the certificates. Part of that delay was about 2 minutes for each service to get to an error like
even though I was actually able to manually load that URL during that time. Others are seeing the same issue: nginx-proxy/acme-companion#209 After these errors though the certificates got created anyway. |
I suspect that something wrong with nginx.tmpl. But no idea how to debug, asked on stack, but no one reply for now. I found in logs such string:
My docker-compose file:
|
There's a problem with the latest version of jrcs/letsencrypt-nginx-proxy-companion so I used the one that I assumed you would have used 4 months ago based on your commit (v1.4) to get your examples working. They worked!
All I had to do was change the image to:
jrcs/letsencrypt-nginx-proxy-companion:v1.4
The text was updated successfully, but these errors were encountered: