# 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:** 10

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [February 16, 2019, 10:02pm UTC](https://meta.discourse.org/t/reverse-proxy-and-https/109342/10 "2019-02-16T22:02:14Z")

</div>

If you aren’t encapsulating https in docker there’s no need to expose 443 at all. Your proxy can forward that.

---

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