# Timeout during connect (likely firewall problem)

**URL:** <https://community.letsencrypt.org/t/timeout-during-connect-likely-firewall-problem/183974>\
**Category:** Help\
**Created:** [September 5, 2022, 1:36pm UTC](https://community.letsencrypt.org/t/timeout-during-connect-likely-firewall-problem/183974 "2022-09-05T13:36:54Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![166166cc161f1f11161f](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/166166cc161f1f11161f/32/63731_2.png) [@166166cc161f1f11161f](https://community.letsencrypt.org/u/166166cc161f1f11161f)\
**Post date:** [September 5, 2022, 1:36pm UTC](https://community.letsencrypt.org/t/timeout-during-connect-likely-firewall-problem/183974/1 "2022-09-05T13:36:55Z")

</div>

I do not understand the world anymore ...  
Can someone help me I just can't get any further..  
what information do you need?

Danke!!!

Which names would you like to activate HTTPS for?

* * *

1: …………...dns-jack.net

* * *

Select the appropriate numbers separated by commas and/or spaces, or leave input  
blank to select all options shown (Enter 'c' to cancel): 1  
Requesting a certificate for [meinhost.dns-jack.net](http://meinhost.dns-jack.net)

Certbot failed to authenticate some domains (authenticator: apache). The Certifi cate Authority reported these problems:  
Domain: [meinhost.dns-jack.net](http://meinhost.dns-jack.net)  
Type: connection  
Detail: 78.43.40.5: Fetching http://.............dns-jack.net/.well-known/acme-cha llenge/5EQMpwBk9wPNAoIXMO1bOBL3CLST0aJieO7oniOfQDs: Timeout during connect (like ly firewall problem)

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

Some challenges have failed.  
Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org). See t he logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for mo re 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:** [September 5, 2022, 1:46pm UTC](https://community.letsencrypt.org/t/timeout-during-connect-likely-firewall-problem/183974/2 "2022-09-05T13:46:52Z")

</div>

Welcome to the community @166166cc161f1f11161f

The Let's Encrypt server is not able to contact your server to verify the request.

I do not see port 80 (or 443) open to your server. Do you have a router that connects to your ISP? If so, make sure ports are open and forwarded as needed to your server.

Check any firewall you have to be sure these ports are open. Port 80 needs to be open for the HTTP challenge to work. Port 443 is the normal port for https requests once you get your cert and configured.

Maybe check to be sure you don't block IP addresses from certain parts of the world (often called GEO block).

```nohighlight
Nmap scan report for meinhost.dns-jack.net (78.43.40.5)
rDNS record for 78.43.40.5: ip-078-043-040-005.um18.pools.vodafone-ip.de
PORT STATE SERVICE
80/tcp filtered http
443/tcp filtered https

```

Note: I checked your IPv4 address even though you also have an IPv6 address in your DNS. The IPv6 fails in such a way that certbot then tries IPv4 (so that's what I checked). You might have something wrong with IPv6 too.

---

<div class="post-metadata">

**Author:** ![166166cc161f1f11161f](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/166166cc161f1f11161f/32/63731_2.png) [@166166cc161f1f11161f](https://community.letsencrypt.org/u/166166cc161f1f11161f)\
**Post date:** [September 5, 2022, 2:06pm UTC](https://community.letsencrypt.org/t/timeout-during-connect-likely-firewall-problem/183974/3 "2022-09-05T14:06:31Z")

</div>

First of all thanks for the quick reply!  
I have to, I'm quite new to this topic and not a computer person.  
I installed an Ubuntu server and set up Nextcloud and followed the instructions, I think Nextcloud works, but I can't get an SSH certificate.  
I have a Fritz box as a red one and ports 80 and 443 are open there

nano /etc/apache2/sites-available/nextcloud.conf  
\<VirtualHost \*:80\>  
ServerAdmin batbat@t-online  
DocumentRoot /var/www/nextcloud/  
ServerName [meinhost.dns-jack.net](http://meinhost.dns-jack.net)  
ServerAlias

```
 <Directory /var/www/nextcloud/>
    Options +FollowSymlinks
    AllowOverride All
    Require all granted
      <IfModule mod_dav.c>
        Dav off
      </IfModule>
    SetEnv HOME /var/www/nextcloud
    SetEnv HTTP_HOME /var/www/nextcloud
 </Directory>

 ErrorLog ${APACHE_LOG_DIR}/error.log
 CustomLog ${APACHE_LOG_DIR}/access.log combined

```

I am sure that I am still missing further settings but how and where???  
would be nice if you could help me

---

<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:** [September 5, 2022, 2:12pm UTC](https://community.letsencrypt.org/t/timeout-during-connect-likely-firewall-problem/183974/4 "2022-09-05T14:12:51Z")

</div>

Does your ISP allow inbound requests to you on ports 80 and 443?

Some ISP's block residential accounts from these ports.

You must have a working HTTP site to get a cert using the HTTP challenge. There's not much I can do than offer general advice about getting your site visible to the public internet.

You can use the [Let's Debug test site](https://letsdebug.net) to help work through initial setup problems. Once you get a successful test you should be able to get a cert.

---

<div class="post-metadata">

**Author:** ![166166cc161f1f11161f](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/166166cc161f1f11161f/32/63731_2.png) [@166166cc161f1f11161f](https://community.letsencrypt.org/u/166166cc161f1f11161f)\
**Post date:** [September 5, 2022, 2:16pm UTC](https://community.letsencrypt.org/t/timeout-during-connect-likely-firewall-problem/183974/5 "2022-09-05T14:16:49Z")

</div>

Thanks !!  
I'm open to any advice.  
i will try .

---

<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:** [September 5, 2022, 2:22pm UTC](https://community.letsencrypt.org/t/timeout-during-connect-likely-firewall-problem/183974/6 "2022-09-05T14:22:44Z")

</div>

Other than checking with your ISP. You might want to try a nextcloud forum. They might have good advice on getting your initial setup working.

---

<div class="post-metadata">

**Author:** ![166166cc161f1f11161f](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/166166cc161f1f11161f/32/63731_2.png) [@166166cc161f1f11161f](https://community.letsencrypt.org/u/166166cc161f1f11161f)\
**Post date:** [September 5, 2022, 2:23pm UTC](https://community.letsencrypt.org/t/timeout-during-connect-likely-firewall-problem/183974/7 "2022-09-05T14:23:47Z")

</div>

Thanks !!  
I'm open to any advice.  
i will try .

---

<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:** [October 5, 2022, 2:24pm UTC](https://community.letsencrypt.org/t/timeout-during-connect-likely-firewall-problem/183974/8 "2022-10-05T14:24:20Z")

</div>

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