search

toomuchio / plex-nginx-reverseproxy

Configuration to serve Plex Media Center https://plex.tv using Nginx https://nginx.com
663 stars 94 forks source link

Internal Clients reporting 127.0.0.1 #36

Closed Animosity022 closed 6 years ago

Animosity022 commented 6 years ago

I just finally turned off my internal clients and pushed them to using the proxy as well.

I turned on verbose/debug and I can see the header looks good:

Aug 29, 2018 14:38:17.702 [0x7f5c13ffc700] VERBOSE -  * X-Real-IP => 192.168.1.105
Aug 29, 2018 14:38:17.702 [0x7f5c13ffc700] VERBOSE -  * X-Forwarded-For => 192.168.1.105
Aug 29, 2018 14:38:17.702 [0x7f5c13ffc700] VERBOSE -  * X-Forwarded-Proto => https

But for some odd reason, I'm seeing only the 127 address for the local LAN IPs instead of the internal address. I'm sure I'm missing something silly but can't seem to figure out what it is.

Animosity022 commented 6 years ago

Missed adding in the Tautulli pic.

image

Animosity022 commented 6 years ago

Here is an example of external IP:

image

Animosity022 commented 6 years ago

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 :(

toomuchio commented 6 years ago

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