# Reverse Proxy Into Discourse

**URL:** https://meta.discourse.org/t/reverse-proxy-into-discourse/331164
**Category:** Self-hosting
**Created:** [October 16, 2024, 1:44pm UTC](https://meta.discourse.org/t/reverse-proxy-into-discourse/331164 "2024-10-16T13:44:14Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![mjbergman92](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mjbergman92/32/456324_2.png) [@mjbergman92](https://meta.discourse.org/u/mjbergman92)
#### Post date: [October 16, 2024, 4:16pm UTC](https://meta.discourse.org/t/reverse-proxy-into-discourse/331164/13 "2024-10-16T16:16:03Z")

</div>

I was able to do so in the GUI as I mentioned before.

@Falco, @pfaffman, @Jagster, @merefield… thanks to you all, I have successfully setup the reverse proxy and I no longer have those Mixed Content errors.

Once I reverse proxied into port 80 of the discourse VM and I was able to register and such, it came down to setting force\_https using the GUI and adding the x-forwarded-proto flag in the advanced tab of nginx proxy manager.

---

_[View the full topic](https://meta.discourse.org/t/reverse-proxy-into-discourse/331164)._