Timeout Error after connect


#1

I have been using certbot without problem but since a few months ago it suddenly stopped working to update the certificate. The log follows below. My guess is the connection from the letsencrypt server is blocked by the firewall in my institute, but our system manager says there is no blocking. Please help.


2019-02-12 18:41:11,366:DEBUG:acme.client:Sending GET request to https://acme-v02.api.letsencrypt.org/acme/authz/0y_kcF2W5Osc0ZPuVBUcOtHDdSnvEBLe8qzxxkjHWnc.
2019-02-12 18:41:11,644:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 “GET /acme/authz/0y_kcF2W5Osc0ZPuVBUcOtHDdSnvEBLe8qzxxkjHWnc HTTP/1.1” 200 1816
2019-02-12 18:41:11,645:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Content-Type: application/json
Content-Length: 1816
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800
Expires: Tue, 12 Feb 2019 09:41:11 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 12 Feb 2019 09:41:11 GMT
Connection: keep-alive

{
“identifier”: {
“type”: “dns”,
“value”: “sage.kunsan.ac.kr”
},
“status”: “invalid”,
“expires”: “2019-02-19T09:39:35Z”,
“challenges”: [
{
“type”: “tls-sni-01”,
“status”: “invalid”,
“url”: “https://acme-v02.api.letsencrypt.org/acme/challenge/0y_kcF2W5Osc0ZPuVBUcOtHDdSnvEBLe8qzxxkjHWnc/12541854980”,
“token”: “RS9YvHp4u2kwVpdBZNhNvYeJlep0KdK4BZpEekRsnQI”
},
{
“type”: “tls-alpn-01”,
“status”: “invalid”,
“url”: “https://acme-v02.api.letsencrypt.org/acme/challenge/0y_kcF2W5Osc0ZPuVBUcOtHDdSnvEBLe8qzxxkjHWnc/12541854981”,
“token”: “dvtFyu-DYXAN6o4V_xjeMtcBZ7VbmB9CUIuq3UQm1yY”
},
{
“type”: “dns-01”,
“status”: “invalid”,
“url”: “https://acme-v02.api.letsencrypt.org/acme/challenge/0y_kcF2W5Osc0ZPuVBUcOtHDdSnvEBLe8qzxxkjHWnc/12541854982”,
“token”: “6WCTzPJb88MeujRzMIatPvhXgpw-dnnxWmUBSorPBOM”
},
{
“type”: “http-01”,
“status”: “invalid”,
“error”: {
“type”: “urn:ietf:params:acme:error:connection”,
“detail”: “Fetching http://sage.kunsan.ac.kr/.well-known/acme-challenge/JMJw-oeCRnNcpLtGWTIFI3m_45AU_zuetDUgmNY59dw: Timeout after connect (your server may be slow or overloaded)”,
“status”: 400
},
“url”: “https://acme-v02.api.letsencrypt.org/acme/challenge/0y_kcF2W5Osc0ZPuVBUcOtHDdSnvEBLe8qzxxkjHWnc/12541854983”,
“token”: “JMJw-oeCRnNcpLtGWTIFI3m_45AU_zuetDUgmNY59dw”,
“validationRecord”: [
{
“url”: “http://sage.kunsan.ac.kr/.well-known/acme-challenge/JMJw-oeCRnNcpLtGWTIFI3m_45AU_zuetDUgmNY59dw”,
“hostname”: “sage.kunsan.ac.kr”,
“port”: “80”,
“addressesResolved”: [
“203.234.55.233”
],
“addressUsed”: “203.234.55.233”
}
]
}
]
}
2019-02-12 18:41:11,647:DEBUG:certbot.reporter:Reporting to user: The following errors were reported by the server:

Domain: sage.kunsan.ac.kr
Type: connection
Detail: Fetching http://sage.kunsan.ac.kr/.well-known/acme-challenge/JMJw-oeCRnNcpLtGWTIFI3m_45AU_zuetDUgmNY59dw: Timeout after connect (your server may be slow or overloaded)

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.
2019-02-12 18:41:11,648:DEBUG:certbot.error_handler:Encountered exception:
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/certbot/auth_handler.py”, line 82, in handle_authorizations
self._respond(aauthzrs, resp, best_effort)
File “/usr/lib/python3/dist-packages/certbot/auth_handler.py”, line 161, in _respond
self._poll_challenges(aauthzrs, chall_update, best_effort)
File “/usr/lib/python3/dist-packages/certbot/auth_handler.py”, line 232, in _poll_challenges
raise errors.FailedChallenges(all_failed_achalls)
certbot.errors.FailedChallenges: Failed authorization procedure. sage.kunsan.ac.kr (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://sage.kunsan.ac.kr/.well-known/acme-challenge/JMJw-oeCRnNcpLtGWTIFI3m_45AU_zuetDUgmNY59dw: Timeout after connect (your server may be slow or overloaded)


My domain is: sage.kunsan.ac.kr

I ran this command: sudo certbot --apache certonly

It produced this output:
Cert is due for renewal, auto-renewing…
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for sage.kunsan.ac.kr
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. sage.kunsan.ac.kr (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://sage.kunsan.ac.kr/.well-known/acme-challenge/JMJw-oeCRnNcpLtGWTIFI3m_45AU_zuetDUgmNY59dw: Timeout after connect (your server may be slow or overloaded)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: sage.kunsan.ac.kr
    Type: connection
    Detail: Fetching
    http://sage.kunsan.ac.kr/.well-known/acme-challenge/JMJw-oeCRnNcpLtGWTIFI3m_45AU_zuetDUgmNY59dw:
    Timeout after connect (your server may be slow or overloaded)

    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): apache 2.4.18

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

My hosting provider, if applicable, is:

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


#2

Hi @bench

your server is invisible ( https://check-your-website.server-daten.de/?q=sage.kunsan.ac.kr ): Only timeouts.

Domainname Http-Status redirect Sec. G
http://sage.kunsan.ac.kr/
203.234.55.233 -14 16.077 T
Timeout - The operation has timed out.
https://sage.kunsan.ac.kr/
203.234.55.233 -14 10.017 T
Timeout - The operation has timed out
http://sage.kunsan.ac.kr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
203.234.55.233 -14 10.016 T
Timeout - The operation has timed out

So http-01 - validation can’t work.

And not only port 80, same with port 443.


#3

Thank you so much for quick reply.

I am puzzled why my server is invisible. I can access the site, so what does it mean that the server is invisible?. And can you please show me how the problem can be fixed? Many thanks


#4

So your server works internal.

Perhaps a firewall that drops incoming requests silent.

Curious: kunsan.ac.kr works partial ( https://check-your-website.server-daten.de/?q=kunsan.ac.kr ):

http://kunsan.ac.kr/
202.30.55.40
	-14
	
	16.030
	T
Timeout - The operation has timed out

has a timeout, but the www and /.well-known/acme-challenge works.

One idea - geoblocking. But

http://kunsan.ac.kr/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de

sends a 302,

http://kunsan.ac.kr/

has a timeout. Perhaps some additional filters.


#5

Thank you so much. I think you nailed the problem. It must be geoblocking. I believe our system manager can help. Thanks again!


#6

It’s curious that the university has a geoblocking.

Access to / isn’t required.

But access to

/.well-known/acme-challenge

is required.


#7

Yes, geoblocking is stupid; unfortunately, they do not know what they are doing.