# Timeout error on certbot (Nextcloud / Apache2 on Ubuntu)

**URL:** <https://community.letsencrypt.org/t/timeout-error-on-certbot-nextcloud-apache2-on-ubuntu/110302>\
**Category:** Help\
**Created:** [January 10, 2020, 7:28pm UTC](https://community.letsencrypt.org/t/timeout-error-on-certbot-nextcloud-apache2-on-ubuntu/110302 "2020-01-10T19:28:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![digiben](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@digiben](https://community.letsencrypt.org/u/digiben)\
**Post date:** [January 10, 2020, 7:28pm UTC](https://community.letsencrypt.org/t/timeout-error-on-certbot-nextcloud-apache2-on-ubuntu/110302/1 "2020-01-10T19:28:24Z")

</div>

First time trying to get Nextcloud to work, its all up and working but I need to get the SSL certificate up for google to trust it.

The domain is via asus, which dont give you ability to edit DNS records. ([https://squiznet.asuscomm.com](https://squiznet.asuscomm.com))  
This is a Ubuntu 18.04.3 LTS - Its the nextcloud manual installation method, with Apache2 for the web server

This is the error I keep getting. Keep in mind port 80 and 443 are being forwarded to the correct IP  
\*\> sudo certbot \*  
_\> Saving debug log to /var/log/letsencrypt/letsencrypt.log_  
_\> Plugins selected: Authenticator apache, Installer apache_  
\*\> \*  
_\> Which names would you like to activate HTTPS for?_  
_\> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -_  
_\> 1: [squiznet.asuscomm.com](http://squiznet.asuscomm.com)_  
_\> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -_  
_\> Select the appropriate numbers separated by commas and/or spaces, or leave input_  
\*\> blank to select all options shown (Enter ‘c’ to cancel): \*  
_\> Obtaining a new certificate_  
_\> Performing the following challenges:_  
_\> http-01 challenge for [squiznet.asuscomm.com](http://squiznet.asuscomm.com)_  
_\> Waiting for verification…_  
_\> Cleaning up challenges_  
_\> Failed authorization procedure. [squiznet.asuscomm.com](http://squiznet.asuscomm.com) (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [http://squiznet.asuscomm.com/.well-known/acme-challenge/i79eW7A0\_gXCPD0ATyZKl9s\_IAWKMUfYckAIbzwM8Ro:](http://squiznet.asuscomm.com/.well-known/acme-challenge/i79eW7A0_gXCPD0ATyZKl9s_IAWKMUfYckAIbzwM8Ro:) Timeout during connect (likely firewall problem)_  
\*\> \*  
_\> IMPORTANT NOTES:_  
_\> - The following errors were reported by the server:_  
\*\> \*  
_\> Domain: [squiznet.asuscomm.com](http://squiznet.asuscomm.com)_  
_\> Type: connection_  
_\> Detail: Fetching_  
_\> [http://squiznet.asuscomm.com/.well-known/acme-challenge/i79eW7A0\_gXCPD0ATyZKl9s\_IAWKMUfYckAIbzwM8Ro:](http://squiznet.asuscomm.com/.well-known/acme-challenge/i79eW7A0_gXCPD0ATyZKl9s_IAWKMUfYckAIbzwM8Ro:)_  
_\> 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._

Anyone have any suggestions where I am going wrong? Could it be permissions?

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [January 10, 2020, 7:33pm UTC](https://community.letsencrypt.org/t/timeout-error-on-certbot-nextcloud-apache2-on-ubuntu/110302/2 "2020-01-10T19:33:31Z")

</div>

Hi @digiben

> [@digiben](#):
>
> Failed authorization procedure. [squiznet.asuscomm.com](http://squiznet.asuscomm.com) (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [http://squiznet.asuscomm.com/.well-known/acme-challenge/i79eW7A0\_gXCPD0ATyZKl9s\_IAWKMUfYckAIbzwM8Ro:](http://squiznet.asuscomm.com/.well-known/acme-challenge/i79eW7A0_gXCPD0ATyZKl9s_IAWKMUfYckAIbzwM8Ro:) Timeout during connect (likely firewall problem)

there are checks of your domain, 20 minutes old and yesterday - [https://check-your-website.server-daten.de/?q=squiznet.asuscomm.com](https://check-your-website.server-daten.de/?q=squiznet.asuscomm.com)

Only Timeouts:

| Domainname | Http-Status | redirect | Sec. | G |
| --- | --- | --- | --- | --- |
| • [http://squiznet.asuscomm.com/](http://squiznet.asuscomm.com/) 2.25.158.124 | -14 | | 10.046 | T |
| Timeout - The operation has timed out | | | | |
| | | | | |
| • [https://squiznet.asuscomm.com/](https://squiznet.asuscomm.com/) 2.25.158.124 | -14 | | 10.047 | T |
| Timeout - The operation has timed out | | | | |
| | | | | |
| • [http://squiznet.asuscomm.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://squiznet.asuscomm.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) 2.25.158.124 | -14 | | 10.043 | T |
| Timeout - The operation has timed out | | | | |

Your port 80 must answer.

But why do you need a new certificate. There is one, created 2019-12-30 13:36:31.

| Issuer | not before | not after | Domain names | LE-Duplicate | next LE |
| --- | --- | --- | --- | --- | --- |
| Let's Encrypt Authority X3 | 2019-12-30 | 2020-03-29 | [squiznet.asuscomm.com](http://squiznet.asuscomm.com) - 1 entries | | |

Works http internal?

```nohighlight
curl http://squiznet.asuscomm.com/

```

from that machine?

---

<div class="post-metadata">

**Author:** ![digiben](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@digiben](https://community.letsencrypt.org/u/digiben)\
**Post date:** [January 10, 2020, 7:41pm UTC](https://community.letsencrypt.org/t/timeout-error-on-certbot-nextcloud-apache2-on-ubuntu/110302/3 "2020-01-10T19:41:21Z")

</div>

That one was when I used the snap installation of nextcloud, but I had to dump that install when it wouldnt allow me to look outside its container. So this is a new install, and I dont have that certificate (wish I had made a copy!)

No that curl failed no you mention it. Does it matter that I have apache set to redirect port 80 to 443?

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [January 10, 2020, 8:46pm UTC](https://community.letsencrypt.org/t/timeout-error-on-certbot-nextcloud-apache2-on-ubuntu/110302/4 "2020-01-10T20:46:52Z")

</div>

> [@digiben](#):
>
> Does it matter that I have apache set to redirect port 80 to 443?

That's not a problem if your configuration is correct.

But port 80 must answer. No answer -\> no http validation.

Read

> **[How It Works - Let's Encrypt](https://letsencrypt.org/how-it-works/)**
>
> The objective of Let’s Encrypt and the ACME protocol is to make it possible to set up an HTTPS server and have it automatically obtain a browser-trusted certificate, without any human intervention. This is accomplished by running a certificate...

then

> **[Challenge Types - Let's Encrypt](https://letsencrypt.org/docs/challenge-types/)**
>
> When you get a certificate from Let’s Encrypt, our servers validate that you control the domain names in that certificate using “challenges,” as defined by the ACME standard. Most of the time, this validation is handled automatically by your ACME...

---

<div class="post-metadata">

**Author:** ![digiben](https://avatars.discourse-cdn.com/v4/letter/d/d6d6ee/32.png) [@digiben](https://community.letsencrypt.org/u/digiben)\
**Post date:** [January 10, 2020, 10:55pm UTC](https://community.letsencrypt.org/t/timeout-error-on-certbot-nextcloud-apache2-on-ubuntu/110302/5 "2020-01-10T22:55:00Z")

</div>

Cheers for that, just need to figure out why the port is blocked.

Nextcloud doesnt want to respond on http 80, i cant see any reason why in the conf files at all. even when i turn off the https redirect, its still not going past the apache error screen

---

<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:** [February 9, 2020, 10:55pm UTC](https://community.letsencrypt.org/t/timeout-error-on-certbot-nextcloud-apache2-on-ubuntu/110302/6 "2020-02-09T22:55:07Z")

</div>

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