I have an external load balancer (aws ELB) directing traffic to my discourse server. I have verified the X-Forwarded-For headers are being sent, but for some reason all the user ips show up as the load balancer ip? Is this a bug or is there some setting I am missing?

I know @mpalmer knows a lot about this. Any advice, Matt?

I’d say you’re missing the nginx setting to “trust” the IP address that is making the connection, so the XFF header is ignored. The setting name is set_real_ip_from; grovel around in your nginx config(s) to see what (if anything) it’s currently set to, and season to taste.

Thanks, found the solution here: Amazon Elastic Load Balancer and Forwarding Real-IP Nginx basically, add the following to the http section in nginx.conf real_ip_header X-Forwarded-For; set_real_ip_from 0.0.0.0/0;

[画像] nhumrich: set_real_ip_from 0.0.0.0/0; Oh sweet jeebers, don’t do that. It’ll allow anyone who can manage to get a HTTP connection into your servers to spoof their IP address, which will only lead to trouble. Set it to the IP range of your VPC, instead.

oh ya, I know that much, I just didnt want to post my range to the public :wink:

Well, they’ll surely scroll down and see your reply just under it, though? I suspect yes.

Discourse reports user ips as the load balancer

Development

mpalmer (Matt Palmer) 2016 年 6 月 1 日午後 11:54 7

Sure, but will everyone else who finds this topic and copies your example know that?

トピック		返信	表示
Reverse proxy X-Forwarded-For Product Support unsupported-install , nginx	5	342	2026 年 5 月 17 日
Handling the "chain of trust" of the end user's real IP Self-Hosting docker , how-to	7	481	2026 年 7 月 2 日
Real IP no longer recognized through proxy Self-hosting	4	330	2026 年 7 月 16 日
Commit b4a3389 更新后如何获取用户ip Self-hosting nginx , cloudflare	3	476	2026 年 6 月 29 日
All IPs recorded as 127.0.0.1 Self-hosting	4	2877	2017 年 6 月 8 日

Discourse reports user ips as the load balancer

関連トピック