2025-02-21, 06:15 PM
You don't mention how you installed Jellyfin. If you didn't install it directly on the host, you may have additional permissions issues with running in a container/flatpak/snap/etc. There are ways to grant permissions to non-standard locations for each of these.
If you did install Jellyfin directly on the host, only after you've mounted it, you should be able to change permissions on the directory. My experience in Ubuntu has been you need to create the directory, mount it with fstab the first time, then sudo chown to the desired owner.
It's also a good idea to store files in a subdirectory of the mount point. This way, if the mount point becomes disconnected, your app does not assume you've deleted all the files and auto update your library. Instead, if the mount point becomes disconnected, you should get a directory not found error. At least that's the way my other apps work...
If you did install Jellyfin directly on the host, only after you've mounted it, you should be able to change permissions on the directory. My experience in Ubuntu has been you need to create the directory, mount it with fstab the first time, then sudo chown to the desired owner.
It's also a good idea to store files in a subdirectory of the mount point. This way, if the mount point becomes disconnected, your app does not assume you've deleted all the files and auto update your library. Instead, if the mount point becomes disconnected, you should get a directory not found error. At least that's the way my other apps work...