I'm using a Unix socket between Caddy and Discourse instead of TCP, but from time to time I get a 'unix:' error

[satonotdead]

Right, you can check this two links:

Discourse socketed: Nginx in front of discourse: no IP adresses

HA! I stand corrected: proxy_set_header X-Real-IP $remote_addr; is correct! My problem was that i only refreshed my discourse tab instead of closing and opening a new one, and the connection was somehow kept by outer nginx. After restarting nginx service: systemctl restart nginx, i can see the correct ips being passed to discourse. @mpalmer can you confirm that what i did is ok, and if it is should i edit the guide/wiki and add this new header?

Handling the "chain of trust" of the end user's real IP

Background Discourse needs to be aware of the end user’s real IP address. However, an end user never directly connects to Discourse since there is always one or more upstream web servers (nginx running in the Discourse container) in place. Thus, we need a way to pass along that information to Discourse in a trusted manner. The x-forwarded-for header is the solution. In this topic I will describe the specific mechanisms for properly handling that information and how we’re expecting it to be pro…

It seems that you are missing a header and/or your chain into Discourse template file.