Caddy와 Discourse 사이에 TCP 대신 Unix 소켓을 사용하는데, 간헐적으로 'unix:' 오류가 발생합니다

[satonotdead]

네, 다음 두 링크를 확인해 보실 수 있습니다:

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?

최종 사용자의 실제 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…

헤더가 누락되었거나, Discourse 템플릿 파일에서 신뢰 체인(chain of trust) 설정이 제대로 되어 있지 않은 것 같습니다.