I’m trying to setup Discourse behind my Apache reverse proxy but I can’t get it working properly with https. I’ve had a lot of problems getting this far. Right now I have Discourse on a server and an Apache server infront of it acting as a reverse proxy. I had a lot of problems getting it to run be…

Apache2 will give you a lot of issues. Consider switching to nginx or caddy or traefik or haproxy

[Bild] Grunskin: Checking the force https flag in Discourse doesn’t help either, it will just break the site since it will just ignore everything over http. What should I do to get rid of the mixed content? I got Apache2 working “no problem” in a test bed with Apache2 as a reverse proxy to a…

Thanks for the reply’s but I don’t have Apache on the same server as Discourse. I might not have been to clear about that. I have an existing Apache server with a bunch of websites and I need it to reverse proxy Discourse located on a different server so I can’t use sockets.

[Bild] Grunskin: I have an existing Apache server with a bunch of websites and I need it to reverse proxy Discourse located on a different server so I can’t use sockets. Cheers. I have not tried this method, but you might consider mounting your remote file system and see if you can access a …

The last time I tried using that config with apache2, I was getting connection failures to the discourse message bus. It was over an year ago at this point tho. It appears as if the side is loading fine but in the F12 developer console it clearly stated that wss connections timed out after a few ini…

[Bild] itsbhanusharma: it clearly stated that wss connections timed out after a few initial tries. You can clearly see in the example configuration I posted, we did not use wss wss !== apache2 reverse proxy (it’s only one way to do it, and we don’t use wss) In fact, we only use ngnix and a…

Why is this necessary? Discourse is an application, not a website. Once the initial javascript payload has been delivered to your browser many of the features rely on a snappy connection to the discourse server. Proxying via another system is going to introduce latency and seriously degrade user ex…

There are plenty of reasons for using a reverse proxy. For example if I only have 1 public IP and need multiple webservers to be public on port 80/443, and I can’t run Discourse for this example on that particular webserver. Use it as SSL Offloading so the end-server doesn’t have to deal with encr…

I suggest to take a look to Traefik. It works great and manages SSL certificates automatically.

There we plenty of reasons to run behind a reverse proxy. I’m pretty sure that Discourse.org ’s infrastructure runs behind HAproxy. I use treafik and vcaddyserver, and have made nginx, HAproxy, and even apache work in the past (for a subfolder install query wordpress). [Bild] Grunskin: As I sai…

Diskurs hinter Reverse Proxy und HTTPS

Unterstützung Installation

neounix (Dark Matter) 21. April 2020 um 08:16 3

Ich habe Apache2 in einem Testsystem „ohne Probleme

Discourse + web server. Possible or better to avoid?

Thema		Antworten	Aufrufe
I want to install using a reverse proxy for Apache Self-hosting	13	4684	8. August 2021
Apache w/ SSL + Discourse: Next steps? Self-hosting	10	1862	18. Juli 2020
Installing Discourse Behind Reverse Proxy using recommended (supported) installation Self-hosting	7	3918	6. Mai 2026
Mixed SSL since upgrade Self-hosting	13	777	30. Dezember 2022
Run other websites on the same machine as Discourse Self-Hosting how-to , advanced-setup	66	138265	30. Juni 2026

Diskurs hinter Reverse Proxy und HTTPS

Verwandte Themen