# Discourse HTTPS Web Socket

**URL:** https://meta.discourse.org/t/discourse-https-web-socket/225805
**Category:** Self-hosting
**Created:** [May 1, 2022, 1:58pm UTC](https://meta.discourse.org/t/discourse-https-web-socket/225805 "2022-05-01T13:58:08Z")
**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: [May 1, 2022, 6:01pm UTC](https://meta.discourse.org/t/discourse-https-web-socket/225805/8 "2022-05-01T18:01:37Z")

</div>

Literally thousands of people host other services on the same server as discourse. There are ways to do this. If you do your research, it is a very well supported usecase. You need to put it behind a reverse proxy to achieve it.

Here is one way of doing it [Run other websites on the same machine as Discourse](https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247)

I have my public discourse sandbox hosted on a NUC which hosts multiple other services behind Nginx Proxy Manager but that’s my way of doing it. It isn’t officially supported but I know my way around it.

---

_[View the full topic](https://meta.discourse.org/t/discourse-https-web-socket/225805)._