コミット b4a3389 更新後にユーザーのIPを取得する方法

CLOUD_PHT · 2026 年 6 月 27 日午前 3:02

FIX: nginx sample configuration should be setting x-f-f to the end user IP

committed 08:24PM - 16 Jun 26 UTC

nginx's responsibility is to determine the correct end user's IP (as far as we c…an trust it) and report that to Discourse. The correct way to do that is to teach nginx how to determine this for itself - this means that both the nginx logs and the downstream value will be correct. (see https://github.com/discourse/discourse_docker/pull/1077 which removes the only use of `proxy_add_x_forwarded_for`) Setting the x-f-f header to `$proxy_add_x_forwarded_for` or `$http_x_forwarded_for` hides this learned knowledge and forces Discourse to go through the same process and possibly arrive at a edifferent answer. In most cases this won't make a difference, but when there is more than one proxy in front of Discourse this exposes a failure case. client → proxyA → proxyB → nginx → discourse means Discourse saw: ``` x-real-ip: client_ip x-forwarded-for: client_ip, proxyA ``` and might end using `client_ip` or `proxyA_ip` depending on codepath. After this change, Discourse sees: ``` x-real-ip: client_ip x-forwarded-for: client_ip ``` for the same situation.

の更新後、すべてのユーザーの最終使用アドレスが Docker のゲートウェイ（例：172.17.0.1）に変更されました。

私の使用しているアーキテクチャは以下の通りです。

Cloudflare → VPS Nginx → Discourse Docker Nginx → Discourse

トピック		返信	表示
All users have the same IP (the Servers IP)? Self-hosting	13	4278	2018 年 7 月 28 日
Discourse shows server IP/localhost as user's IP Self-hosting unsupported-install	18	2267	2022 年 7 月 12 日
Discourse socketed: Nginx in front of discourse: no IP adresses Self-hosting	5	2739	2018 年 9 月 5 日
All IPs recorded as 127.0.0.1 Self-hosting	4	2796	2017 年 6 月 8 日
IP Lookup is Pulling CDN's X-Forwarded-For Self-hosting	8	1127	2024 年 7 月 30 日

コミット b4a3389 更新後にユーザーのIPを取得する方法

関連トピック