# Reverse Proxy and HTTPS

**URL:** <https://meta.discourse.org/t/reverse-proxy-and-https/109342>\
**Category:** Product Support\
**Tags:** unsupported-install\
**Created:** [February 16, 2019, 7:26pm UTC](https://meta.discourse.org/t/reverse-proxy-and-https/109342 "2019-02-16T19:26:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)\
**Post date:** [February 16, 2019, 7:32pm UTC](https://meta.discourse.org/t/reverse-proxy-and-https/109342/2 "2019-02-16T19:32:18Z")

</div>

First thing I’d check is the reverse proxy configuration.

What You should really be doing is to proxy the HTTPS to HTTP and then manage SSL through reverse proxy

My best guess in this case is that discourse is unable to generate SSL due to the complex setup and that’s why it is not available over HTTPS

---

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