Timeout error but machine accessible from multiple hosts

Hi there,

I'm trying to get a certificate for my domain but I receive timeout errors from Let's Encrypt.
Here's the same issue shown in Let's Debug: Let's Debug

I'm confused as I'm able to access this machine from various hosts located in different parts of the world, but it seems like Let's Encrypt is unable to connect.

check-your-website.server-daten.de result: https://check-your-website.server-daten.de/?q=nl-vspc001.ek.co

My domain is: nl-vspc001.ek.co

I ran this command: /usr/bin/certbot --webroot --noninteractive --agree-tos --email REDACTED --webroot-path /var/www/html -d nl-vspc001.ek.co

It produced this output:

stderr:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Performing the following challenges:
http-01 challenge for nl-vspc001.ek.co
Using the webroot path /var/www/html for all unmatched domains.
Waiting for verification...
Challenge failed for domain nl-vspc001.ek.co
http-01 challenge for nl-vspc001.ek.co
Cleaning up challenges
Some challenges have failed.

stdout:
Requesting a certificate for nl-vspc001.ek.co
IMPORTANT NOTES:
- The following errors were reported by the server:

   Domain: nl-vspc001.ek.co
   Type:   connection
   Detail: 185.44.245.140: Fetching
   http://nl-vspc001.ek.co/.well-known/acme-challenge/mo6Vrcg1aiQvaiE6DRky6cE2oOwCtfA7n2saxdjEAr0:
   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): nginx/1.22.1

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

My hosting provider, if applicable, is: We're hosting this ourselves

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 1.12.0

While I can connect too (just 10 ms away in the same country as the host), Let's Debug is also showing connection issues from its own point of view:

Looks like there might be some geo-blocking in progress. Let's Encrypt validates from multiple vantage points around the world with changing IP addresses, so the host needs to be accessible from any IP address, regardless of location.

Looking at the test results at Website Availability Test - Check Website Uptime | Uptimia it seems like your site is only accessible from some sites in Europe and not even all of them. Outside of Europe, none can connect.

This is confirmed by e.g. https://geopeeker.com/fetch/?url=nl-vspc001.ek.co.

6 Likes

Thank you Osiris, I hadn't considered that possibility. My test hosts were indeed all located in Europe. I'll ask in the company if geo blocking is setup or if there are some other routing issues.

Will report back with the results :slight_smile:

3 Likes

Thanks again for the help @Osiris, there was indeed geo-blocking. After getting it removed it I was able to get a new certificate issued.

6 Likes

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