Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: www.waltr.net (Ipv4) www.waltr.org (ipv6)
I ran this command: certbot renew
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /usr/local/etc/letsencrypt/renewal/www.waltr.net-0001.conf
Certificate not yet due for renewal
The following certificates are not due for renewal yet:
/usr/local/etc/letsencrypt/live/www.waltr.net-0001/fullchain.pem expires on 2022-03-26 (skipped)
No renewals were attempted.
My web server is (include version): apache 2.4.51 (FreeBSD 12.2-Release-p7 )
The operating system my web server runs on is (include version): FreeBSD 12.2-Release-p7
My hosting provider, if applicable, is: myself. privately owned.
I can login to a root shell on my machine (yes or no, or I don't know): yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): NO
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot): certbot 1.18.0
Additional Details:
I upgraded the server to FreeBSD release 12 not long ago. I have been having chronic issues with certbot/certificates. During the upgrade I may have messed something up in the lets encrypt system.
Here are the directory structures:
tree
.
|-- DUMMY
| |-- www.waltr.net.conf
| `-- www.waltr.org.conf
|-- accounts [error opening dir]
|-- archive [error opening dir]
|-- csr
| |-- 0000_csr-certbot.pem
| |-- 0001_csr-certbot.pem
| |-- 0002_csr-certbot.pem
| |-- 0003_csr-certbot.pem
| |-- 0004_csr-certbot.pem
| |-- 0005_csr-certbot.pem
| |-- 0006_csr . . .
. . .
| |-- 1802_csr-certbot.pem
| |-- 1803_csr-certbot.pem
| `-- 1804_csr-certbot.pem
. . .
|-- live
| |-- README
| |-- ipv4.waltr.org
| | |-- README
| | |-- cert.pem -> ../../archive/ipv4.waltr.org/cert15.pem
| | |-- chain.pem -> ../../archive/ipv4.waltr.org/chain15.pem
| | |-- fullchain.pem -> ../../archive/ipv4.waltr.org/fullchain15.pem
| | `-- privkey.pem -> ../../archive/ipv4.waltr.org/privkey15.pem
| |-- waltr.net
| | |-- cert.pem -> ../../archive/waltr.net/cert25.pem
| | |-- chain.pem -> ../../archive/waltr.net/chain25.pem
| | |-- fullchain.pem -> ../../archive/waltr.net/fullchain25.pem
| | `-- privkey.pem -> ../../archive/waltr.net/privkey25.pem
| |-- www.waltr.net
| | |-- cert.pem -> ../../archive/www.waltr.net/cert24.pem
| | |-- chain.pem -> ../../archive/www.waltr.net/chain24.pem
| | |-- fullchain.pem -> ../../archive/www.waltr.net/fullchain24.pem
| | `-- privkey.pem -> ../../archive/www.waltr.net/privkey24.pem
| |-- www.waltr.net-0001
| | |-- README
| | |-- cert.pem -> ../../archive/www.waltr.net-0001/cert1.pem
| | |-- chain.pem -> ../../archive/www.waltr.net-0001/chain1.pem
| | |-- fullchain.pem -> ../../archive/www.waltr.net-0001/fullchain1.pem
| | `-- privkey.pem -> ../../archive/www.waltr.net-0001/privkey1.pem
| |-- www.waltr.net-0002
| | |-- README
| | |-- cert.pem -> ../../archive/www.waltr.net-0002/cert2.pem
| | |-- chain.pem -> ../../archive/www.waltr.net-0002/chain2.pem
| | |-- fullchain.pem -> ../../archive/www.waltr.net-0002/fullchain2.pem
| | `-- privkey.pem -> ../../archive/www.waltr.net-0002/privkey2.pem
| `-- www.waltr.org
| |-- README
| |-- cert.pem -> ../../archive/www.waltr.org/cert10.pem
| |-- chain.pem -> ../../archive/www.waltr.org/chain10.pem
| |-- fullchain.pem -> ../../archive/www.waltr.org/fullchain10.pem
| `-- privkey.pem -> ../../archive/www.waltr.org/privkey10.pem
|-- options-ssl-apache.conf
|-- renewal
| `-- www.waltr.net-0001.conf
`-- renewal-hooks
|-- deploy
|-- post
`-- pre
35 directories, 3964 files
httpd.conf points the SSLCertificate file to ....letsencrypt/live/... and this is consistent.
After the upgrade, certbot began complaining and started making -0001 -0002 etc.
Any ideas on how I can clean this up and get things working right?
Thanks.