Hey there! I just attempted to setup my Discourse Forum. When I clicked the link in the E-Mail I saw a button, but couldn’t press it. I saw quite a bunch of errors which seems to be there because it’s trying to load files over HTTP. This may be caused by the fact that I’m not using HTTPS through Discourse but rather through my apache2 Webserver using a ProxyPass. How can I make it request the files ofer HTTPS without using Discourse’s HTTPS? (Or tell me a way to use my already to easily existing .crt and .key Files with Discourse that would work as well :wink:) [image]

Didn’t know this was enabled. Thanks! It’s all working now finally! For anyone else, those are the steps I did: [image] CRUGG: I just noticed that I can just enable HTTPs via Discourse and since Discourse is running on the Default Ports, I can just put community.website.tld on the IP of Server 2. [image] Stephen: Turn Cloudflare off for now. Unless you’re frequently attacked it’s a cause of more hurt than good. If the orange cloud is enabled Discourse can’t enrol the certificate from Let’s Encrypt. [image] codinghorror: Turn off cloudflare rocket loader. It’s breaking your site, as you can see in the error message.

You Just have to go to settings and enable the checkbox that says force https. Just to be clear, be 100% sure that your reverse proxy can handle ssl for discourse before enabling that setting. :warning: Discourse doesn’t play nice with apache2 … If possible move to nginx.

Wait what Settings? Where the hell would I find a checkbox?

community.example.net/admin is the path where you’ll find your Discourse admin panel.

But for that I need an Account on my Forum first, which I can’t create without fixing the HTTPS Issue

You can enable force SSL via console: ./launcher enter app rails c SiteSetting.force_https = true exit exit

Do I have to rebuild or do anything after that? Edit: I’ve rebuilded. Still get that same error that some files are still loaded via HTTP

force_https was removed from the admin UI as it caused more confusion than anything else. As discourse installs https by default now, it’s only cases like this one where it needs to be enabled manually.

It wasn’t enabled by default for me. I was having trouble using the installer script so I edited the app.yml. Is this the reason?

Are you doing HTTP behind the proxy by disabling the template for HTTPS?

The two HTTPS Templates were disabled by default for me. Discourse is running on the two default Ports on Server 2 I’m then using a ProxyPass in an apache2 (running on Server 1) VHost where SSL is configured. I just noticed that I can just enable HTTPs via Discourse and since Discourse is running on the Default Ports, I can just put community.website.tld on the IP of Server 2. How would I go about enabling SSL? Uncomment the two templates and then enter the LetsEncrypt E-Mail? Also, how do I create an Account on LetsEncrypt? I can’t find any “Register” Button on their website.

HTTPS through Proxy; Discourse still trying to get files using HTTP

Product Support Self-hosting

riking (Kane York) April 3, 2020, 9:19pm 22

Make sure that the proxy is setting the X-Forwarded-Proto header to https appropriately, which should fix https detection.

Topic		Replies	Views
Login-button unsecured Self-hosting	5	590	February 2, 2021
Set up HTTPS support with Let's Encrypt Self-Hosting how-to , domains	2	111646	February 25, 2024
Discourse without SSL? SSL in apache2 proxy Self-hosting	4	2761	December 10, 2019
How do I configure Discourse behind an AWS or Google Cloud Proxy with SSL Self-hosting	20	3637	March 25, 2019
Trouble enabling https for hosted instance Product Support	3	1130	May 12, 2016

HTTPS through Proxy; Discourse still trying to get files using HTTP

Related topics