Server Version#: Version 1.25.2.5319
Player Version#: Plex Web Version 4.66.1
Relevant Logs:
Jan 09, 2022 15:42:43.488 [0x7fd42178fb38] DEBUG - Request: [94.XX.200.XX:47480 (WAN)] GET /status/sessions (10 live) GZIP Signed-in Token (Username) / accept => application/json, text/plain, */* / accept-encoding => gzip, deflate, br / accept-language => en / Connection => Upgrade / Host => plex.website.xyz / referer => https://plex.website.xyz/web/index.html / sec-ch-ua => " Not;A Brand";v="99", "Google Chrome";v="97", "Chromium";v="97" / sec-ch-ua-mobile => ?0 / sec-ch-ua-platform => "Windows" / sec-fetch-dest => empty / sec-fetch-mode => cors / sec-fetch-site => same-origin / user-agent => Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36 / X-Forwarded-For => 3.XX.30.XX / X-Forwarded-Proto => https / X-Plex-Client-Identifier => i3rr247ymerwzbpmxq02dulr / X-Plex-Device => Windows / X-Plex-Device-Name => Chrome / X-Plex-Device-Screen-Resolution => 2560x1321,2560x1440 / X-Plex-Features => external-media,indirect-media / X-Plex-Language => en / X-Plex-Model => bundled / X-Plex-Platform => Chrome / X-Plex-Platform-Version => 97.0 / X-Plex-Product => Plex Web / X-Plex-Sync-Version => 2 / X-Plex-Token => xxxxxxxxxxxxxxxxxxxx / X-Plex-Version => 4.66.1 / X-Real-IP => 3.XX.30.XX
Jan 09, 2022 15:42:43.488 [0x7fd42178fb38] DEBUG - [Now] Adding 1 sessions.
Jan 09, 2022 15:42:43.488 [0x7fd42178fb38] VERBOSE - It took 0.0 sec to serialize a list with 1 elements.
Jan 09, 2022 15:42:43.489 [0x7fd421cd2b38] DEBUG - Completed: [94.XX.200.XX:47480] 200 GET /status/sessions (10 live) GZIP 1ms 1355 bytes (pipelined: 33)
Jan 09, 2022 15:42:43.498 [0x7fd421cafb38] VERBOSE - X-Forwarded-For: 3.XX.30.XX
Plex Dashboard reports IP 94.XX.200.XX when it should report 3.XX.30.XX.
This used to work when WAN was a private address like 127.0.0.1 so maybe its a bug where if the WAN IP is not a private address it ignores any X-Real-IP header from the reverse proxy.
