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: roe13.org
I ran this command: /certbot-auto renew --dry-run Renew also fails the same way as does manual.
It produced this output:
Cert is due for renewal, auto-renewingâŚ
Plugins selected: Authenticator apache, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for roe13.org
http-01 challenge for www.roe13.org
Waiting for verificationâŚ
Challenge failed for domain roe13.org
Challenge failed for domain www.roe13.org
http-01 challenge for roe13.org
http-01 challenge for www.roe13.org
Cleaning up challenges
Attempting to renew cert (roe13.org) from /etc/letsencrypt/renewal/roe13.org.conf produced an unexpected error: Some challenges have failed⌠Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/roe13.org/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/roe13.org/fullchain.pem (failure)
** DRY RUN: simulating âcertbot renewâ close to cert expiry
** (The test certificates above have not been saved.)
1 renew failure(s), 0 parse failure(s)
IMPORTANT NOTES:
-
The following errors were reported by the server:
Domain: roe13.org
Type: connection
Detail: During secondary validation: Fetching
http://roe13.org/.well-known/acme-challenge/itYW0XRoH1y8HJOuh6GS4vrFqsS6AZfPv6vC25A-p5w:
Timeout during connect (likely firewall problem)Domain: www.roe13.org
Type: connection
Detail: During secondary validation: Fetching
http://www.roe13.org/.well-known/acme-challenge/o4Tqu7_Cm2Bc5zg7pODX9orqgu7qq1sMZT7iNrkfHVU:
Timeout during connect (likely firewall problem)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. 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): Server version: Apache/2.4.23 (Linux/SUSE)
Server built: 2019-02-26 15:44:01.000000000 +0000
The operating system my web server runs on is (include version):
NAME=âopenSUSE Leapâ
VERSION=â42.3â
My hosting provider, if applicable, is: self
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): 0.15.0 (same issue with second identical server with newer version)
Logs show successful access to the validation files.
18.224.20.83 - - [18/Mar/2020:11:29:05 -0500] âGET /.well-known/acme-challenge/o4Tqu7_Cm2Bc5zg7pODX9orqgu7qq1sMZT7iNrkfHVU HTTP/1.1â 200 87 â-â âMozilla/5.0 (compatible; Letâs Encrypt validation server; +https://www.letsencrypt.org)â
18.224.20.83 - - [18/Mar/2020:11:29:06 -0500] âGET /.well-known/acme-challenge/itYW0XRoH1y8HJOuh6GS4vrFqsS6AZfPv6vC25A-p5w HTTP/1.1â 200 87 â-â âMozilla/5.0 (compatible; Letâs Encrypt validation server; +https://www.letsencrypt.org)â
66.133.109.36 - - [18/Mar/2020:11:29:06 -0500] âGET /.well-known/acme-challenge/itYW0XRoH1y8HJOuh6GS4vrFqsS6AZfPv6vC25A-p5w HTTP/1.1â 200 87 â-â âMozilla/5.0 (compatible; Letâs Encrypt validation server; +https://www.letsencrypt.org)â
66.133.109.36 - - [18/Mar/2020:11:29:06 -0500] âGET /.well-known/acme-challenge/o4Tqu7_Cm2Bc5zg7pODX9orqgu7qq1sMZT7iNrkfHVU HTTP/1.1â 200 87 â-â âMozilla/5.0 (compatible; Letâs Encrypt validation server; +https://www.letsencrypt.org)â
Same results with manual. Checks with whynopadlock, ssllabs and Letâs debug are good. check-your-website.server also gets the error: Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge canât work. You need a running webserver (http) and an open port 80. If itâs a home server + ipv4, perhaps a correct port forwarding port 80 extern â working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If itâs a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask
I do block most out of the US addresss at a firewall but web logs show access. Updates were fine all last year and worked on 1/1/2020. No changes since then until I started trying to fix it.