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 domain is:
test.ericmauldin.info
I ran this command:
sudo certbot renew --dry-run
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/test.ericmauldin.info.conf
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Running pre-hook command: /etc/letsencrypt/renewal-hooks/pre/nginx.sh
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for test.ericmauldin.info
Using the webroot path /root/recipe-app-backend for all unmatched domains.
Waiting for verification…
Challenge failed for domain test.ericmauldin.info
http-01 challenge for test.ericmauldin.info
Cleaning up challenges
Attempting to renew cert (test.ericmauldin.info) from /etc/letsencrypt/renewal/test.ericmauldin.info.conf produced an unexpected error: Some challenges have failed… Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/test.ericmauldin.info/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/test.ericmauldin.info/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)
Running post-hook command: /etc/letsencrypt/renewal-hooks/post/nginx.sh
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: test.ericmauldin.info
Type: connection
Detail: Fetching
http://test.ericmauldin.info/.well-known/acme-challenge/lrbCb0Lo5ynvG3Nw5BcTALKqvUJTQU8udAHmbywACgo:
Connection refusedTo 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. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
My web server is (include version):
nginx/1.17.10 (Ubuntu)
The operating system my web server runs on is (include version):
Ubuntu 20.04
My hosting provider, if applicable, is:
namecheap
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 0.40.0