Hi, I have researched quite a lot but nothing seems to work with me. I have a discourse setup installed. And I have this remote reverse proxy server that acts as a HTTPS layer between the user and the main discourse server.. [image] I have included these revers proxy settings properly.. But why…

The nginx running in the container does not trust headers set by the proxy. [图片] X-Forwarded-For proxy tag not recognized by Discourse? Self-hosting Take a look at the templates/cloudflare.template.yml file. Basically, you need to insert set_real_ip_from direc…

Hi @schleifer , Can you guide me on this? I have looked into these files, seems too fragile to manipulate on a production environment. Thanks!

If you have a single IP for the proxy, something like: - replace: filename: /etc/nginx/conf.d/discourse.conf from: "types {" to: | set_real_ip_from 192.168.0.1; real_ip_header X-Forwarded-For; real_ip_recursive on; types {

[图片] PhoenixPeca: I have included these revers proxy settings properly… But why does it still show my Reverse Proxy server’s IP Address (hostname to be specific) Probably you need to remove the same definitions from docker, modify your app.yml and rebuild: run: - exec: echo "Beginning of c…

最后显示的 IP 是反向代理 IP 地址

支持

riking (Kane York) 2019 年3 月 31 日 03:48 4

You only need the last part - inserting set_real_ip_from <CIDR>; to the nginx.conf. The other parts are more complicated to support Cloudflare adding new IPs.

话题		回复	浏览量
Real IP no longer recognized through proxy Self-hosting	4	313	2026 年7 月 16 日
Reverse proxy X-Forwarded-For Support unsupported-install , nginx	5	321	2026 年5 月 17 日
Rate Limiting w/ Reverse Proxy Self-hosting	3	793	2021 年11 月 16 日
All IPs recorded as 127.0.0.1 Self-hosting	4	2868	2017 年6 月 8 日
Reverse proxy for Discourse \| Real IP masking Self-hosting	14	2188	2023 年8 月 19 日

最后显示的 IP 是反向代理 IP 地址

相关话题