Jellyfin fails to play most files after updating to EE

Apps and Virtualization
1

Hi,

pre-update I had HW transcode working with Nvidia P400. After update I followed the post from HoneyBadger and succesfully added the gpu to frigate app.

Next I attempted to do the same with my Jellyfin. I confirmed with nvidia-smi in the container that it sees the gpu.

I clicked first video from my next up and it started playing, then I chose the lowest bitrate to force transcoding - playback fatal error (logs on my privatebin: PrivateBin)

Now it’s where it gets weirder, I almost never use the transcoding anyway, I just had it setup coz the gpu is in the box so I disabled HW transcoding in JF options.

Clicked another file from Next Up - fatal playback error. Checked the file that worked before and it works, but only if direct streaming (transcode fails even with disabled HW transcoding). Thought it’s codec related, the working file is hevc, the nonworking was h264. Tried another hevc file - fatal playback error. (logs when trying to cpu transcode: PrivateBin)

Cleared browser cache. Restarted jellyfin container. Rebooted the whole NAS. No change. It is not permissions related as I can access/delete/rename the file that doesn’t play from within jellyfin container.

Anyone has any idea what could be going on?

tl;dr Most files fail to play, Neither cpu nor gpu transcoding work

2

Borked permissions on the transcode directory?

1 Like
3

So, I checked the permissions and they were drwxrwxrwt for the user running the jellyfin container. But the path was sorta weird I thought, so I checked the Transcode settings in JF container and although it was set to Temporary in RAM as before update, all I did was set it to Temporary on disk and after redeploy everything works, even HW transcoding \o/

for reference the path when temporary in ram was:
/mnt/.ix-apps/docker/volumes/ix-jellyfin_tmp/_data/
perms were drwxrwxrwt

and with temporary on disk it is:
/mnt/.ix-apps/docker/volumes/ix-jellyfin_config_transcodes/_data
and perms drwxr-xr-x

Thanks for having the right idea!

edit: although isn’t it a bit of a bug? I mean both options are created by the ui, I haven’t set any perms by myself, yet one doesn’t work, where it worked pre-update.

1 Like
4

Might be worth reporting it as a bug, yes.
Did you accidentally leave the leading slash out in the second path?

5

I did indeed. I’m going to flip it back to in RAM and if it still doesn’t work open a bug on jira

edit: issue on github
edit2: just closed as fixed, no idea when the fix hits the app, hopefully next update of the app

1 Like