mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
privacy is undermined and reliability suffers due to unconfigurable aspects of FFMPEG web requests #7946
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @fartwhif on GitHub (Dec 25, 2025).
similar to https://github.com/jellyfin/jellyfin/issues/15440 , https://github.com/jellyfin/jellyfin/issues/11015
Anywhere a web request is invoked either via FFMPEG or otherwise, the global and context config, specifically the user agent, cookies, and proxy settings need to travel to the web agent doing the request. Use of web request tools without facilitating and piping critical web configuration settings forces ffmpeg and by extension jellyfin server into an unnecessary situation where certain functionality is targeted and denied access to web content by relying on the permanence of its crystalized web fingerprint.
the transcoder has no way to specify user agent and because of that google 403 forbids a whole bunch of segment ts GET requests ffmpeg makes, resulting in sometimes the player not playing, and sometimes when it does it's missing the first minute or minute and a half of content.
the requested isn't a feature, it's a privacy and stability patch
My guess is that they're allowing the requests, eventually, so that when they detect unknown clients they can truncate and delay the datastream from third party utilities that have decoded their URLs outside of approved apps and browsers. If it's not intentional then it might be AI fighting off oceans of bot activity and misclassifying ffmpeg's requests or something, but in any case modifying the user agent is the answer. jellyfin where running ffmpeg when its web request features are invoked it requires the admin configuration. Set it to the proper default user agent like jellyfin whatever whatever, that's fine, but it needs to be something controlled by the whim of the owner of the instance in order to alleviate this nonsense. it would be nice not to have to further customize ffmpeg or an ffmpeg launchpad every now and then.
"Live TV" has this, but not for libraries with playlist files pointing to web resources.