# Discourse behind reverse proxy and https

**URL:** <https://meta.discourse.org/t/discourse-behind-reverse-proxy-and-https/148705>\
**Category:** Self-hosting\
**Created:** [April 21, 2020, 6:58am UTC](https://meta.discourse.org/t/discourse-behind-reverse-proxy-and-https/148705 "2020-04-21T06:58:13Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [April 22, 2020, 11:13am UTC](https://meta.discourse.org/t/discourse-behind-reverse-proxy-and-https/148705/11 "2020-04-22T11:13:30Z")

</div>

There we plenty of reasons to run behind a reverse proxy. I’m pretty sure that [Discourse.org](http://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).

> [@Grunskin](#):
>
> As I said in the first post `force_https` breaks the site,

This is your problem. You need to enable b force\_https and figure out why it’s breaking. Turning it off isn’t an option. You asked for free support and those who responded don’t have a solution for apache, so you’ll have to be the leader of the apache band.

---

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