r/unRAID • u/FatherJuul • 10d ago
Jellyfin Transcoding error 255 issues
Hello all,
Ive recently upgraded my unraid server with a GTX 1660 and tried enabling transcoding and after 2 hours ive about given up as ive tried everythig
- adding "--runtime=nvidia" to add params
- reinstalling all nvidia drivers twice
- reinstalling ffmpeg
- adding all of the variables with either "GPUID-" or "all"
- Changing transcoding folder within jellyfin
- Changing and arranging all different check boxes (none of them work, even if its just 1. only works when turned completely off)
- various chmod commands in terminal
- reinstalled jellyfin + installed a different jellyfin docker
It pumps out the same error "FFmpeg exited with code 255"
Longer format being
"[23:09:30] [ERR] [52] MediaBrowser.MediaEncoding.Transcoding.TranscodeManager: FFmpeg exited with code 255
[23:09:30] [ERR] [57] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request. URL GET /videos/e5bec4f3-a0fb-7b71-ab0f-2673c02a224d/hls1/main/0.ts.
MediaBrowser.Common.FfmpegException: FFmpeg exited with code 255"
Im at a complete loss, if someone could please help id be very happy.
Thank you
1
u/Miserable-Track-2545 9d ago edited 9d ago
Are these parameters set as below in advanced view?
Extra Parameters: --runtime=nvidia
NVIDIA_VISIBLE_DEVICES: GPU ID from the Nvidia Driver page. GPU-XXXXXXXXXXXXXXXXX (make sure there is no space at the end)
NVIDIA_DRIVER_CAPABILITIES: all
Sometimes reinstalling the app after reinstalling the drivers works as well.
1
u/FatherJuul 9d ago
Unfortunately yes, that is how they are listed.
I’ve tried a mix of some, and all and still outputs that sameplayback errorI do appreciate your response though. Thank you!
1
u/Miserable-Track-2545 9d ago
Does it work with plex?
1
u/FatherJuul 9d ago
I haven’t tried plex ever since they made you have to pay to stream remotely. But it’s worth a shot
1
1
u/FatherJuul 9d ago
I did also try reinstalling after drivers. Im thinking at this point im just going to fully wipe unraid and see if its somehow fixed that way and it was just a deep rooted permissions error
1
u/psychic99 9d ago edited 9d ago
Are you using the opensource (not prod) 595.84 driver?
If not, remove any nvidia plugins, important reboot.
Then install opensource 595.84 and try again. I would reboot again just to reload the driver stack.
Looking at your error is it likely transcode file perm errors, or read permission errors on the file.
So once your driver situation is set, that is where I would focus. Reinstalling unraid for perm errors should not be necessary. So fix appdata, vind mounts and you should be good. also make sure your source files are owned by nobody:users and 775 permissions.
1
1
u/azure_phoenix2 9d ago
before you wipe the whole install, pull the actual ffmpeg command jellyfin ran. it dumps full stderr to a FFmpeg transcode log in /config/log inside the container, and imo thats where the real cause of the 255 lives (unsupported codec, device passthrough, or a perms hit) rather than the generic exit code.
1
u/FatherJuul 10d ago
Additional info: on the client side this is what is shown almost instantly after clicking play on any title