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 Self-Hosting 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 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? 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: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.

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.

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.

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?

שגיאה באימות LetsEncrypt

תמיכה

MihaVuk (Miha Vuk) 13 באפריל,‏ 2022,‏ 12:18pm 5

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

נושא		תגובות	צפיות
Set up HTTPS support with Let's Encrypt Self-Hosting how-to , domains	2	111866	25 בפברואר,‏ 2024
No connection accepted on http / https after fresh installation on Ubuntu 22.04 LTS Self-hosting	5	2624	16 בדצמבר,‏ 2022
HTTPS : issue while trying to set up SSL certification Self-hosting	24	2758	31 באוגוסט,‏ 2019
Fresh installation with Let’s Encrypt errors Self-hosting	18	4494	26 בדצמבר,‏ 2019
Let's encrypt failing for IP behind firewall Self-hosting unsupported-install	7	1356	7 ביוני,‏ 2023

שגיאה באימות LetsEncrypt

נושאים קשורים