# Error at LetsEncrypt validation

**URL:** https://meta.discourse.org/t/error-at-letsencrypt-validation/223921
**Category:** Support
**Created:** [April 11, 2022, 3:45pm UTC](https://meta.discourse.org/t/error-at-letsencrypt-validation/223921 "2022-04-11T15:45:58Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![MihaVuk](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@MihaVuk](https://meta.discourse.org/u/MihaVuk)
#### Post date: [April 11, 2022, 3:45pm UTC](https://meta.discourse.org/t/error-at-letsencrypt-validation/223921/1 "2022-04-11T15:45:58Z")

</div>

I have setup the self-hosted Docker environment and enabled HTTPS using Let’s Encrypt following the tutorial.

> [@Set up HTTPS support with Let's Encrypt](https://meta.discourse.org/t/setting-up-https-support-with-lets-encrypt/40709):
>
> bookmark This is a guide for enabling HTTPS on an existing Discourse installation using Let’s Encrypt. It assumes prior installation without HTTPS enabled. person_raising_hand Required user level: System Administrator exclamation This guide is only for existing installs where HTTPS is not enabled. Following the [official setup guide](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md) automatically enables HTTPS by default. So you’d like to add https to your Discourse absolutely free, courtesy of our friends at [Let’s Encrypt?](https://letsencrypt.org/)bell I…

It always fails on the step below. Setup without HTTPS works fine and the forum is publicly available on HTTP.

root@discoursetest3-app:/shared/letsencrypt# cat acme.sh.log  
…  
[Mon 11 Apr 2022 02:56:35 PM UTC] [discourse-test3.docentric.com](http://discourse-test3.docentric.com):Verify error:Fetching [http://discourse-test3.docentric.com/.well-known/acme-challenge/iEFjgyseuVL1IzIrTjmfhwv0HqV7EgUmQUVhy1nmnCE:](http://discourse-test3.docentric.com/.well-known/acme-challenge/iEFjgyseuVL1IzIrTjmfhwv0HqV7EgUmQUVhy1nmnCE:) **Timeout after connect (your server may be slow or overloaded)**

It seems that ACME challenge is not accessible.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 11, 2022, 4:04pm UTC](https://meta.discourse.org/t/error-at-letsencrypt-validation/223921/2 "2022-04-11T16:04:14Z")

</div>

Did you read the first sentence in that guide that says that if you’re doing a [standard install](https://meta.discourse.org/t/142537?silent=true) you don’t need to follow that guide?

Is this a recent [standard install](https://meta.discourse.org/t/142537?silent=true)? Did you run `discourse-setup`?

It looks like you may have port 80 (and perhaps also port 443) blocked for incoming connections.

---

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [April 11, 2022, 4:26pm UTC](https://meta.discourse.org/t/error-at-letsencrypt-validation/223921/3 "2022-04-11T16:26:19Z")

</div>

Oddly, the first works but the second doesn’t:

```plaintext
○ → curl http://discourse-test3.docentric.com/srv/status
ok

○ → timeout -v 5s curl http://discourse-test3.docentric.com/.well-known/acme-challenge/iEFjgyseuVL1IzIrTjmfhwv0HqV7EgUmQUVhy1nmnCE
timeout: sending signal TERM to command ‘curl’

```

I’m not sure what would cause that if it’s a standard setup.

---

<div class="post-metadata">

### Author: ![MihaVuk](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@MihaVuk](https://meta.discourse.org/u/MihaVuk)
#### Post date: [April 12, 2022, 8:37am UTC](https://meta.discourse.org/t/error-at-letsencrypt-validation/223921/4 "2022-04-12T08:37:32Z")

</div>

It is an old test installation without HTTPS and now I would like to enable HTTPS.  
I have tried to edit app.yml manually and also to run discourse-setup. In both cases the same error.  
I have also tried to delete Discourse (containers and files) and install from scratch, but the result is the same.

I agree that it looks that port 80 in not available, but if I comment the following two lines in app.yml, the forum runs on HTTP without problem.

- “templates/web.ssl.template.yml”
- “templates/web.letsencrypt.ssl.template.yml”

Where on the disk are static files like [http://discourse-test3.docentric.com/.well-known/acme-challenge/iEFjgyseuVL1IzIrTjmfhwv0HqV7EgUmQUVhy1nmnCE](http://discourse-test3.docentric.com/.well-known/acme-challenge/iEFjgyseuVL1IzIrTjmfhwv0HqV7EgUmQUVhy1nmnCE)?

---

<div class="post-metadata">

### Author: ![MihaVuk](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@MihaVuk](https://meta.discourse.org/u/MihaVuk)
#### Post date: [April 13, 2022, 12:18pm UTC](https://meta.discourse.org/t/error-at-letsencrypt-validation/223921/5 "2022-04-13T12:18:47Z")

</div>

It has turned out that just ACME protocol was blocked on the company firewall. Now it works 🙂

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [May 13, 2022, 12:19pm UTC](https://meta.discourse.org/t/error-at-letsencrypt-validation/223921/6 "2022-05-13T12:19:17Z")

</div>

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