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: cnpd.pensions.rbm.mw

I ran this command: sudo certbot --nginx -d cnpd.pensions.rbm.mw

It produced this output:Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Requesting a certificate for cnpd.pensions.rbm.mw
Performing the following challenges:
http-01 challenge for cnpd.pensions.rbm.mw
Using default address 80 for authentication.
Waiting for verification...
Challenge failed for domain cnpd.pensions.rbm.mw
http-01 challenge for cnpd.pensions.rbm.mw
Cleaning up challenges
Some challenges have failed.


  • The following errors were reported by the server:

    Domain: cnpd.pensions.rbm.mw
    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.

My web server is (include version): nginx

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

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

1 Like

In order to fulfill the HTTP-01 challenge to prove to Let's Encrypt that you own the domain name, your site has to be publicly accessible on the Internet. That error shows that your web server isn't. (I can't get to it from my computer either.) That can have a bunch of causes, like (1) the web server software isn't running on the computer, (2) there's an intentional firewall in place only allowing some people access to the server, or (3) the IP for that hostname doesn't actually point to that server that you think it should.

So, if this is a server that's supposed to be available to everyone on the Internet, then you need to fix that problem first. And if it isn't supposed to be available to everyone (like it's a server only for internal use), then you need to either open up the firewall at least for /.well-known/acme-challenge/… requests or use the DNS-01 challenge instead.


pls test
curl https://acme-v02.api.letsencrypt.org

1 Like

i'm able to get a response. the Html page print

1 Like


Hello William :slightly_smiling_face:

From what I've seen, both ports 80 (http) and 443 (https) are closed for inbound connections to cnpd.pensions.rbm.mw. You can test this with:



Welcome to the Let's Encrypt Community, Myra :slightly_smiling_face:

That will only check for outbound connectivity to the Let's Encrypt server. The problem here is that there is no inbound connection over port 80 for Let's Encrypt to reach cnpd.pensions.rbm.mw.

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