I’ve been using Let’s Encrypt for almost a year and it’s fantastic - so well done to all involved. I recently dockerized everything, and everything appears to be working very well except for a small issue I’m having around using certbot to renew my certificates. The certbot renewal request went th…

Please show: ls -l /etc/letsencrypt/live/ certbot certificates

[image] thecarlo: The certbot renewal request went through, but it keeps saving the renewed certificates to a new folder with -0001 appended to my domain : /etc/letsencrypt/live/humankode.com-0001 Hi @thecarlo , The intended way to renew your certificates is just certbot renew (ideally twice …

still waiting for the certbot certificates in the interim, take a look at: https://crt.sh/?q=humankode.com which seems to indicate that your “renewal” process is actually issuing new certs… also why use “certonly” ?

[image] schoen: The intended way to renew your certificates is just certbot renew Hi @schoen , I ran the certbot renew command: sudo docker run --rm -it --name certbot \ -v "/docker-volumes/etc/letsencrypt:/etc/letsencrypt" \ -v "/docker-volumes/var/lib/letsencrypt:/var/lib/letsencrypt" \ -…

Start with this: certbot certificates

Also you’re issuing a lot of certificates. Keep the rate limits in mind and use the staging environment to experiment (certbot --staging and certbot renew --dry-run). https://crt.sh/?q=%humankode.com https://letsencrypt.org/docs/rate-limits/ https://letsencrypt.org/docs/staging-environment/

[image] rg305: Start with this: certbot certificates I deleted all the -0001 subfolders and artifacts. ls -la /docker-volumes/etc/letsencrypt/live/humankode.com returns drwxr-xr-x 2 root root 4096 Dec 23 20:07 . drwxr-xr-x 3 root root 4096 Jan 6 05:38 .. -rw-r--r-- 1 root root 1818 Dec…

Ok, I managed to solve the issue. Thanks for all the input. I found the root of the problem. When I initially created the certificate, I used a non-official docker certbot image to issue the initial certificates. I used deliverous/certbot instead of the certbot/certbot image. Then, when I tried t…

Certbot renew request saves certificates to -0001 to folder

Help

Topic		Replies	Views
Lets encrypt generating -0001 and -0002 folders when renewing certificates Help	9	1217	April 7, 2024
Handling scheduled renewals when /etc/letsencrypt/ folder is not available? Help	12	2905	April 27, 2018
Letsencrypt-auto always create a new folder for cert renewal Help	5	2551	December 30, 2019
New folders were created when renewing wildcard certs Help	8	1041	April 5, 2022
Prevent -0001 -xxxx Certificate Suffixes Help	3	8054	July 16, 2018

Certbot renew request saves certificates to -0001 to folder

Related topics