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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domains are: calolms.com and www.calolms.com and quercus.frantznursery.com
I ran this command: /usr/local/bin/certbot renew
Note that I ran that command in May and it worked fine. I donāt think anything substantial has changed on the server since then. The only difference, that Iām aware of, is that when I ran the command in May my previous certificates had not yet expired. However, when I run it today, my certificates ARE currently expired.
It produced this output:
[root@calolms ~]# /usr/local/bin/certbot renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/calolms.com.conf
Cert is due for renewal, auto-renewingā¦
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for calolms.com
http-01 challenge for www.calolms.com
Using the webroot path /var/www/html for all unmatched domains.
Waiting for verificationā¦
Challenge failed for domain calolms.com
Challenge failed for domain www.calolms.com
http-01 challenge for calolms.com
http-01 challenge for www.calolms.com
Cleaning up challenges
Attempting to renew cert (calolms.com) from /etc/letsencrypt/renewal/calolms.com.conf produced an unexpected error: Some challenges have failedā¦ Skipping.
Processing /etc/letsencrypt/renewal/quercus.frantznursery.com.conf
Cert is due for renewal, auto-renewingā¦
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for quercus.frantznursery.com
Cleaning up challenges
Attempting to renew cert (quercus.frantznursery.com) from /etc/letsencrypt/renewal/quercus.frantznursery.com.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6ā¦ Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/calolms.com/fullchain.pem (failure)
/etc/letsencrypt/live/quercus.frantznursery.com/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/calolms.com/fullchain.pem (failure)
/etc/letsencrypt/live/quercus.frantznursery.com/fullchain.pem (failure)
2 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: calolms.com
Type: unauthorized
Detail: Invalid response from
https://quercus.frantznursery.com/.well-known/acme-challenge/kUTNDyidLqyCVHDs8Mrj2FJTAvB6mdkDgo9qXX69oRI
[3.89.181.113]: ā\n\n404 Not
Found\n\nNot Found
\n<pāDomain: www.calolms.com
Type: unauthorized
Detail: Invalid response from
https://quercus.frantznursery.com/.well-known/acme-challenge/RanM26zEGWd1xV-cycmu03ODbBF8jez-Giid-7a9jqc
[3.89.181.113]: ā\n\n404 Not
Found\n\nNot Found
\n<pāTo fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
[root@calolms ~]#
My web server is (include version): Amazon linux (EC2)ā¦
The operating system my web server runs on is (include version):
[root@calolms ~]# uname -a
Linux calolms.com 4.14.181-108.257.amzn1.x86_64 #1 SMP Wed May 27 02:43:03 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
My hosting provider, if applicable, is: AWS
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):
[root@calolms ~]# certbot --version
certbot 0.40.1
[root@calolms ~]# certbot-auto --version
-bash: certbot-auto: command not found
Additional details you did not ask forā¦ It appears as if thereās some kind of problem with the āwell-defined/acme-challengeā mechanism. So, to be sure, here are the permissions of all the pertinent direcrtories:
[root@calolms ~]# ls -ald /
dr-xr-xr-x 26 root root 4096 Jun 6 22:34 /
[root@calolms ~]# ls -ald /var
drwxr-xr-x 20 root root 4096 Sep 16 2019 /var
[root@calolms ~]# ls -ald /var/www
drwxr-xr-x 8 root root 4096 May 14 11:13 /var/www
[root@calolms ~]# ls -ald /var/www/html
drwxr-xr-x 15 root root 4096 Jul 24 17:21 /var/www/html
[root@calolms ~]# ls -ald /var/www/html/.well-known
drwxr-xr-x 3 root root 4096 May 7 11:53 /var/www/html/.well-known
[root@calolms ~]# ls -ald /var/www/html/.well-known/acme-challenge
drwxr-xr-x 2 root root 4096 Aug 3 17:15 /var/www/html/.well-known/acme-challenge
[root@calolms ~]# ls -al /var/www/html/.well-known/acme-challenge
total 8
drwxr-xr-x 2 root root 4096 Aug 3 17:15 .
drwxr-xr-x 3 root root 4096 May 7 11:53 ā¦
-rw-rār-- 1 root root 0 May 7 11:53 O4JFsJ1UgzFX_doR6skfqjJGjceLst5imK9paMx1ctU
That last one may be tellingā¦ it at least shows that a file was built via this mechanism last May, which I think, maybe?, indicates that it worked back then. It also shows that the acme-challenge directory appears to have been modified today (Aug 3)ā¦ so something happened there today.
Ok, so what now?