So I’m having a lot of problems trying to setup SSL with Let’s Encrypt. Previously I started this topic, as I’m setting up Discourse on an Ubuntu VM. Going to localhost in a broswer on my Ubuntu VM with Discourse installed does bring up the “Congratulations!” (when I try to NOT set up SSL in app.ym…

Is this an internet-connected server, or a VM on a local PC?

Did you take note of this [画像] Set up HTTPS support with Let's Encrypt Note: ./discourse-setup will enable Let’s Encrypt. And as of March 2017, you can run it again, and press return a few times and enter your email address ; the script will include the required templates and insert your email a…

@Stephen It’s a VM hosted on ProxMox VE 5.3 . The OS on the VM that I installed Discourse on is Ubuntu Server 18.04 LTS . ProxMox, and the VM itself, are both connected to the Internet. No problems there. Both have Static IPs properly assigned to them through my router. Note: ./discourse-setup wil…

[画像] Stephen: Is there a valid public DNS record pointed at the public IP of the server? Are :80 and :443 externally accessible on that hostname and IP? There indeed is. The Internal IP on the Discourse VM is 192.168.0.104. I created the DNS (let’s say its boards.myreserveddns.com ) and I assi…

Assuming you’ve configured your DNS and network correctly, the only things you need in your app.yml are: uncomment in templates: - "templates/web.ssl.template.yml" - "templates/web.letsencrypt.ssl.template.yml" uncomment in expose: - "443:443" # https add an email to LETSENCRYPT_ACCOUNT_…

Yes if discourse is the only site on the machine then you can just enable let’s encrypt with discourse-setup.

[画像] pfaffman: Yes if discourse is the only site on the machine then you can just enable let’s encrypt with discourse-setup. But, he doesn’t? In fact he said the opposite: [画像] naupe: I’ve got an Nginx VM that I need to have the External IP assigned to because I have multiple VMs set up …

[画像] Stephen: Assuming you’ve configured your DNS and network correctly, the only things you need in your app.yml are: uncomment in templates: - "templates/web.ssl.template.yml" - "templates/web.letsencrypt.ssl.template.yml" uncomment in expose: - "443:443" # https add an email to LETSENCR…

Ok, made some more progress. Been following THIS guide mostly, although I’ve followed THIS guide’s advice of not including the ssl_certificate nor the ssl_certificate_key in the Nginx CONF file, as nginx -t was reporting errors. nginx -t on the Nginx Server nor Discourse Rebuild are reporting error…

リバースプロキシの背後に Discourse をインストールする際の証明書利用

サポートインストール

Stephen (Stephen) 2019 年 5 月 9 日午前 4:09 5

You’ve skirted around answering my question somewhat.

Is there a valid public DNS record pointed at the public IP of the server? Are :80 and :443 externally accessible on that hostname and IP?

「いいね！」 1

Letsencyrpt setup fails for host with internal IP address

トピック		返信	表示
Discourse not serving pages Self-hosting	25	3004	2020 年 8 月 4 日
After Discourse installation can’t reach it in browser Self-hosting	24	4048	2020 年 9 月 5 日
Installing Discourse Behind Reverse Proxy using recommended (supported) installation Self-hosting	6	3547	2025 年 2 月 10 日
Run other websites on the same machine as Discourse Self-Hosting advanced-setup , how-to	66	137034	2025 年 2 月 23 日
Fresh install returning 502 Bad Gateway Self-hosting unsupported-install	28	851	2024 年 4 月 11 日

リバースプロキシの背後に Discourse をインストールする際の証明書利用

関連トピック