Does Plex ignore X-Real-IP or X-Forwarded for in the headers for local IP Addresses?

General Discussions
1

Network Setup:

WAN > Router > DMZ Proxy (172.16.0.1) > LAN (172.16.20.x)

Plex is on 172.16.20.200
Using NGINX Reverse Proxy on 172.16.0.1 (DMZ Network) to proxy requests from WAN, and also internally on LAN for SSL/Cert/Name resolution.

If I access Plex from outside my network coming in on the WAN, Plex honours the origin IP in the header.

If I access Plex from my network e.g. 172.16.20.123 or 172.16.20.300 then Plex seems to completely ignore the header and shows the origin IP as the Proxy (172.16.0.1) - I have checked, and the origin IP (172.16.20.123) is definitely forwarded to Plex in the header.

Am I missing something? Seems to be the same issue here, but it was dismissed - perhaps misunderstood? Why doesn’t plex use X-Real-IP or X-Forwarded-For headers? - General Discussions - Plex Forum

Not being able to distinguish between different hosts/clients on my internal network is a huge limitation.

1 Like
2

Seems like it. I’m trying to find a solution, but best thing i figured out was to at least add IP of my proxy to local networks in plex, so i at least can distinguish between local and remote connections. But this issue is indeed very annoying.

3

Thanks - glad it is not just me.

Anyone from Plex able to comment? Is this intended behaviour, or perhaps an oversight or bug?

Thanks.

4

Anyone?

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.