The new SSH certificate from LetsEncrypt renew had been running for over year.
Last January, when I renew, it failed so I had to reissue.
Now somehow it created a key under datacook.org-0001. I thought it has been working. and renew worked but from Apr 5th still the site saying the datacook.org has expired.
Here is the output.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - new certificate deployed without reload, fullchain is /etc/letsencrypt/live/www.datacook.org/fullchain.pem - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Congratulations, all renewals succeeded. The following certs have been renewed: /etc/letsencrypt/live/datacook.org-0001/fullchain.pem (success) /etc/letsencrypt/live/www.datacook.org/fullchain.pem (success) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
Certificate Name: datacook.org-0001
Domains: [datacook.org](http://datacook.org/)
Expiry Date: 2022-07-07 16:19:10+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/datacook.org-0001/fullchain.pem
Private Key Path: /etc/letsencrypt/live/datacook.org-0001/privkey.pem Certificate Name: [www.datacook.org](http://www.datacook.org/)
Domains: [www.datacook.org](http://www.datacook.org/)
Expiry Date: 2022-07-07 16:19:20+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/[www.datacook.org/fullchain.pem](http://www.datacook.org/fullchain.pem)
Private Key Path: /etc/letsencrypt/live/[www.datacook.org/privkey.pem](http://www.datacook.org/privkey.pem)
My domain is: datacook.org
I ran this command: certbot renew
It produced this output:
My web server is (include version): datacook.org
The operating system my web server runs on is (include version): ubuntu
My hosting provider, if applicable, is: AWS EC2
I can login to a root shell on my machine (yes or no, or I don't know): YES
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot --version
certbot 0.31.0
I wonder why it created -0001 certificate.
and it doesn't recognized the renewal.