I’m testing deploying Discourse on top of the CentOS-derived AlmaLinux 9 with SELinux enabled and external nginx configured. Because the Ubuntu-based container doesn’t know about SELinux, it keeps replacing the unix domain socket with a new file that is not security labeled every time I start the c…

Thanks! public (active) target: default ... services: dhcpv6-client http https ssh ports: protocols: forward: yes masquerade: yes forward-ports: source-ports: icmp-blocks: rich rules:

There is a difference in latency, a socket is about ~3x quicker than a local loopback port. That said, we’re talking a difference of 4-5us here at best.

After looking into this more, I definitely want to add proxy_set_header "Connection" ""; to disable the default Connection: close header

Any downsides to proxy via port instead of unix domain socket?

Product Support Self-hosting

Falco (Falco) September 29, 2022, 2:14am 2

As long as you block people from connecting directly to port 8008 using your preferred method, no problem.

Topic		Replies	Views
Difference between socket- and port-based connection to outer NGINX? Self-hosting	10	12776	December 28, 2019
Discourse not working through separate nginx docker Self-hosting	3	2767	October 17, 2017
[SOLVED]Install issues with 2 separate servers Self-hosting	2	660	April 15, 2020
Disable direct access with port (nginx) Self-hosting	2	9651	July 22, 2015
Using nginx as proxy server is very slow, but it is very fast if using nginx in docker! Why? Self-hosting	0	2402	November 2, 2020

Any downsides to proxy via port instead of unix domain socket?

Related topics