I really hate to do something out of the ordinary here. I hate it as much as anyone else, but it’s all I know how to do and how every other self-hosted app I have is running. I have my wildcard A record pointing to an internal IP on my network which has port 80 and 443 exported by nginx proxy manag…

I am looking at the dns-01 challenge option mentioned here. [image] HTTPS for local network only Help Welcome to the Let's Encrypt Community, Henry 🙂 You could use dns-01 challenges that use TXT records created in your public…

There are some topics about running Discourse behind nginx proxy manager. Basically, you configure Discourse not to bind to any ports and add the requisite labels in a labels: section in your app.yml.

If I go the nginx proxy manager route, which is how i have it setup right now (as opposed to setting up lets encrypt on the discourse VM itself)… [image] Jay Pfaffman: Basically, you configure Discourse not to bind to any ports and add the requisite labels in a labels: section in your app.yml. …

I am going to try the socketd template mentioned here along with the config for nginx proxy manager in the advanced tab here .

[image] Malachi Bergman: I do not think this is possible to get rid of since the http:// references in the code are hard coded… or am i wrong? is that what this labels field you referenced would change? There is a setting called force_https that you need to enable, either via ENV or rails con…

I will try that if the Unix socket setup does not work. Thank you @Falco and @pfaffman for the support. I will get back with what works.

I can not do the Unix socket setup… my discourse VM is on a separate machine. back to the original plan. Let me see if i can figure out the force_https enabling with some other posts on the forum. FYI, this is the step I can not do.

[image] Falco: x-forwarded-proto You actually need what Falco suggested.

in nginx proxy manager: proxy_set_header X-Forwarded-Proto $scheme;

Reverse Proxy Into Discourse

Product Support Self-hosting

merefield (Robert) October 16, 2024, 4:12pm 12

DISCOURSE_FORCE_HTTPS=true I believe (env)
or
DISCOURSE_FORCE_HTTPS: true in app.yml in ENV section.

Topic		Replies	Views
Cannot get Discourse to install behind Nginx-proxy-manager Self-hosting	2	2074	March 12, 2020
Discourse with reverse proxy manager Self-hosting	5	341	November 8, 2025
Discourse behind reverse proxy and https Self-hosting	18	7738	March 13, 2022
Using a certificate when Discourse is installed behind a reverse proxy Self-hosting unsupported-install	24	5358	May 17, 2019
Wanting to run Discourse alongside apache Self-hosting	12	2225	August 8, 2019

Reverse Proxy Into Discourse

Related topics