Error at LetsEncrypt validation

[MihaVuk]

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

This guide is only for existing installs where HTTPS is not enabled. Following the official setup guide 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? Is everything else on your site ready for HTTPS? Before you start, please bear in mind that for HTTPS to work properly, every single resource on the page must be HTTPS compatible. Consider your CDN, your social logins, your…

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:Verify error:Fetching 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.

[pfaffman (Jay Pfaffman)]

Did you read the first sentence in that guide that says that if you’re doing a standard install you don’t need to follow that guide?

Is this a recent standard install? Did you run discourse-setup?

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

[supermathie (Michael Brown)]

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

○ → 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.

[MihaVuk]

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?

[MihaVuk]

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