Hey, Anyone can guide or provide examples how to set up web socket with HTTPS for Discourse? Simple HTTP works, but I would need it over HTTPS.

FWIW, as I read from your other post, this might be worth a shot [이미지] Install Discourse on a residential internet with Cloudflare Tunnel Sysadmins Since Discourse now has support for running on a Raspberry Pi , running a small instance in your home lab will be…

Not really, I run other websites just fine over 80/443 as I said, I am already running websites with LiteSpeed, even mail server is not blocked. I even tried with 8443 port, but nothing come up on that. Websocket way, I was able to at least run it over HTTP, but it was broken due to mixed content o…

Discourse doesn’t support any port combination other than 80/443

Discourse may not support, but Docker does, but I can still pass it with sockets to outter Nginx. [image] This is over 8080. My only issue is, I can’t seems to get HTTPS working in any way.

That’s why I said Discourse doesn’t support any ports other than 80/443 If you really want to attempt any alternative combination, You’re on your own.

That’s a really dumb thing if you ask me. People usually run multiple services on the same server, you are literally restricting users not to do so. Also docker containers are usually not alone on the same server. You seems to be pushing other people to purchase seperated servers, just because you d…

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 …

I already tried that before as well, it doesn’t comes through properly. Anyways, I don’t see the point of support in this case then at all, because as you said thousands of people do that. Yet there are no clear steps to make it work anywhere on Github or Wiki. Just straight the 80/443 option, that …

Except I am not running apache anyways, I would rather need nginx and litespeed, but neverthless, it would be simplier to just let use any other ports, then we can easily pass that to other web servers.

Discourse HTTPS Web Socket

지원 자체 호스팅

pfaffman (Jay Pfaffman) 5월 1, 2022, 6:18오후 10

You’ll need a reverse proxy, like How to set up Discourse on a server with existing Apache sites.

글		댓글	조회수
Run discourse in front of load balancer like AWS/Oracle OCI Self-hosting	1	423	7월 26, 2023
Run other websites on the same machine as Discourse Self-Hosting how-to , advanced-setup	66	139077	6월 30, 2026
Can't get Discourse to work on different ports Self-hosting	2	1608	3월 9, 2021
Content Security Policy: The settings of the page have blocked the loading of a resource ("script-src") Self-hosting unsupported-install	27	2369	5월 3, 2023
I see Discourse by port number but i couldn't see it to subdomain. (:3001) Self-hosting unsupported-install	7	670	1월 6, 2021

Discourse HTTPS Web Socket

Related topics