FileBot

Maybe not a specific FilBot error but.
I have two Synology NAS:es (DSM 7 both). Currently I use the second to store media.
I have remote mounted the target directory to my "FileBot" NAS as a remote directory via CIFS via NAS GUI.
I have no problems accessing the "remote" map or manually copy files, BUT ...
when I run filebot, via FileBot Node (or via scheduler), I get an i/o error when it tries to move the renamed file.
I have tried to check access rights but I) see nothing strange.
Users "xxxx" (member of admin) ; "users" ; "Everyone" on my fist NAS has full access to the remote directory.
And directory is cifs mounted as me "xxxx"

I don't get the problem?. Does FileBot script run as a different user??

If you're using FileBot Node then the filebot command is likely executed by the FileBot user. You can click the System Info button to confirm.


Installing FileBot on Synology NAS › Package Permissions



If you're using the Synology Task Scheduler then the filebot command is executed as the user you have configured for the task at hand. Commands executed via the FileBot Node WebUI and the Synology Task Scheduler may therefore run as different users by default.

I changed the user running the scheduling task and that resolved that problem. Now that works.... Great!!

However I was not able to fix the problem with FileBot Node.
I can't give the FilBot user direct permission directly to the mounted directory because then I get a DSM message about Windows ACL not allowing...
And if I tried giving user FileBot read/write to the whole "top level" directory, but It still fails.

But I guess that is more a Synology problem than a FilleBot one..

Thank you!

palle wrote: ↑08 Aug 2025, 19:12 But I guess that is more a Synology problem than a FilleBot one..

Yep, permissions can be tricky, especially if a remote file system is involved. Furthermore, on a Synology NAS, the ACL permissions can override the classic Unix permissions. Unfortunately, you cannot configure the package to run as a different user to workaround permission issues since Synology DSM runs packages as their own user for security reasons.


As a workaround, you can always organize files locally first (using hardlinks so you don't need extra disk space) and then move organized folders onto the target device in a second step later on.