Done.
Deleted (rm -rf ) the subfolders, did the dry-run first which was successful. Then the actual certificate creation.
Output:
Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/grembeirn.duckdns.org/fullchain.pem
Key is saved at: /etc/letsencrypt/live/grembeirn.duckdns.org/privkey.pem
This certificate expires on 2024-06-11.
These files will be updated when the certificate renews.
When checking the certificates, I now get:
sudo certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Python 3.7 support will be dropped in the next planned release of Certbot - please upgrade your Python version.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
Certificate Name: grembeirn.duckdns.org
Serial Number: some number
Key Type: ECDSA
Domains: grembeirn.duckdns.org
Expiry Date: 2024-06-11 22:21:51+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/grembeirn.duckdns.org/fullchain.pem
Private Key Path: /etc/letsencrypt/live/grembeirn.duckdns.org/privkey.pem
Guess next step now is to make sure my update script works fine:
sudo /opt/certbot/bin/certbot renew --dns-duckdns-credentials /etc/letsencrypt/renewal/grembeirn.duckdns.org.conf
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Python 3.7 support will be dropped in the next planned release of Certbot - please upgrade your Python version.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/grembeirn.duckdns.org.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Certificate not yet due for renewal
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
The following certificates are not due for renewal yet:
/etc/letsencrypt/live/grembeirn.duckdns.org/fullchain.pem expires on 2024-06-11 (skipped)
No renewals were attempted.
Which was the output I was expecting.
It looks like I'm out of the woods for now. No?