I have a Jellyfin server containing three media directories, one of which is nothing but symlinks. Prior to the Jellyfin 10.11 upgrade Infuse worked fine with this, and other players still work fine for the same files (I’ve tested with Swiftfin on Apple TV and the web player in Firefox), so the problem seems to be specific to Infuse. When I attempt to play a file from the symlink library in Infuse, the client just says “An error occurred loading this content” and the server reports playback errors such as the following:
Oct 28 11:10:04 jellyfin jellyfin[762477]: [11:10:04] [ERR] Connection id “0HNGM5VO4R7FG”, Request id “0HNGM5VO4R7FG:00000001”: An unhandled exception was thrown by the application.
Oct 28 11:10:04 jellyfin jellyfin[762477]: System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (25 of 1455221872).
Oct 28 11:17:33 jellyfin jellyfin[762477]: System.ArgumentOutOfRangeException: (Parameter 'count')
Playback of non-symlinked media seems fine, and as mentioned earlier, other players are able to play this same media from the same library.
This problem is occurring with Infuse on Apple TV and on iPad, while playback has been successful on Swiftfin for Apple TV, the Jellyfin web player in Firefox, and the Jellyfin app on iPad. This did not occur on Jellyfin 10.07, and I have tried restarting my Apple TV, and removing the Jellyfin share and readding it, with no change in behavior. If there’s other information I can provide please let me know.
same problem here on macos, 2 days ago it was working fine
Also getting the same error, although I’m not sure if its related to Jellyfin updates or the latest Infuse updates.
To confirm though, working in other media players e.g. Jellyfin direct
AND
If I use Plex instead of Jellyfin accessing the same Symlink this also works.
So its unique to the combination of Jellyfin + Infuse + Symlinks
Anyone got any workarounds/fixes?
You may try updating to the latest Jellyfin 10.11.2 version and Infuse 8.3.1 to see if this helps.
If the issue persists, sending in a report from Infuse (and posting the code here) will allow us to look a bit further into what may be going on here.