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:
partes.tasiva.com
I ran this command:
certbot certonly --manual -d partes.tasiva.com
It produced this output:
*Saving debug log to /var/log/letsencrypt/letsencrypt.log
Renewing an existing certificate for partes.tasiva.com


Create a file containing just this data:

2qfFnnlvDmCRkDa-oHqP5wbHjRTC4A9mwtiVg9nxFy8.m31wQIF-q-gPSezTQWrOwz5sCDaehsR3XYOEDwZWcfs

And make it available on your web server at this URL:

http://partes.tasiva.com/.well-known/acme-challenge/2qfFnnlvDmCRkDa-oHqP5wbHjRTC4A9mwtiVg9nxFy8


Press Enter to Continue

Certbot failed to authenticate some domains (authenticator: manual). The Certificate Authority reported these problems:
Domain: partes.tasiva.com
Type: connection
Detail: 88.10.67.208: Fetching http://partes.tasiva.com/.well-known/acme-challenge/2qfFnnlvDmCRkDa-oHqP5wbHjRTC4A9mwtiVg9nxFy8: Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to verify the manually created challenge files. Ensure that you created these in the correct location.

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):
apache2 (2.11.0)
The operating system my web server runs on is (include version):
Debian 6.1.94-1
My hosting provider, if applicable, is:
Dinahosting
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):
I think not, but Iā€™m not sure.
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Certbot 2.11.0
Explanation:
When I execute the command certbot certonly --manual -d partes.tasiva.com and I create the file in the path it tells me, I can access the file from the internet. (From another computer)
But when I hit enter and Certbot tries to access the path I get the error I showed before. I don't understand why this happens, any idea? I've checked everything, from opening ports 80, 8080, 443, permissions problems... But nothing.

Hi @iker.iparraguirre, and welcome to the LE community forum :slight_smile:

That is usually exactly what it sounds like.
Are you running a local firewall?
Is that the correct IP [88.10.67.208]?
Is your site accessible from the Internet via HTTP [TCP port 80]?

2 Likes

Yes, I am using the UFW firewall, here are the rules I have set up:
*Status: active

To Action From


1194/udp ALLOW Anywhere
OpenSSH ALLOW Anywhere
8080 ALLOW Anywhere
3306 ALLOW Anywhere
3306/tcp ALLOW Anywhere
80 ALLOW Anywhere
443 ALLOW Anywhere
9194 ALLOW Anywhere
8086 ALLOW Anywhere
3001 ALLOW Anywhere
8000 ALLOW Anywhere
3000 ALLOW Anywhere
9090 ALLOW Anywhere
80/tcp ALLOW Anywhere
443/tcp ALLOW Anywhere
22/tcp ALLOW Anywhere
30500 ALLOW Anywhere
1194/udp (v6) ALLOW Anywhere (v6)
OpenSSH (v6) ALLOW Anywhere (v6)
8080 (v6) ALLOW Anywhere (v6)
3306 (v6) ALLOW Anywhere (v6)
3306/tcp (v6) ALLOW Anywhere (v6)
80 (v6) ALLOW Anywhere (v6)
443 (v6) ALLOW Anywhere (v6)
9194 (v6) ALLOW Anywhere (v6)
8086 (v6) ALLOW Anywhere (v6)
3001 (v6) ALLOW Anywhere (v6)
8000 (v6) ALLOW Anywhere (v6)
3000 (v6) ALLOW Anywhere (v6)
9090 (v6) ALLOW Anywhere (v6)
80/tcp (v6) ALLOW Anywhere (v6)
443/tcp (v6) ALLOW Anywhere (v6)
22/tcp (v6) ALLOW Anywhere (v6)
30500 (v6) ALLOW Anywhere (v6)*

The IP Address is correct, I can see the certificate correctly as you can see in the image:

Can you also reach your site/IP from the Internet?

I can't:

curl -Ii http://partes.tasiva.com/.well-known/acme-challenge/Test_File-1234
curl: (28) Failed to connect to partes.tasiva.com port 80 after 130996 ms: Connection timed out
2 Likes

Yes, I can, I see the following if I run from my home computer (it's outside my company's network)
image
And if i run from my company computer i see the same:
HTTP/1.1 404 Not Found
Date: Mon, 23 Sep 2024 12:24:11 GMT
Server: Apache/2.4.61 (Debian)
Cache-Control: no-cache, private
Content-Type: text/html; charset=UTF-8

1 Like

hmm...

Is there any GEO-Location blocking?

3 Likes

Looks like it; one tool I tried could only connect from Spain, and not from anywhere else.

4 Likes

It could be, everything seems to indicate that yes, my company's external firewall is run by another company, I'll send them an email and I'll let you know what they tell me.

1 Like

I just wrote an email to the company that manages our firewall to allow connections from anywhere in the world. I will let you know what they tell me.

1 Like

You (and/or the people managing the network) may find this post useful, describing how and why Let's Encrypt checks from multiple places around the world to ensure that one actually controls a domain name as seen from everywhere.

6 Likes

I bring good news, the problem was what you told me, the firewall rules have been changed to allow connections from anywhere in the world and now I have obtained the certificates correctly. Thank you very much!

3 Likes

It was what you said, the rules have been changed to allow connections from anywhere in the world and I have been able to obtain the certificates correctly.
Thank you very much!

3 Likes

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