You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just se tup a new rancher deployment, and Am currently trying to ge this letsencrypt stack working.
I simply added from the catalog, filled in the details (I'm using DNSimple) and launched. The service keeps restarting, and by using the docker logs command, I see the following lines, repeated over and over:
level=info msg="Starting Let's Encrypt Certificate Manager v0.2.7 5dbb48c"
level=info msg="Using locally stored Let's Encrypt account for opb@redacted.com"
level=info msg="Trying to obtain SSL certificate for myhost.mydomain.uk"
level=error msg="[myhost.mydomain.uk] Error obtaining certificate: Error presenting token dns: domain must be fully qualified"
I was using a real domain which is already set up in DNSimple, but have obviously swapped it out for a placeholder there.
Any suggestions would be appreciated, thanks!
The text was updated successfully, but these errors were encountered:
Hi, thanks for this report.
The error is due to a bug in the upstream ACME library. I just submitted a patch and as soon as that gets merged i will push a new image for Rancher. go-acme/lego#193
@opb If you wanna give it a try before this makes it into the community catalog:
Clone or upgrade the letsencrypt service in Rancher and change the image to: janeczku/rancher-letsencrypt:v0.2.8
Hi there
I've just se tup a new rancher deployment, and Am currently trying to ge this letsencrypt stack working.
I simply added from the catalog, filled in the details (I'm using DNSimple) and launched. The service keeps restarting, and by using the
docker logs
command, I see the following lines, repeated over and over:I was using a real domain which is already set up in DNSimple, but have obviously swapped it out for a placeholder there.
Any suggestions would be appreciated, thanks!
The text was updated successfully, but these errors were encountered: