+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: No files will play on clients. (/t-no-files-will-play-on-clients)
No files will play on clients. - damnsignin - 2024-03-05
I have set up Jellyfin on a Raspberry Pi 5, via CasaOS, with three external Firecuda 5TB HDDs on a powered USB hub, using this guide:
https://www.youtube.com/watch?v=MgOFtewmBi8
After some studying about using fstab, I have everything connected, configured and Jellyfin has my entire library scanned, albeit without metadata support, to access on my home network.
But nothing will play on my any of my devices. Any video will give "This item cannot be played" messages and a few will close out saying they quit after multiple failed attempts. No music or audio files will play either. The Jellyfin client app will load the music, but sits at 0:00 with no actual play. I think (and I may be thinking wrong) I'm missing permissions on the Raspberry Pi configuration to let Jellyfin play to anything on my network, but after two days of Google searches and reading through guides and notes, I cannot figure out how to troubleshoot this issue. I'm completely stumped.
I'm using Jellyfin 10.8.13 on the latest CasaOS and Raspberry Pi OS Full.
RE: No files will play on clients. - TheDreadPirate - 2024-03-05
Can you share your Jellyfin logs with us via sourcebin or pastebin?
RE: No files will play on clients. - damnsignin - 2024-03-05
Which log file? I've got three log files with the combined size of the Encyclopedia Britannica from the adding of 12TB of files to Jellyfin and two dozen FFmpeg transcode files from attempts to run files.
RE: No files will play on clients. - damnsignin - 2024-03-06
I tried to paste the non-ffmpeg log files to pastebin, but they're too big. One file is 95.3MB and the other is 2.23MB.
RE: No files will play on clients. - TheDreadPirate - 2024-03-07
Those are absolutely gigantic logs.
Stop your server, rename your jellyfin logs. Start your server, replicate the problem, share the fresh log with us.
RE: No files will play on clients. - damnsignin - 2024-03-08
Here it is
https://pastebin.com/U2zjraAc
RE: No files will play on clients. - TheDreadPirate - 2024-03-08
This looks like a permissions issue or the files are otherwise inaccessible to Jellyfin.
Code:
[2024-03-07 16:55:13.928 -08:00] [ERR] [33] MediaBrowser.Controller.Entities.BaseItem: Error refreshing owned items for "/NAS_C/Media/Media/Movies/Code 8/(2024) Part 2.mp4"
System.IO.DirectoryNotFoundException: Could not find a part of the path '/NAS_C/Media/Media/Movies/Code 8'.RE: No files will play on clients. - damnsignin - 2024-03-08
I was afraid of that. But I don't know how to grant permissions to Jellyfin. I've looked it up and failed to figure out what place I need to edit to give Jellyfin permissions.
RE: No files will play on clients. - 34626 - 2024-03-08
Open a terminal and cd to the external drive mount like:
cd /to/path/of/mounted/drive/
Then execute:
sudo chmod -R 777 *
This command will give all permission to all files in the folder you execute it and all files and folders that is in below that path.
You might need to restart the Jellyfin server and scan the library (Please test only on one external drive).
I would recommand you to run Jellyfin in a docker, then you can set permissions for the folders in docker which is better.
RE: No files will play on clients. - TheDreadPirate - 2024-03-08
(2024-03-08, 11:29 AM)34626 Wrote: Open a terminal and cd to the external drive mount like:
cd /to/path/of/mounted/drive/
Then execute:
sudo chmod -R 777 *
This command will give all permission to all files in the folder you execute it and all files and folders that is in below that path.
You might need to restart the Jellyfin server and scan the library (Please test only on one external drive).
I would recommand you to run Jellyfin in a docker, then you can set permissions for the folders in docker which is better.
This would work, but only if there isn't an ACL or some other mount parameter restricting the permissions.