Certbot Timeout during connect (likely firewall problem)

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: bld-team.tech

I ran this command: sudo certbot --nginx -v

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx

Which names would you like to activate HTTPS for?
We recommend selecting either all domains, or all domains in a VirtualHost/server block.


1: bld-team.tech
2: www.bld-team.tech


Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel):
Certificate not yet due for renewal

You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry.
(ref: /etc/letsencrypt/renewal/www.bld-team.tech.conf)

What would you like to do?


1: Attempt to reinstall this existing certificate
2: Renew & replace the certificate (may be subject to CA rate limits)


Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
Renewing an existing certificate for bld-team.tech and www.bld-team.tech
Performing the following challenges:
http-01 challenge for www.bld-team.tech
Waiting for verification...
Challenge failed for domain www.bld-team.tech
http-01 challenge for www.bld-team.tech

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: www.bld-team.tech
Type: connection
Detail: 5.180.30.76: Fetching http://www.bld-team.tech/.well-known/acme-challenge/0IRHaSOHDY4xzVUo2DBZNd25ddqY6maZ4PYHLOwTtYM: Timeout during connect (likely firewall problem)

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

Cleaning up challenges
Some challenges have failed.
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):
Nginx 1.18.0
The operating system my web server runs on is (include version):
Ubuntu 22.04
My hosting provider, if applicable, is: perfect quality hosting

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): 2.11.0

I have also tried curl presented URL. That's what I've got:
curl http://www.bld-team.tech/.well-known/acme-challenge/AEwo0sVoje3gsf965b2ARTANGWp2uNuLgHjFU3tVdTw

301 Moved Permanently

301 Moved Permanently


nginx/1.18.0 (Ubuntu)

Welcome to the community @ReaperOQ

Are you still having a problem? Because your apex and www subdomain are both using a cert you got about 40 minutes ago. See for example this SSL cert site: https://decoder.link/sslchecker/www.bld-team.tech/443

Since you have a cert could you try this and show result?

sudo certbot renew --dry-run
3 Likes

Why are you trying to get a new certificate when you already have one?

Testing should be done using --dry-run to prevent re-issuing production certificates without a good reason.

3 Likes

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