+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: This client isn't compatible with the media... (/t-solved-this-client-isn-t-compatible-with-the-media)
Pages:
1
2
This client isn't compatible with the media... - LittleHorus - 2024-03-09
Hi thanks for taking time helping me, it's very much appreciated.
I'm getting an error message when I try to stream my videos, I think I know why but don't know how to fix. My media is on a second drive which I have set up to mount automatically, when I check the log it says:
/run/media/fedora/Jellyfin/Jellyfin Server Media/tv shows/The long way down/Long Way Down (2).mp4: No such file or directory
This is the guide I used.
https://www.zdnet.com/article/how-to-permanently-mount-a-drive-in-linux-and-why-you-should/
I'm using Fedora 39 updated, Jellyfin 10.8.13 and I think I've installed the necessary codecs.
Full log:
https://pastebin.com/embed_js/pqyGMw3D
Thanks again.
RE: This client isn't compatible with the media... - TheDreadPirate - 2024-03-09
The error is pretty obvious. Jellyfin does not have permission to some portion of your media path or your drive was unmounted.
What is the output of
Code:
cat /proc/mountsRE: This client isn't compatible with the media... - LittleHorus - 2024-03-09
/dev/sda3 / btrfs rw,seclabel,relatime,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/root 0 0
devtmpfs /dev devtmpfs rw,seclabel,nosuid,size=4096k,nr_inodes=989687,mode=755,inode64 0 0
tmpfs /dev/shm tmpfs rw,seclabel,nosuid,nodev,inode64 0 0
devpts /dev/pts devpts rw,seclabel,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
sysfs /sys sysfs rw,seclabel,nosuid,nodev,noexec,relatime 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
cgroup2 /sys/fs/cgroup cgroup2 rw,seclabel,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot 0 0
pstore /sys/fs/pstore pstore rw,seclabel,nosuid,nodev,noexec,relatime 0 0
efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
bpf /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 0 0
configfs /sys/kernel/config configfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /run tmpfs rw,seclabel,nosuid,nodev,size=1600636k,nr_inodes=819200,mode=755,inode64 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,nosuid,noexec,relatime 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=3808 0 0
mqueue /dev/mqueue mqueue rw,seclabel,nosuid,nodev,noexec,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,seclabel,nosuid,nodev,relatime,pagesize=2M 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,nosuid,nodev,noexec,relatime 0 0
tracefs /sys/kernel/tracing tracefs rw,seclabel,nosuid,nodev,noexec,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,nosuid,nodev,size=4001584k,nr_inodes=1048576,inode64 0 0
/dev/sda3 /home btrfs rw,seclabel,relatime,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/home 0 0
/dev/sda2 /boot ext4 rw,seclabel,relatime 0 0
/dev/sdb1 /data ext4 rw,seclabel,relatime 0 0
/dev/sda1 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
tmpfs /run/user/1000 tmpfs rw,seclabel,nosuid,nodev,relatime,size=800316k,nr_inodes=200079,mode=700,uid=1000,gid=1000,inode64 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
portal /run/user/1000/doc fuse.portal rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
(2024-03-09, 06:45 PM)TheDreadPirate Wrote: The error is pretty obvious. Jellyfin does not have permission to some portion of your media path or your drive was unmounted.
What is the output of
Code:cat /proc/mounts
RE: This client isn't compatible with the media... - TheDreadPirate - 2024-03-09
What kind of drive was your media stored on? The only mention of the path in the error is this mount.
Code:
tmpfs /run tmpfs rw,seclabel,nosuid,nodev,size=1600636k,nr_inodes=819200,mode=755,inode64 0 0And it is a tmpfs path.
RE: This client isn't compatible with the media... - LittleHorus - 2024-03-09
(2024-03-09, 07:11 PM)TheDreadPirate Wrote: What kind of drive was your media stored on? The only mention of the path in the error is this mount.
Code:tmpfs /run tmpfs rw,seclabel,nosuid,nodev,size=1600636k,nr_inodes=819200,mode=755,inode64 0 0
And it is a tmpfs path.
1TB WD Green hdd
The media is on the drive and I can play it using the Videos app in Linux, but doesn't play through Jellyfin locally or remotely.
RE: This client isn't compatible with the media... - TheDreadPirate - 2024-03-09
You need to step through the entire folder path and make sure that the Jellyfin user has sufficient permissions to access the files. Jellyfin doesn't need to own everything. But the "other" permissions needs to be at least r-x on every step of that path if Jellyfin doesn't own it.
RE: This client isn't compatible with the media... - LittleHorus - 2024-03-09
(2024-03-09, 08:27 PM)TheDreadPirate Wrote: You need to step through the entire folder path and make sure that the Jellyfin user has sufficient permissions to access the files. Jellyfin doesn't need to own everything. But the "other" permissions needs to be at least r-x on every step of that path if Jellyfin doesn't own it.
When I use chmod I get this:
chmod: cannot access '/data/Jellyfin': No such file or directory
I also did ls -al and got this:
drwxr-xr-x. 1 fedora fedora 0 Mar 9 01:15 'Jellyfin Server Media'
When I check the Disks app the drive is mounted, the mount point is /data. When I check +Other Locations it only shows my SSD and not the second drive. Sorry if that's not much help, fairly new to Linux.
RE: This client isn't compatible with the media... - TheDreadPirate - 2024-03-09
The problem is that the video you tried to play isn't located in /data/Jellyfin.
Code:
/run/media/fedora/Jellyfin/Jellyfin Server Media/tv shows/The long way down/Long Way Down (2).mp4: No such file or directoryIf you moved stuff around, you need to update the library to look in the correct location.
RE: This client isn't compatible with the media... - LittleHorus - 2024-03-09
(2024-03-09, 09:43 PM)TheDreadPirate Wrote: The problem is that the video you tried to play isn't located in /data/Jellyfin.
Code:/run/media/fedora/Jellyfin/Jellyfin Server Media/tv shows/The long way down/Long Way Down (2).mp4: No such file or directory
If you moved stuff around, you need to update the library to look in the correct location.
See attached screenshot, it is in that location and I have updated the library.
Code:
/run/media/fedora/Jellyfin/Jellyfin Server Media/tv shows/The long way down/Long Way Down (2).mp4: No such file or directoryThis was the location prior to making the drive auto mount. When I try to add the current location in Jellyfin it doesn't exist.
Code:
UUID=929ef080-13f6-4469-928c-9f24da4dfff8 / btrfs subvol=root,compress=zstd:1 0 0
UUID=bdd6b137-6751-4d03-864c-f7777de69c72 /boot ext4 defaults 1 2
UUID=517A-7130 /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=929ef080-13f6-4469-928c-9f24da4dfff8 /home btrfs subvol=home,compress=zstd:1 0 0
/dev/sdb1 /data ext4 defaults 0 0RE: This client isn't compatible with the media... - TheDreadPirate - 2024-03-09
Did you reboot or remount since changing /etc/fstab?