Some challenges have failed

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. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:
certbot certonly --webroot --webroot-path=/var/lib/zulip/certbot-webroot/ -d -m --force-interactive --no-eff-email -v

It produced this output:
Error Log:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Requesting a certificate for
Performing the following challenges:
http-01 challenge for
Using the webroot path /var/lib/zulip/certbot-webroot for all unmatched domains.
Waiting for verification...
Challenge failed for domain
http-01 challenge for

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Type: connection
Detail: Fetching Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

Cleaning up challenges
Some challenges have failed.
Ask for help or search for solutions at See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): Ubuntu 22

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

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

How fix this error ?
What i misstake?

1 Like

Welcome to the community @blake

The reason for the Timeout is that the Let's Encrypt servers cannot reach your domain using HTTP to perform the challenge. You must have port 80 open to the public internet to allow the HTTP request. Your port 80 is currently blocked by what looks like a firewall. You should check your EC2 Security Group inbound rule for port 80 and make sure it is allowed. Also check any other firewalls.

The Let's Debug test site is helpful when testing comms setups on new sites.

Also, for Ubuntu 22 you should look to update Certbot to the snap install rather than the apt version. Version 1.21 is already 2 years old and there have been many improvements since. Follow instructions below but carefully. The 1.21 is not causing your Timeout it is just good practice to update.


Additional supporting information to

$ nmap -Pn -p80,443
Starting Nmap 7.80 ( ) at 2023-11-23 22:26 UTC
Nmap scan report for (
Host is up (0.15s latency).
Other addresses for (not scanned):
rDNS record for

80/tcp  filtered http
443/tcp open     https

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

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