Letsencrypt renewal has failed since recentlly upgrading ISPOCOnfig and ubuntu, and /var/log/letsencrypt/letsencrypt.log shows sundry failures including: '2024-10-19 20:43:01,902:ERROR:certbot._internal.renewal:Renewal configuration file /etc/letsencrypt/renewal/XXXXX.org.conf is broken. 2024-10-19 20:43:01,903:ERROR:certbot._internal.renewal:The error was: renewal config file {} is missing a required file reference' and ' Traceback (most recent call last): File "/snap/certbot/3834/lib/python3.8/site-packages/certbot/_internal/renewal.py", line 76, in reconstitute renewal_candidate = storage.RenewableCert(full_path, config) 'File "/snap/certbot/3834/lib/python3.8/site-packages/certbot/_internal/storage.py", line 489, in __init__ raise errors.CertStorageError(certbot.errors.CertStorageError: renewal config file {} is missing a required file reference' Elsewhere in log seems to be referring to acme.. '2024-10-19 15:39:00,679EBUG:acme.client:Sending POST request to https://acme-v02.api.letsencrypt.org/acme/new-order:' The website that is currently shown as not having its letsencrypt cert renewed since 13 Oct does not appear in the letsencrypt log. I've tried turning letsencrypt on and off in ISPconfig for that website and it behaves normally. I'm stuck as to what to do.
I've managed to resolve several of the issues (they were due to errors in DNS records after change of network provider. I'm left with two unresolved sudo certbot renew --dry-run fails two sites with the message ' /etc/letsencrypt/renewal/EXAMPLE.com.au.conf (parsefail)' I tried turning off Letsencrypt for the two sites in ISPConfig and then turning it back on again but no effect.
You can try to compare the .conf file of a working cert with the one that fails and fix the failing one. There is likely a syntax error or a missing line. In the past, certbot had the tendency to mess up its own files sometimes.
