Failed to renew: Timeout during connect (likely firewall 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. |, 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: sudo certbot renew -v

It produced this output:
Certificate is due for renewal, auto-renewing...
Plugins selected: Authenticator apache, Installer apache
Simulating renewal of an existing certificate for
Performing the following challenges:
http-01 challenge for
Waiting for verification...
Challenge failed for domain
http-01 challenge for

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Type: connection
Detail: Fetching Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

Cleaning up challenges
Failed to renew certificate with error: Some challenges have failed.

My web server is (include version):

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

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 1.22.0

Welcome to the community @NorhishamMN

Have you added a firewall recently? Because I cannot reach your website from the US or several other places around the globe.

The Let's Debug test site (link here) shows the error you see above

Or, maybe your IP address changed? The DNS says


Hi @MikeMcQ ,

Thank you for the reply, sorry for the delayed reply
IP Address is same nothing is changed, its a public ipv4 address that was created in Azure
Port 80 is already open from source to public IP

1 Like

Hi @MikeMcQ ,

Sorry found out what the issue was, I was typing earlier that Port 80 is open from source to public
Then it strikes me, port 80 should open for everything for cert to renew
Did that and it works :smile:

Thank you!


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