# Real IP no longer recognized through proxy **URL:** https://meta.discourse.org/t/real-ip-no-longer-recognized-through-proxy/407792 **Category:** Self-hosting **Created:** [July 16, 2026, 1:02pm UTC](https://meta.discourse.org/t/real-ip-no-longer-recognized-through-proxy/407792 "2026-07-16T13:02:29Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi) #### Post date: [July 16, 2026, 2:39pm UTC](https://meta.discourse.org/t/real-ip-no-longer-recognized-through-proxy/407792/3 "2026-07-16T14:39:50Z")
Probably related to this commit: [FIX: nginx sample configuration should be setting x-f-f to the end us… · discourse/discourse@b4a3389 · GitHub](https://github.com/discourse/discourse/commit/b4a3389751ebe118f58ec6dd5419d6007c61228f) This may help you: > [@Handling the "chain of trust" of the end user's real IP](https://meta.discourse.org/t/handling-the-chain-of-trust-of-the-end-users-real-ip/406372): > > 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… --- _[View the full topic](https://meta.discourse.org/t/real-ip-no-longer-recognized-through-proxy/407792)._