The Strict Mode FileBot Node WebUI checkbox corresponds to the -non-strict command-line flag, i.e. you can set -non-strict by not checking Strict Mode.

License: FileBot License PX24200233 (Valid-Until: 2071-03-28) means that your license is valid and working. If the license was invalid or expired, filebot -script fn:sysinfo would print a corresponding error message instead. :idea: If you do get an error in some context (e.g. multiple users each us...

Click Execute ➔ Schedule and then copy the command from there:

If you label a call as Book or Bookmarks then you are forcing Unsorted Mode : Parameter: ut_label = Bookmarks Process as Unsorted [Bookmarks] :idea: If you use labels, then you'll want to label movies with --def ut_label=Movie and episodes with --def ut_label=TV , or rely on auto-detection by not la...

You cannot use QuickConnect anymore, since FileBot Node is now running independently of DSM. You will still have to log into DSM first. You must access DSM and FileBot Node via the same IP, as to create the DSM authentication cookie for that site in your browser. :idea: If you get an Unauthorized er...

I work with what I have. Unfortunately, you didn't provide file paths for testing. I ask for file paths because I need to recreate your file structure for testing, i.e. it needs to be exact and machine-readable. If I cannot recreate your file structure, then my answer will be generic. There are many...

Looks like there might be more than one result: I meant the second one:

find / -name filebot-node.log will find the log for you:

Thanks for the post! Before a real human comes by, please make sure your report has all the following points checked: What are you trying to do achieve? What's not working? What have you tried so far? Include screenshots , logs or filenames (i.e. demonstrate the issue) Include System Information (i....

I noticed that the link you sent points towards installing filebot-node-0.4.0-noarch.spk...would you advise I try this? Yep, if you're on DSM 6.2.4 then you have no choice but to use the latest beta. That will only fix the WebUI though, and likely won't fix permission issues. :idea: You may need to...

Considering that moving and renaming is a single file system operation (i.e. not two separate operations) as far as FileBot is concerned, meaning it can't really half work half not work, the behaviour your describe is most strange and unusual. My best guess would be some kind of display issue, i.e. ...

What does the log say?
viewtopic.php?t=11030

DSM 7.0 is all about implementing good security practices. Forcing each package to run as its own user / group with limited permissions is easy and just makes sense. Synology won't (and shouldn't) go back on that. Running everything as root was never a good idea in the first place.

Good catch! Fixed with FileBot r8373.

Only thing I noticed which I'm not sure of is that a warning appears if you do something in the Filebot Node GUI saying you shouldn't run filebot.sh as root. I believe it wasn't like this in the old version, only if you really ran filebot.sh as root via SSH or your scheduler for example. The filebo...

Looks like I generic file system / user permission issue. Did you recently disable the admin user by any chance?


This thread might be relevant:
viewtopic.php?p=54246#p54246

FileBot Node for Synology DSM 6.2.4 is available for testing: filebot-node-0.4.0-noarch.spk :!: You may need to uninstall older versions of FileBot Node, before manually installing the latest beta package. Upgrading the package may result in broken permissions caused by previously created user data...

These errors would suggest some kind of generic file system / user permission issue somewhat unrelated to FileBot Node or FileBot specifically: File does not exist: /Sync/Seedbox/2-To Process ... Invalid usage: output folder must exist and must be a directory: /Sync/Seedbox/3-Processed ... EDIT: Thi...

You can do Double-Click ➔ Edit Match ➔ Select both episodes to manually force a MultiEpisode match.





Please read FAQ #2 for general advice on how to deal with tricky files.

FileBot is more of a supporting tool, so FileBot will almost certainly follow wherever Plex and Kodi and friends end up going.

FileBot will make things work. We'll remain on the TheTVDB API v2 for the time being because that's what Plex is using. The most recent news is that things will keep working as they are for at least another half year. Wait and see. If you're worried about TheTVDB, then you can always use TheMovieDB ...

Thanks for the post! Before a real human comes by, please make sure your report has all the following points checked: What are you trying to do achieve? What's not working? What have you tried so far? Include screenshots , logs or filenames (i.e. demonstrate the issue) Include System Information (i....

DSM 6.2.4 seems to be rolling out to more devices since yesterday. I'll start working on a fix for DSM 6.2.4 once my DS213J auto-updates.

[FileBot Node] DSM 6.2.4 workaround

1. Did you restart the FileBot Node service after you mode your code changes? 2. If you continue to have trouble, please open the Developer Tools in your Browser so you can see each HTTP request and the corresponding error message: https://developer-chrome-com.imgix.net/image/BrQidfK9jaQyIHwdw91aVpk...