# Failed authorization procedure. Timeout during connect (likely firewall problem)

**URL:** <https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-during-connect-likely-firewall-problem/157417>\
**Category:** Help\
**Created:** [August 9, 2021, 8:17am UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-during-connect-likely-firewall-problem/157417 "2021-08-09T08:17:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![edq37843](https://avatars.discourse-cdn.com/v4/letter/e/ebca7d/32.png) [@edq37843](https://community.letsencrypt.org/u/edq37843)\
**Post date:** [August 9, 2021, 8:17am UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-during-connect-likely-firewall-problem/157417/1 "2021-08-09T08:17:40Z")

</div>

Hello,

it was working fine for me before, but now I cannot get certificate for any new domain nor can update existing certificates. Tried automatically and manually.

Certificates are expiring and I cannot renew them for some reason.

Port 80 is open, firewall is letting it through, but somehow it still wouldn't work.

What could be the problem? It was working fine before

INFO:

My domain is: restreamer.beesport.online

I ran this command: sudo certbot --nginx -d restreamer.beesport.online and sudo certbot --renew

It produced this output:  
Saving debug log to /var/log/letsencrypt/letsencrypt.log  
Plugins selected: Authenticator nginx, Installer nginx  
Cert is due for renewal, auto-renewing...  
Renewing an existing certificate  
Performing the following challenges:  
http-01 challenge for restreamer.beesport.online  
Waiting for verification...  
Cleaning up challenges  
Failed authorization procedure. restreamer.beesport.online (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [http://restreamer.beesport.online/.well-known/acme-challenge/Pzd53lAVuswp9GhWCeXCrtUiVTRZNqc-Uqo1wGY8tjo:](http://restreamer.beesport.online/.well-known/acme-challenge/Pzd53lAVuswp9GhWCeXCrtUiVTRZNqc-Uqo1wGY8tjo:) Timeout during connect (likely firewall problem)

IMPORTANT NOTES:

- The following errors were reported by the server:

My web server is (include version): Nginx proxy - nginx/1.14.2

The operating system my web server runs on is (include version): Debian GNU/Linux 10 (buster)

My hosting provider, if applicable, is: NA

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 0.31.0

---

<div class="post-metadata">

**Author:** ![webprofusion](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/webprofusion/32/85310_2.png) [@webprofusion](https://community.letsencrypt.org/u/webprofusion)\
**Post date:** [August 9, 2021, 9:03am UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-during-connect-likely-firewall-problem/157417/2 "2021-08-09T09:03:03Z")

</div>

I think you may be geoblocking requests to your site, so you are inadvertently blocking validation requests from Let's Encrypt.

> **[Test result for restreamer.beesport.online: Error](https://letsdebug.net/restreamer.beesport.online/629660)**
>
> 1 unique issue(s) detected (IssueFromLetsEncrypt)

---

<div class="post-metadata">

**Author:** ![edq37843](https://avatars.discourse-cdn.com/v4/letter/e/ebca7d/32.png) [@edq37843](https://community.letsencrypt.org/u/edq37843)\
**Post date:** [August 9, 2021, 11:03am UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-during-connect-likely-firewall-problem/157417/3 "2021-08-09T11:03:49Z")

</div>

Thank you. It was not geoblocked but our Mikrotik blocked all lets encrypt attempts. Thanks for pointing to the right direction!

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [August 9, 2021, 1:49pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-during-connect-likely-firewall-problem/157417/4 "2021-08-09T13:49:53Z")

</div>

If Mikrotik allows, you should Geoblock block HTTPS (but not HTTP).  
You could handle the global ACME challenge requests in HTTP and forward all else to HTTPS.

For `nginx`, try something like:

```nohighlight
  location ^/(?!\.well-known) { # skip challenge requests
    return 301 https://$host$request_uri; # send all requests to HTTPS
  }# location
  root /new/dedicated/challenge/path;

```

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [September 8, 2021, 1:49pm UTC](https://community.letsencrypt.org/t/failed-authorization-procedure-timeout-during-connect-likely-firewall-problem/157417/5 "2021-09-08T13:49:59Z")

</div>

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