Hello there, trying to setup discourse with reverse proxy manager on nginx on one machine. Everything is accessible through my dns using default ports on the box but when setting up with reverse proxy to route traffic through my sub domain with ssl forced, it, simply does not work. I get a 502. I’m running multiple containers. proxy manager being isolated and everything discourse in another. I’ve looked through pretty much every guide I can find and nothing, works. There’s gotta be a way to successfully do this in 2025! I’ve got one site running with proxy manager and that all checks out. Do I need to hand over fpm network to discourse containers as that’s the default network that proxy manager uses to make discourse containers accessible to proxy manager? If so, where do I need to go to put that in as I cannot find any info. People say to put it in their setups but not knowing exactly where. ? I do not wanna have to change setups. I’ve seen some guides saying to not expose ports and let proxy manager do the rest, done that. I’ve seen guides saying to try and use web.socketed templates.yml in discourse/templates dir but that don’t work neither. I’ve seen people getting this to work with and with out exposing ports on discourse. Nothing seems to be consistent here. What works, and what works well nowadays. Remember ,I’m only running off of one, box.
1 Like