Issue with proxy and bitrate limit

[flame]

In Nginx proxy manager, did you follow our documentation and add the specified options in the advanced tab?

https://jellyfin.org/docs/general/networ...xy-manager

One of the options is specifically for ensuring that things like bit rate limits are applied correctly.

Code:

proxy_set_header X-Real-IP $remote_addr;

Without this option, Jellyfin will read the proxy's IP address.  With this option in Nginx, in combination with Known Proxies, Jellyfin will read the address in the header for the proxied client.

Yes I am using most of the required part in the Nginx proxy managers advanced config except for the security settings since this isn't shared with anyone except family and the tld (.home) is for local network access so cannot generate a publicly trusted SSL cert for it.

Even after setting the max bitrate allowed for external connections to 3Mbps, I was still able to receive a 6+Mbps remuxed video over mobile data on my phone.

Log file regarding the incident:

[INF] User policy for "flame". EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True 
[INF] RemoteClientBitrateLimit: 3000000, RemoteIP: "192.168.1.10", IsInLocalNetwork: True

And as for the known proxies list, as I have already mentioned, 192.168.1.10 is already added as a known proxy.

I really don't understand why it is still showing up as a local network device