# Fixing SSL mixed content errors with external NGINX proxy via UNIX socket

**URL:** <https://meta.discourse.org/t/fixing-ssl-mixed-content-errors-with-external-nginx-proxy-via-unix-socket/134683>\
**Category:** Self-hosting\
**Created:** [November 29, 2019, 6:24am UTC](https://meta.discourse.org/t/fixing-ssl-mixed-content-errors-with-external-nginx-proxy-via-unix-socket/134683 "2019-11-29T06:24:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [November 29, 2019, 6:32am UTC](https://meta.discourse.org/t/fixing-ssl-mixed-content-errors-with-external-nginx-proxy-via-unix-socket/134683/2 "2019-11-29T06:32:19Z")

</div>

There is a site setting force\_https. You might set this env variable

```
DISCOURSE_FORCE_HTTPS=true

```

---

_[View the full topic](https://meta.discourse.org/t/fixing-ssl-mixed-content-errors-with-external-nginx-proxy-via-unix-socket/134683)._
