[Failed to renew certificate] - Some challenges have failed

Help
1

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. crt.sh | 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: http://library.wccac.net

I ran this command: sudo certbot -v renew --dry-run

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

Processing /etc/letsencrypt/renewal/library.wccac.net.conf

Certificate is due for renewal, auto-renewing...
Plugins selected: Authenticator apache, Installer apache
Simulating renewal of an existing certificate for library.wccac.net
Performing the following challenges:
http-01 challenge for library.wccac.net
Waiting for verification...
Challenge failed for domain library.wccac.net
http-01 challenge for library.wccac.net

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: library.wccac.net
Type: connection
Detail: 52.10.248.255: Fetching http://library.wccac.net/.well-known/acme-challenge/1uQrZ0WYhvXA6aAthsw-SMxw2FbGTbtAklCu3LnfO24: Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

Cleaning up challenges
Failed to renew certificate library.wccac.net with error: Some challenges have failed.

All simulated renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/library.wccac.net/fullchain.pem (failure)

1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): Apache/2.4.25 (Debian)

The operating system my web server runs on is (include version): Debian GNU/Linux 9.13

My hosting provider, if applicable, is: The web server is running on an AWS EC2

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): SSH Terminal

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 3.0.0

2

Welcome back @DHW0715

Have the earlier problems returned? You had a firewall blocking HTTP (port 80) last time. I can't reach your domain using HTTP requests from anywhere. Not even my own EC2 test server in US East region.

I can reach it using HTTPS (port 443) but not HTTP.

I made several suggestions last time. What did you finally decide to do?

3 Likes
3

I see what Mike sees as well

$ nmap -Pn -p80,443 library.wccac.net
Starting Nmap 7.93 ( https://nmap.org ) at 2024-11-07 17:53 PST
Nmap scan report for library.wccac.net (52.10.248.255)
Host is up (0.019s latency).
rDNS record for 52.10.248.255: ec2-52-10-248-255.us-west-2.compute.amazonaws.com

PORT    STATE    SERVICE
80/tcp  filtered http
443/tcp open     https

Nmap done: 1 IP address (1 host up) scanned in 1.47 seconds
1 Like
4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.