I’ve noticed that the limit remote stream bitrate setting does not seem to be applied or respected when using a reverse proxy. I’ve published my reverse proxy Plex URL for discovery which works fine, I have remote access itself disabled as I’m not externally forwarding 32400 directly anymore. However, the limit bitrate setting only seems to work when remote access is through TCP 32400. Although, Plex itself knows the stream is remote. However I can see higher bandwidth than my set limit being used.
So when it comes to reverse proxies, i have seen this a lot with other services i use (not necessarily plex) being the proxy does not pass the client IP to the end service. This means the service you are actually landing at thinks the traffic is coming from the localhost (or where ever your proxy is running)
I would suggest checking the logs, dashboard or using another 3rd party network monitoring tool to what address Plex thinks the traffic is coming in from, not the proxy or client. You say Plex itself knows, where are you seeing that?
I could be barking up the wrong tree but it is just a thought and i guess a place to start looking. Can’t tell without knowing how you got things setup and what services you are using
Thanks for your reply. This is from the Plex Dashboard of the server itself. It knows the traffic is remote and it’s showing the external IPv4 of the client that’s streaming content. As far as I know my reverse proxy is passing that correctly, otherwise it wouldn’t be visible to Plex.
Thanks. I’ve confirmed x-forwarded-for is being passed to Plex, it’s present in the logs. It sees the local IP of my reverse proxy server, but it’s seeing the true remote IP from a client:
Apr 25, 2020 19:27:40.175 [0x7f16935aa700] DEBUG - Using X-Forwarded-For: 2a01:4c8:c0f:xxxx:x:x:xxxx:xxxxx as remote address
In this case my mobile network I tested with has IPv6, but I could also see this on an external IPv4 client too.
As the limit bandwidth setting is present on the remote access tab, is there a chance it’s tied to the standard remote access method over the port specified and not take into account the reverse proxy?
Could well be but that isn’t something i can answer. I would assume if your proxy is passing to the localhost:32400 and passing in the client IP, Plex shouldn’t know any different
A theory - could be wrong:
If you have actually disabled remote access in Plex is that by default stopping those extra features?
I use a dedicated server and only has 1 IP being the external, no internal subnet. My Plex says not accessible outside but is accessible inside (I can see it from the outside world) and these features work for me. Of course it is very different from yours as i don’t use a proxy for Plex but the main concept is there of Plex not seeing any remote access:
