# Reverse Proxy and HTTPS

**URL:** <https://meta.discourse.org/t/reverse-proxy-and-https/109342>\
**Category:** 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:** 8

<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, 8:06pm UTC](https://meta.discourse.org/t/reverse-proxy-and-https/109342/8 "2019-02-16T20:06:40Z")

</div>

The only explanation I have for you sounds like this:

You’re using a complex setup.  
I run my discourse behind an nginx reverse proxy  
I followed a guide here on meta to configure my proxy  
It said that you have to terminate ssl to rp and forward requests to Discourse over port 80 (or socket in my case)

What I know of the internet is that You can’t reverse proxy SSL certificates.

That’s the best I have for You, can’t help any more than that.

EDIT: this is the guide I’m talking about: [Add an offline page to display when Discourse is rebuilding or starting up](https://meta.discourse.org/t/adding-an-offline-page-when-rebuilding/45238)

---

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