If I understand things correctly there are two ways of configuring your discourse instance behind an NGINX server: with a socket connection (as described here ) by exposing some port of the container and telling the outer NGINX to forward traffic for discourse to that port (as suggested here and he…

UNIX sockets (as opposed to TCP sockets) are faster and more efficient, and less prone to accidental disclosure to places you don’t want connections coming from. A misconfiguration can potentially cause a listening TCP socket to be exposed to the Internet, whereas there’s absolutely no way you can …

OK, so I’ll continue trying the UNIX socket. What would be some steps for trouble shooting why a UNIX socket is not working? (I already have the default_server listening on port 81 for the time being, just to have it out of the way)

I think there is a typo in the tutorial. At the end of the first line is a colon too much. Don’t forget to rebuild! For https installations It should be: proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock; proxy_set_header X-Real-IP $remote_…

[image] Lutz: I think there is a typo in the tutorial. At the end of the first line is a colon too much. Don’t forget to rebuild! I already tried both with and without the extra colon. But good to know that it should definitely be without the colon. Regarding rebuild: this is the config for t…

[image] kraml: You need to put the whole location block inside the server block. Opps, how embarassing. :dizzy_face: But also interesting that sudo nginx -t did not complain about the extra }. Unfortunately, however, that was apparently not the only problem as I still get ERR_CONNECTION_R…

Where did you get this ERR_CONNECTION_REFUSED error? On a client machine? If so then your nginx is just not listening on port 80.

Yes, the error is on a client machine. Okay, then I suspect the problem is with my /etc/nginx/sites-available/default. For the time being I set it to listen to port 81: server { listen 81 default_server; listen [::]:81 default_server; server_name 88.99.**.** mydomain.net www…

@tophee @Lutz pls give me some advice thx I have 3 multisite running each of them disable https and run a nginx over the host, nginx.conf is like this.url is 522 error. events { worker_connections 1024; } http { include mime.types; default_type application/octet-stream; lu…

Sorry, I can’t help you with this. The first and (almost) last time I looked at the details of NGINX was three years ago, when I set up my forum… And I have no experience with multi-site at all.

Difference between socket- and port-based connection to outer NGINX?

Product Support Self-hosting

kraml (Kai Liu) March 29, 2017, 8:20am 6

You need to put the whole location block inside the server block.

Topic		Replies	Views
Run other websites on the same machine as Discourse Self-Hosting how-to , advanced-setup	66	140130	June 30, 2026
Discourse working with jwilder /nginx proxy & acme-companion Self-hosting	6	5708	February 9, 2022
Use Nginx Proxy Manager to manage multiple sites with Discourse Sysadmins how-to	33	25067	February 23, 2025
Discourse with jwilder/nginx-proxy howtos? Self-hosting	11	8392	April 6, 2019
Installation on v-server as a subfolder with other services in subfolders using apache Self-hosting	39	8507	July 6, 2016

Difference between socket- and port-based connection to outer NGINX?

Related topics