2023-12-31, 10:13 AM
(This post was last modified: 2023-12-31, 10:18 AM by Efficient_Good_5784. Edited 2 times in total.)
Are you using the scheduled task method or docker compose method from the guide you linked? Keep in mind with the container manager app, you can now use yaml files to launch apps.
Also, what the guide is showing you to do is something that can be done directly on the system shell. Synology has access to the shell with SSH turned off by default, but if you turn it on, you can SSH into your NAS and run the command directly. I don't understand why Synology units don't have an interface built in to directly access the shell from the main web GUI. The guide is showing that you can use the scheduled task feature to run a command like you normally would on a shell interface.
If you're doing the scheduled task method, try removing the whole -u flag line. It should put Jellyfin to run as root which should have access to all of your linked folders.
If this fixes the issue, then it's a permissions issue. The user you configured to the Jellyfin container doesn't have access to the folder. You'll have to remake the container with a user that does, or give the existing user permissions to access the folders you want.
A bit of a side note. If you want, I can explain how to create and launch a docker container using yaml files through the shell of your nas. You'll avoid having to make an automated task to launch the docker image. And since you can store yaml files, making changes to containers (or updating to a new image) is just editing an exiting yaml file instead of redoing a large docker run command each time.
Also, what the guide is showing you to do is something that can be done directly on the system shell. Synology has access to the shell with SSH turned off by default, but if you turn it on, you can SSH into your NAS and run the command directly. I don't understand why Synology units don't have an interface built in to directly access the shell from the main web GUI. The guide is showing that you can use the scheduled task feature to run a command like you normally would on a shell interface.
If you're doing the scheduled task method, try removing the whole -u flag line. It should put Jellyfin to run as root which should have access to all of your linked folders.
If this fixes the issue, then it's a permissions issue. The user you configured to the Jellyfin container doesn't have access to the folder. You'll have to remake the container with a user that does, or give the existing user permissions to access the folders you want.
A bit of a side note. If you want, I can explain how to create and launch a docker container using yaml files through the shell of your nas. You'll avoid having to make an automated task to launch the docker image. And since you can store yaml files, making changes to containers (or updating to a new image) is just editing an exiting yaml file instead of redoing a large docker run command each time.