Let's Encrypt certificate
See original GitHub issueI am looking at the Let’s Encrypt implementation.
Should we generate a new certificate every time the container is booted? Because validating /etc/letsencrypt/live/$LETSNECRYPT_DOMAIN/fullchain.pem
will fail, since the container will not keep files that are not in volumes, after the container is shut down.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Let's Encrypt
Let's Encrypt is a free, automated, and open certificate authority brought to you by the nonprofit Internet Security Research Group (ISRG). 548 Market...
Read more >Let's Encrypt - Wikipedia
Let's Encrypt is a non-profit certificate authority run by Internet Security Research Group (ISRG) that provides X.509 certificates for Transport Layer ...
Read more >Let's Encrypt SSL certificate overview
Let's Encrypt is a new Certificate Authority (CA) that offers FREE SSL certificates that are just as secure as paid certificates. This project ......
Read more >Install Let's Encrypt to Create SSL Certificates - Linode
Let's Encrypt is an SSL certificate authority managed by the Internet Security Research Group (ISRG). It utilizes the Automated Certificate ...
Read more >How to Install Let's Encrypt SSL Certificate - Cloudways Support
A step-by-step guide on how you can Install the Let's Encrypt SSL certificate [with video tutorial].
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey,
I run into the same issue again because of testing. The reason is based on the docu, which says: “IMPORTANT: At the moment, configuration is not regenerated on every container boot, so if you make any changes to your .env file, make sure you remove the configuration directory before starting your containers again”. See https://github.com/jitsi/docker-jitsi-meet#configuration
Please update the docu, to watch out for the certificate. So it wont be deleted if necessary.
Thx
Cheers
dennis
For anyone finding this in the future, LE say that there’s no way to clear the status of your domain-set until the 7 days “sliding window” has elapsed, regardless of how you spell, or arrange the domains in the
certbot
command. However, if like me, you have a spare domain kicking around that you haven’t yet added to the cert, add that and re-run the command. This worked for me.