-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Can not retrieve terms of service from certificate authority #29
Comments
Me too, I want to know how to solve it. @stieuquy @Valian |
refs: patch: try it. |
@otolab thank you Solved my problem |
Actually new Dehydrated must be included, which is already part of |
I will look at this and update the image soon, when I'll find some spare time. Sorry for delay! |
Any idea when this will get fixed? @Valian |
Hi @Valian, I had an immediate requirement to setup https on reverse proxies, and had to go with a different solution. I tried building the Docker image myself from the patch commented above, but still ran into errors. For anyone else who is a DevOps noob like myself, I found that configuring Traefik Reverse Proxy was really easy. It has support for Letsencrpyt (not as seemless as this image but not very hard either). This is the blog post I referred to for setting Traefik up : https://timonweb.com/tutorials/an-example-of-docker-compose-and-traefik-config-domain-name-ssl-certificate/ I like this package more and am patiently waiting for you to rebuild this image. Thanks |
@stieuquy @shivekkhurana @elertan I've updated lua-resty-auto-ssl package version in #31 and tested it on some of my websites. I think it should be fixed now, but please confirm. Also, I've started to properly tag image releases, this has tag 1.0.0 because this image seems to be already pretty stable. So, to test everything, try to use either tag Just to be sure, the previous image (before #31 was merged) is available as |
Thanks @Valian. I tested |
Hi everybody,
I got error to generate certs

Has anyone got this error before?
My docker-compose is same as the sample in your document.
Thanks for help!
The text was updated successfully, but these errors were encountered: