Internal Clients reporting 127.0.0.1 about plex-nginx-reverseproxy HOT 4 CLOSED

Missed adding in the Tautulli pic.

from plex-nginx-reverseproxy.

Here is an example of external IP:

from plex-nginx-reverseproxy.

I'm guessing it has to be plex at this point as the only issues I have are with any private address ranges. I tested on my HomeVPN as well which is on a different subnet:

Aug 31, 2018 10:12:05.608 [0x7f7bf93fe700] VERBOSE - X-Forwarded-For: 12.150.5.XXX
Aug 31, 2018 10:12:05.608 [0x7f7bf93fe700] DEBUG - Using X-Forwarded-For: 12.150.5.XXX as remote address

Aug 31, 2018 10:09:28.167 [0x7f7bf43fe700] VERBOSE -  * X-Real-IP => 10.0.8.6
Aug 31, 2018 10:09:28.168 [0x7f7bf43fe700] VERBOSE -  * X-Forwarded-For => 10.0.8.6
Aug 31, 2018 10:09:28.168 [0x7f7bf43fe700] VERBOSE -  * X-Forwarded-Proto => https

None of the private IP ranges seem to make the debug message of using the X-Forwarded-For: Anyone else seen this? I can turn back on 32400 locally if that's the case :(

from plex-nginx-reverseproxy.

Seems like a configuration issue perhaps with Plexpy, I'm unable to recreate it.

from plex-nginx-reverseproxy.