# Issue Onebox in HTTPS

**URL:** <https://meta.discourse.org/t/issue-onebox-in-https/57904>\
**Category:** Self-hosting\
**Created:** [February 24, 2017, 3:45pm UTC](https://meta.discourse.org/t/issue-onebox-in-https/57904 "2017-02-24T15:45:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [February 24, 2017, 4:13pm UTC](https://meta.discourse.org/t/issue-onebox-in-https/57904/6 "2017-02-24T16:13:09Z")

</div>

> [@Trash](#):
>
> Do you confirm that even if discourse runs through sock, and so the “ssl template” is commented out, everything should work fine?

I’m not really a fan of running reverse proxy in self-hosted environments, unless you are very comfortable with your reverse proxy of choice.

That said, if you have all the correct headers set, it will work.

---

_[View the full topic](https://meta.discourse.org/t/issue-onebox-in-https/57904)._