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.
This seems related to the issue discussed here:
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!