+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Issue with proxy and bitrate limit (/t-issue-with-proxy-and-bitrate-limit)
Issue with proxy and bitrate limit - flame - 2024-09-17
Hello,
I am facing a problem while using Nginx proxy manager as a proxy on my LAN and using tail scale to access the proxy.
I have defined the proxy's IP as a known proxy (192.168.1.10)
I even restarted the jellyfin service after saving the new config.
However, when checking the logs and trying to stream this is what comes up:
[INF] RemoteClientBitrateLimit: 8000000, RemoteIP: "192.168.1.10", IsInLocalNetwork: True
Isn't it supposed to be false after defining 192.168.1.10 as a known proxy?
RE: Issue with proxy and bitrate limit - flame - 2024-09-17
Jellyfin version 10.9.11
Install Method: Debian repository
RE: Issue with proxy and bitrate limit - TheDreadPirate - 2024-09-17
In Nginx proxy manager, did you follow our documentation and add the specified options in the advanced tab?
https://jellyfin.org/docs/general/networking/nginx/#nginx-proxy-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.
RE: Issue with proxy and bitrate limit - flame - 2024-09-18
(2024-09-17, 10:55 PM)TheDreadPirate Wrote: In Nginx proxy manager, did you follow our documentation and add the specified options in the advanced tab?
https://jellyfin.org/docs/general/networking/nginx/#nginx-proxy-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
RE: Issue with proxy and bitrate limit - TheDreadPirate - 2024-09-18
Have you restarted jellyfin since applying those network config changes? I did some testing and I was only able to replicate this situation by not restarting Jellyfin after make a config change.