# HTTPS through Proxy; Discourse still trying to get files using HTTP

**URL:** <https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749>\
**Category:** Self-hosting\
**Created:** [April 3, 2020, 7:40pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749 "2020-04-03T19:40:58Z")\
**Posts on this page:** 1\
**Showing post:** 18

<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:** [April 3, 2020, 8:50pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/18 "2020-04-03T20:50:31Z")

</div>

Pretty much that, enable the template for HTTPS and let’s encrypt, make sure port 443 is exposed and specify an email before rebuilding.

There’s very few good reasons to put Discourse behind a proxy. If it has a dedicated server and FQDN it will be much easier to manage with the above.

---

_[View the full topic](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749)._