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

<div class="post-metadata">

**Author:** ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)\
**Post date:** [May 1, 2022, 8:33pm UTC](https://meta.discourse.org/t/discourse-https-web-socket/225805/12 "2022-05-01T20:33:40Z")

</div>

No, I don’t understand a bit about docker. But when I had a discourse at same VPS where I had Nginx and Varnish before Discourse I used sock without issues. But is it different thing?

Nowadays I have Discourse on different VPS than where is Nginx/Varnish so I can’t use socket. That’s why Varnish sends everyone to port 82 and from there to VPS of Discourse. And that’s why I have:

```plaintext
 expose:
  - "82:80"

```

But is even that totally different thing than Discourse can use only ports 80/443?

---

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