Quick update, I uninstalled node v8, installed v6 and now Filebot Node works.

I am trying to install and run Filebot Node on my QNAP TS 251+. When I run Filebot Node the web app starts but when I try to run the Dry Run option, a service unavailable error is shown. Here are the details from the log and what's installed: cat /share/CACHEDEV1_DATA/.qpkg/filebot-node/filebot-node ...

Just getting back to this and now trying to debug a new issue. My script produces a file not found error when my script initializes. I copied the runtime execution from Vuze and ran it in Terminal - here's the error: /usr/local/bin/filebot -script fn:amc --output /Volumes/Data/Video/ --log-file amc ...

Apologies for the quick response, the issue was an extra space after the output folder.
I guess I was tired and either accidentally added the space or just couldn't see the extra space.

Removing the space solved the issue.

Found the issue. I'm good for now.

Done and done - Filebot 4.7.2 is fully functional. I need assistance correcting a space being added to the target folder. Here's an example of what is being created when Command Runner executes my script (notice the space between Video and Movies) /Volumes/Data/Video/ /Movies/ Here's an execution ...

Here's the latest: Error from Vuze after changing the executable path: Executing: /usr/local/bin/filebot.sh -script fn:amc /Users/olivera/Documents/Vuze Downloads/1914 Frank Ocean Blonde 2016 320 --output /Volumes/Data/Video/ --log-file amc.log --action copy --conflict skip -non-strict --def music=n ...

Hello: I download and configured Vuze with their command runner; however, I am unable to successfully execute an AMC script using the script runner. The script works from a command line (without the %D variable). I am hoping you can assist me to get this going. Here are the details: Vuze version: 5 ...