I have some domain certs that are signed by letsencrypt. My server was very old and and I had to run not just certbot-auto but an old version of it. Lately that has been failing as unsupported. But luckily and surprisingly my certificates seem to be renewed and will last till April.
I've just moved the server over for these domains, and copied the old /etc/letsencrypt to the new server. Going to the sites in their new location gives me a nice padlock and "Verified by: Let's Encrypt" as on the old server.
Now I have a recent OS I can run certbot. I installed it from the Debian repository and am aware of your warnings about version compatibility. I'll go to snaps if I must, but prefer use the latest Debian package while it seems to work.
But, it isn't working!
Running "certbot renew --dry-run" gives
Attempting to renew cert (www.notjustcamden.uk) from /etc/letsencrypt/renewal/www.notjustcamden.uk.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6.. Skipping.
I see that /etc/letsencrypt/accounts/acme-staging.api.letsencrypt.org/directory/113ab11b4babf5d10bbb556f82c79ae5/meta.json
contains a ref to the old server domain in the creation_host key and I wonder if this is the reason. Clearly this is not an editable file and any change to the server domain must be done elsewhere.
So my question is, what is the format of the certbot command I should cron to check for auto-renewal, and do I need to reconfigure anything to make it work?
Sorry if this has been asked before, I couldn't find a match in the help forum.
Thanks in advance!