Как получить IP-адрес пользователя после обновления коммита b4a3389

CLOUD_PHT · 27.Июнь.2026 03:02:07

После обновления

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	28.07.2018
Discourse shows server IP/localhost as user's IP Self-hosting unsupported-install	18	2267	12.07.2022
Discourse socketed: Nginx in front of discourse: no IP adresses Self-hosting	5	2739	05.09.2018
All IPs recorded as 127.0.0.1 Self-hosting	4	2796	08.06.2017
IP Lookup is Pulling CDN's X-Forwarded-For Self-hosting	8	1127	30.07.2024

Как получить IP-адрес пользователя после обновления коммита b4a3389

Связанные темы