# Error starting Certbot (Likely firewall problem)

**URL:** <https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038>\
**Category:** Help\
**Created:** [March 2, 2022, 7:22pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038 "2022-03-02T19:22:55Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pinkhas](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@Pinkhas](https://community.letsencrypt.org/u/Pinkhas)\
**Post date:** [March 2, 2022, 7:22pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/1 "2022-03-02T19:22:55Z")

</div>

**My domain is** : [pinkhas.hopto.org](http://pinkhas.hopto.org) (DDNS)

**I ran this command** : certbot -d [pinkhas.hopto.org](http://pinkhas.hopto.org) certonly --standalone

**It produced this output:**  
Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:  
Domain: [pinkhas.hopto.org](http://pinkhas.hopto.org)  
Type: connection  
Detail: Fetching [http://pinkhas.hopto.org/.well-known/acme-challenge/LVnPZugERvDh4Z03gBfcFnqQnL1AMLHOrDWCjZ3SeJY:](http://pinkhas.hopto.org/.well-known/acme-challenge/LVnPZugERvDh4Z03gBfcFnqQnL1AMLHOrDWCjZ3SeJY:) Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

**My web server is (include version):** creating one myself, clicked on "Other" in the certbot installation

**The operating system my web server runs on is (include version)**: Win11 (My PC)

**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.24.0

Soooooo  
I've disabled the firewall on my pc (Win11 - the webserver host) and forwarded ports 80 and 443 (Also tried DMZ on/off - same result either way).  
When I ran the command with the --manual option, it did create and deleted almost immediately after a .well-known directory contaning a few files.

Any ideas?  
Thanks!

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [March 2, 2022, 7:51pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/2 "2022-03-02T19:51:19Z")

</div>

> [@Pinkhas](#):
>
> Timeout during connect

Same for me.

Are you sure your IP address is `46.117.123.105` and you have allowed inbound connections on your firewalls (pc, router, isp) and port forwarding on your router?

---

<div class="post-metadata">

**Author:** ![Pinkhas](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@Pinkhas](https://community.letsencrypt.org/u/Pinkhas)\
**Post date:** [March 2, 2022, 8:04pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/3 "2022-03-02T20:04:43Z")

</div>

When I run my web app, I can connect via my external ip as well as the domain name using a browser (port 80 - indicating that my firewalls aren't blocking the connection).  
I've also set up a windows firewall "Inbound Rule" and configured a port forwarding rule that leads to my PC to allow all connection using port 80 as TCP.

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [March 2, 2022, 8:07pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/4 "2022-03-02T20:07:30Z")

</div>

@pinkhas Welcome to the community

You could add `--debug-challenge -v` to your command

That will pause before doing the challenge so you (or we) could try it.  
The standalone mode is harder to debug otherwise since port 80 is only connected while the standalone server is running.

---

<div class="post-metadata">

**Author:** ![Pinkhas](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@Pinkhas](https://community.letsencrypt.org/u/Pinkhas)\
**Post date:** [March 2, 2022, 8:16pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/5 "2022-03-02T20:16:14Z")

</div>

Ran the command with the suggested args.  
As the cmd described, I created a file in C:.well-known\acme-challenge\ with the proper name and value and pressed a key in order to let the program run.

Output:  
C:\WINDOWS\system32\>certbot -d [pinkhas.hopto.org](http://pinkhas.hopto.org) certonly --standalone --debug-challenge -v  
Saving debug log to C:\Certbot\log\letsencrypt.log  
Plugins selected: Authenticator standalone, Installer None  
Requesting a certificate for [pinkhas.hopto.org](http://pinkhas.hopto.org)  
Performing the following challenges:  
http-01 challenge for [pinkhas.hopto.org](http://pinkhas.hopto.org)

* * *

Challenges loaded. Press continue to submit to CA.

The following URLs should be accessible from the internet and return the value  
mentioned:

URL:  
[http://pinkhas.hopto.org/.well-known/acme-challenge/-HyRonz0BP-nCdlCvBbl-AWuyPaJb\_YyK2Pncxm5Ka8](http://pinkhas.hopto.org/.well-known/acme-challenge/-HyRonz0BP-nCdlCvBbl-AWuyPaJb_YyK2Pncxm5Ka8)  
Expected value:  
-HyRonz0BP-nCdlCvBbl-AWuyPaJb\_YyK2Pncxm5Ka8.sy6COMqEWsXkSUoZr-PnXJUvioeTCAQ1DOh0I2vvBDI

* * *

Press Enter to Continue  
Waiting for verification...  
Challenge failed for domain [pinkhas.hopto.org](http://pinkhas.hopto.org)  
http-01 challenge for [pinkhas.hopto.org](http://pinkhas.hopto.org)

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:  
Domain: [pinkhas.hopto.org](http://pinkhas.hopto.org)  
Type: connection  
Detail: Fetching [http://pinkhas.hopto.org/.well-known/acme-challenge/-HyRonz0BP-nCdlCvBbl-AWuyPaJb\_YyK2Pncxm5Ka8:](http://pinkhas.hopto.org/.well-known/acme-challenge/-HyRonz0BP-nCdlCvBbl-AWuyPaJb_YyK2Pncxm5Ka8:) Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet.

Cleaning up challenges  
Some challenges have failed.  
Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org). See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [March 2, 2022, 8:19pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/6 "2022-03-02T20:19:14Z")

</div>

You should not create any challenge files certbot does that for you.

Do you have any geo blocking in your firewall?

Try running the command again but when it says "Press Enter to Continue" don't do anything and let us know the URL it is looking for. We can evaluate it better in that condition

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [March 2, 2022, 8:20pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/7 "2022-03-02T20:20:09Z")

</div>

Does the Windows firewall allow certbot to listen on port 80 and serve clients? Or just your webapp?

I seem to remember you need to allow each app by itself, on Windows.

---

<div class="post-metadata">

**Author:** ![Rip](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rip/32/70863_2.png) [@Rip](https://community.letsencrypt.org/u/Rip)\
**Post date:** [March 2, 2022, 8:22pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/8 "2022-03-02T20:22:59Z")

</div>

Just an observation...

> **[Test result for pinkhas.hopto.org: Error](https://letsdebug.net/pinkhas.hopto.org/932562)**
>
> 2 unique issue(s) detected (ANotWorking, IssueFromLetsEncrypt)

```nohighlight
Nmap scan report for pinkhas.hopto.org (46.117.123.105)
Host is up (0.23s latency).
rDNS record for 46.117.123.105: 46-117-123-105.bb.netvision.net.il

PORT STATE SERVICE
22/tcp filtered ssh
53/tcp filtered domain
80/tcp filtered http
443/tcp filtered https

```

---

<div class="post-metadata">

**Author:** ![Pinkhas](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@Pinkhas](https://community.letsencrypt.org/u/Pinkhas)\
**Post date:** [March 2, 2022, 8:23pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/9 "2022-03-02T20:23:32Z")

</div>

defined it as "Any App" - port 80 is open  
I'll try to make an outbound rule aswell

---

<div class="post-metadata">

**Author:** ![Pinkhas](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@Pinkhas](https://community.letsencrypt.org/u/Pinkhas)\
**Post date:** [March 2, 2022, 8:25pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/10 "2022-03-02T20:25:49Z")

</div>

Ran, Output:

C:\WINDOWS\system32\>certbot -d [pinkhas.hopto.org](http://pinkhas.hopto.org) certonly --standalone --debug-challenge -v  
Saving debug log to C:\Certbot\log\letsencrypt.log  
Plugins selected: Authenticator standalone, Installer None  
Requesting a certificate for [pinkhas.hopto.org](http://pinkhas.hopto.org)  
Performing the following challenges:  
http-01 challenge for [pinkhas.hopto.org](http://pinkhas.hopto.org)

* * *

Challenges loaded. Press continue to submit to CA.

The following URLs should be accessible from the internet and return the value  
mentioned:

URL:  
[http://pinkhas.hopto.org/.well-known/acme-challenge/alzUuQrksKqVp9rkKVe0wpkFod1C1HwSsnpmmHl9aQ0](http://pinkhas.hopto.org/.well-known/acme-challenge/alzUuQrksKqVp9rkKVe0wpkFod1C1HwSsnpmmHl9aQ0)  
Expected value:  
alzUuQrksKqVp9rkKVe0wpkFod1C1HwSsnpmmHl9aQ0.sy6COMqEWsXkSUoZr-PnXJUvioeTCAQ1DOh0I2vvBDI

* * *

Press Enter to Continue

Waiting 🙂

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [March 2, 2022, 8:25pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/11 "2022-03-02T20:25:54Z")

</div>

That nmap scan is a lot better than the one I did earlier. There was not a single port answering.

Still timeout, @Pinkhas

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [March 2, 2022, 8:30pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/12 "2022-03-02T20:30:26Z")

</div>

Great. I can see the correct value using an AWS region in US East Coast (one Let's Encrypt server also in that AWS region).

But, [Let's Debug](https://letsdebug.net/pinkhas.hopto.org/932571?debug=y) also still cannot see it. It does similar method to Let's Encrypt. Could you have a geo block on Germany or other US areas? Let's Encrypt needs to challenge from several points around the globe (currently usually Germany and up to 3 US sites).

Sure seems like GEO based firewall - maybe in your ISP or router?

Here is my detailed results:

```nohighlight
curl -i http://pinkhas.hopto.org/.well-known/acme-challenge/alzUuQrksKqVp9rkKVe0wpkFod1C1HwSsnpmmHl9aQ0

HTTP/1.0 200 OK
Server: BaseHTTP/0.6 Python/3.9.7
Date: Wed, 02 Mar 2022 20:31:34 GMT

alzUuQrksKqVp9rkKVe0wpkFod1C1HwSsnpmmHl9aQ0.sy6COMqEWsXkSUoZr-PnXJUvioeTCAQ1DOh0I2vvBDI

```

---

<div class="post-metadata">

**Author:** ![Pinkhas](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@Pinkhas](https://community.letsencrypt.org/u/Pinkhas)\
**Post date:** [March 2, 2022, 8:34pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/13 "2022-03-02T20:34:02Z")

</div>

How can I check GEO blocking?  
Also, what can I do with your "detailed result"?

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [March 2, 2022, 8:37pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/14 "2022-03-02T20:37:02Z")

</div>

You cannot do anything with my 'detailed result'. Just providing more info to other volunteers to confirm what is happening. It just proves the standalone certbot server can be reached from someone.

Check your router for any geographic based firewall (that's what I meant by geo). I think @9peppe is in Italy so he is failing and also Let's Debug and Let's Encrypt which both try from Europe so might be the key pattern.

---

<div class="post-metadata">

**Author:** ![Pinkhas](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@Pinkhas](https://community.letsencrypt.org/u/Pinkhas)\
**Post date:** [March 2, 2022, 8:39pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/15 "2022-03-02T20:39:34Z")

</div>

On it - brb!  
Thanks for the tip!

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [March 2, 2022, 8:43pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/16 "2022-03-02T20:43:14Z")

</div>

I tried a global reachability website [test](https://www.site24x7.com/check-website-availability.html) and it's completely random. Sometimes it works sometimes it doesn't. It doesn't look like it's geographical.

---

<div class="post-metadata">

**Author:** ![Pinkhas](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@Pinkhas](https://community.letsencrypt.org/u/Pinkhas)\
**Post date:** [March 2, 2022, 8:48pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/17 "2022-03-02T20:48:52Z")

</div>

Used @9peppe 's tool, doesn't seem too odd - works with everything but Amsterdam  
Should I use a VPN to manipulate geoblocking?

---

<div class="post-metadata">

**Author:** ![Pinkhas](https://avatars.discourse-cdn.com/v4/letter/p/e47774/32.png) [@Pinkhas](https://community.letsencrypt.org/u/Pinkhas)\
**Post date:** [March 2, 2022, 8:49pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/18 "2022-03-02T20:49:55Z")

</div>

Also, should I terminate the last Certbot request? It is still waiting  
@MikeMcQ

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [March 2, 2022, 8:53pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/19 "2022-03-02T20:53:31Z")

</div>

It is a bit of a mess, I mean:

 ![immagine](https://global.discourse-cdn.com/letsencrypt/original/3X/9/7/9720087e3ab0f334a3ed5c431c117dd4cbe118f5.png)

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [March 2, 2022, 8:54pm UTC](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038/20 "2022-03-02T20:54:21Z")

</div>

> [@Pinkhas](#):
>
> should I terminate the last Certbot request?

No, fine to leave it while debugging it is helpful.

curl to that URL works for me every time from AWS EC2 East Coast. Yet another location at another provider on US East coast times out.

Maybe not geo but could your firewall be blocking requests with certain user-agents?

I don't know the site 9peppe used well enough to evaluate its results. My user-agent was curl from AWS but I will try some others

[Next page](https://community.letsencrypt.org/t/error-starting-certbot-likely-firewall-problem/173038.md?page=2)
