Timeout during connect (likely firewall problem) - Ports confirmed open


I’ve spent a few hours reading this forum and have been unable to resolve this issue. Port 80 is open on both the server and the router. I suspect I have some kind of configuration on apache setup to force HTTPS that may be interfering with certbot. I just can’t figure out how to fix it. Any help you can provide is appreciated.

firewall-cmd --zone=public --list-all
public (active)
target: default
icmp-block-inversion: no
interfaces: eth0
services: dhcpv6-client http https ssh
masquerade: no
rich rules:

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. https://crt.sh/?q=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: kristinandmatthew.com

I ran this command: certbot renew

It produced this output:

Challenge failed for domain www.kristinandmatthew.com
http-01 challenge for www.kristinandmatthew.com
Cleaning up challenges
Attempting to renew cert (www.kristinandmatthew.com) from /etc/letsencrypt/renewal/www.kristinandmatthew.com.conf produced an unexpected error: Some challenges have failed… Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/www.kristinandmatthew.com/fullchain.pem (failure)

** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/www.kristinandmatthew.com/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)

1 renew failure(s), 0 parse failure(s)


  • The following errors were reported by the server:

    Domain: www.kristinandmatthew.com
    Type: connection
    Detail: Fetching
    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.

  • Your account credentials have been saved in your Certbot
    configuration directory at /etc/letsencrypt. You should make a
    secure backup of this folder now. This configuration directory will
    also contain certificates and private keys obtained by Certbot so
    making regular backups of this folder is ideal.

My web server is (include version): Server version: Apache/2.4.6 (CentOS)

The operating system my web server runs on is (include version): CentOS 7

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

1 Like

Hi @simonetm

there is nothing open. But you have a curious configuration - see your check created this morning - https://check-your-website.server-daten.de/?q=kristinandmatthew.com

You have different ip addresses:

Host T IP-Address is auth. ∑ Queries ∑ Timeout
kristinandmatthew.com A Minneapolis/Minnesota/United States (US) - CenturyLink Hostname: 70-59-79-212.mpls.qwest.net yes 1 0
AAAA yes
www.kristinandmatthew.com A Minneapolis/Minnesota/United States (US) - CenturyLink Hostname: 70-59-70-54.mpls.qwest.net yes 1 0
AAAA yes

The non www works, there is an answer. The www has a timeout.

Do you really have one machine and two different ip addresses?

Or is the www ip address wrong / old / expired?

1 Like

Interesting. I recently setup Dynamic DNS. I need to correct this with the domain registrar right?

It’s not something misconfigured on the machine hosting the website, correct?

1 Like

It depends on what’s wrong.

You’re using Namecheap as the domain registrar, DNS service and dynamic DNS service, right?

You might need to change something in Namecheap’s control panel, or in the configuration of the dynamic DNS client installed on your device(s).

1 Like

Right, Dynamic DNS aside, the issue causing “certbot renew” to hang with the timeout is the www. address not resolving to the actual website?

1 Like

@JuergenAuer Updating the host record did the trick, thanks!


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