I’m using 115-Openlist-strm-jellyfin-infuse media chain, But infuse can’t play (thought other players can). So I searched and found this topic. Is this a real bug?
根据我的调试发现问题在于Infuse请求时没有传递User-Agent，Openlist会使用一个默认的User-Agent去生成115直链。然后Infuse访问直链时因为User-Agent与默认的不同导致验签失败。
本地修改代码在生成直链时不使用默认UA，就用空的去生成115直链，然后Infuse就可以播放了。
但这会引入另一个问题，播放时Infuse不会缓存302的直链，所以会频繁的调用Openlist生成115直链，体验不是很好。
我的方案是使用nginx以url和UA作为cache_key，将302响应缓存，这样配置下来体验还可以。
Mod Edit For Translation:
According to my debugging, the problem is that the User-Agent is not passed in the Infuse request, and Openlist will use a default User-Agent to generate a 115 direct link. Then when Infuse accessed the direct link, the signature verification failed because the User-Agent was different from the default one.
The local modification code does not use the default UA when generating direct links, use empty to generate 115 direct links, and then Infuse can play it.
But this will introduce another problem. Infuse will not cache 302 direct links during playback, so it will frequently call Openlist to generate 115 direct links, and the experience is not very good.
My solution is to use nginx to use url and UA as cache_key to cache the 302 response. After configuration like this, the experience is OK.
Please also post in English unless you’re posting in 汉语 - Chinese - Firecore so that more users can benefit from your contributions. Also you may get an answer sooner from others who have had the same problem.
也请用英文发布，以便更多用户可以从您的贡献中受益。 此外，您可能会更快地从遇到同样问题的其他人那里得到答案。
Hi,
I’m experiencing a playback issue when using the following setup:
Infuse → Jellyfin → STRM file → OpenList → 115
Playback in Infuse fails with:
A playback error occurred
An error occurred loading this content
The same media works correctly in Jellyfin Web and in VidHub connected to the same Jellyfin server.
I also did some additional testing:
- If I bypass Jellyfin and open the STRM/OpenList URL directly with Infuse, playback works.
- If the STRM file in Jellyfin contains a direct media URL instead of an OpenList URL, playback works.
- If I replace OpenList with a simple Nginx HTTP 302 redirect to a normal MP4 URL, playback through Jellyfin and Infuse also works.
Therefore, this does not appear to be a general issue with HTTP 302 redirects.
After some further testing, the issue appears to be related to User-Agent handling. OpenList generates a temporary 115 download URL based on the User-Agent associated with the request, and the User-Agent used when Infuse later accesses the resulting URL may not match. This can cause the 115 URL to fail validation.
It seems that the combination of Infuse + Jellyfin + STRM + OpenList/115 exposes a User-Agent mismatch that does not occur when Infuse accesses OpenList directly.
Would it be possible for Infuse to preserve or otherwise handle the User-Agent required by redirected media URLs in this playback path?
I’m happy to provide additional logs or testing information if needed.
Thanks!
I moved your post to that already running thread discussing this issue. I edited out the reference to this thread since you post is now in it. 
User-agent would be super helpful for a lot of m3u8 streams I use too once M3U Playlist support is available.
Passing of user-agent via the same method as popular Android players such as tivimate via ‘|User-Agent=‘ would be a good way to add it without a clunky extra setting possibly?
Would you be able to replicate the issue and send in a report from your device and post the code here?
I have already sent the feedback and the code is ND63A
The video title is test in Jellyfin, and the strm file points to a mp4 file.