Connection timout on one virtual host

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: /root/letsencrypt/certbot-auto

It produced this output:
Type: connection
Detail: Fetching
Timeout during connect (likely firewall problem)

My web server is (include version):
Apache httpd-2.2.15-60.el6.centos.6.x86_64

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

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

I have a bunch of virtual hosts, e.g.,, is no different.
When I run certbot-auto it lists 18 different hosts. If I check some, it works. If I include, it fails.

Renewing an existing certificate
Performing the following challenges:
http-01 challenge for
http-01 challenge for
http-01 challenge for
http-01 challenge for
http-01 challenge for
Waiting for verification…
Challenge failed for domain
http-01 challenge for
Cleaning up challenges
Some challenges have failed. is a CNAME. The A record is the same as the other virtual hosts. It had a LetsEncrypt certificate before, which expired in May 2019

I can access the website just fine in my browser, though currently there’s just the Apache splash page. I’m not sure why the LE robot would be timing out on that URL. The directory exists on the server.
A test file is accessible

It looks like your websites have two different IP addresses:                 14400  A             14400  A              14400  A      14400  A  14400  A  14400  A  14400  A                 14400  A             14400  A              14400  A          14400  A

I get a "no route to host" error if I try to connect to on port 80.

For what it's worth, the zone apex isn't allowed to be a CNAME. Some DNS software will let you do it, but it's not valid, and it won't work reliably.

I don't see a CNAME record on, though.

1 Like

I just realized this is connected to DNS issues I have been having. Network Solutions hides the DNS IP address in their database view and only shows the name. So some domains were using stale DNS entries in and, although when I did a DNS lookup here I got the correct new values pulled from or
I’ve just changed the DNS servers for all my domains on Network Solutions to new names, dns4… with those IP addresses. Those seem to have been pushed to the TLD servers.

I think this is solved; I was able to renew the cert for It’s a bit weird though - as I say I had obtained a certificate this year although the DNS issue has been present since late 2018.

I was mistaken; is not a CNAME. is a CNAME

Thank you - Andrew

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