+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Jellyfin docker container not starting after changing a setting (/t-jellyfin-docker-container-not-starting-after-changing-a-setting)
Jellyfin docker container not starting after changing a setting - Chapster5 - 2025-12-21
Hi all as above.
I have the latest jellyfin version from the official docker image on my unraid server and it was working great however I had a bit of a glitch sometimes where media would randomly stop and just not play again if you wait 5 mins then come out the media and go back in it'll play again.
I ask for transcoding tips in the jellyfin group on Facebook and a guy sent me some commands to run in tbe unraid console to create a transcode directory for jellyfin to use.
I added an extra path under the jellyfin unraid config that pointed to this newly created directory to use and I changed the directory under transcoding in Jellyfin to the same place.
I now no longer have access to jellyfin and the server on Docker refuses to start up. I have since gone back into the jellyfin config and deleted the extra host path line out and saved. It compiles fine but when. I try and start the server i just get execution error -
server error.
The commands I ran are
"if you have ram available could use it for transcoding. Better than nvme. Use temimal : mkdir -p /mnt/ramdisk/jellyfin mount -t tmpfs -o size=16g tmpfs /mnt/ramdisk/jellyfin chmod 777 /mnt/ ramdisk/jellyfin"
There is errors when it's starting up about files cannot be found now? Just wondering if there's a fix without nuking my jellyfin setup and having to start again?