Just for info.

I also have a number of schedules set up to run on the NAS via FileBot/Task Scheduler. I had to remake the schedules and delete the old ones as the old ones were not picking up the {plex} parameter changes, the new schedules appear to be doing so.

Rednoah Many thanks, got there! The issue I was having was that I was typing {plex} into the 3 fields (Movie/Series/Anime Formats) and then closing FileBot down. When I came to run FileBot again and tried running it at a later time all three fields were greyed out again. It looks like you have to ...

OK. Here it is: filebot -script 'fn:amc' /volume1/Shared --output /volume1/Media --action move -non-strict --order Airdate --conflict auto --lang en --def 'clean=y' 'skipExtract=y' 'movieDB=TheMovieDB' 'seriesDB=TheTVDB' 'animeDB=TheMovieDB::TV' 'excludeList=.excludes' --apply refresh --log all ...

rednoah Many thanks for getting back to me. I'm fairly sure that FileBot is working as it should. The only difference being that any new series files since the update are now stored in a different directory, 'Alias' {tmdb} xxxxxx instead of 'Alias'. That's all working fine, no issues at all. However ...

Hi All I have seen all the warnings on FileBot Node: [PSA] Important Discussion of Proposed Changes: https://www.filebot.net/forums/viewtopic.php?t=13406 And was rather hoping that it would have no impact, I was wrong. My system is a Synology NAS, interrogated by Kodi (RPi). Since the latest update ...

For Info.

DSM 7 just prompted me to update FileBot Node v0.4.1 to v0.4.2.

Updated, all fine.

Ta.

Just upgraded to the release candidate version DSM 7. I uninstalled Java, FileBot and Filebot Node prior to the upgrade. Completed the upgrade then reinstalled (manual install of correct files), had to remove Node.js v8 as it was no longer supported in the new DSM version and installed Node.js v12 ...

And that worked.

Apologies if I was unintentionally at fault.....trying my best!

Regards

Dave

As requested;; total 28 -rw-r--r-- 1 root root 122 Apr 7 07:16 dsm.filebot-node.conf -rw-r--r-- 1 root root 72 May 22 14:59 dsm.ssdp.conf -rw-r--r-- 1 root root 192 May 22 14:59 dsm.StorageAnalyzer.conf -rw-r--r-- 1 root root 282 May 22 17:03 dsm.synorelayd.conf -rw-r--r-- 1 root root 0 May 22 14:58 ...

rednoa URL is on the local network: 192.168.1.xx:5001. Selected the FileBot Node icon from within the DSM UI. This is with 'Improve protection against cross-site request forgery attacks' NOT selected https://am3pap002files.storage.live.com/y4mI7Y_atXE2G-vVxkkMIKw1eUhCUdX2hWIch8f1ofOwXTVcFOc8IU6CTpDS ...

Ha! Tried that as well, got the the following error message in the FileBot window:

Full log below: FILEBOT_TASK_CMD: 'filebot-node-task', TERM: 'vt102', FILEBOT_CMD_UID: '0', SYNOPKG_TEMP_LOGFILE: '/tmp/synopkgmgr.log-filebot-node', SYNOPKG_DSM_ARCH: 'apollolake', OLDPWD: '/', JAVA_OPTS: '', FILEBOT_CMD_CWD: '/volume1', PATH: '/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno ...

rednoah It was already enabled. However, logged out and then back in again. Log still shows { HTTP_COOKIE: 'id=FL7F7x99WixPyJDacRX-gBVuacX_VOaj3247036GpB8bohytQ3iRG75JIJ32KZ_f4wRF2q0Mr_b4uCalAFkE3M', REMOTE_ADDR: '192.168.1.2', HTTP_X_SYNO_TOKEN: undefined } https://am3pap002files.storage.live.com ...

Just uninstalled FileBot 0.4.0, rebooted and installed Filebot 0.4.1. Ran it and unauthorised again. Log File below: ENVIRONMENT { SYNOPKG_DSM_LANGUAGE: 'def', FILEBOT_TASK_CMD: 'filebot-node-task', TERM: 'vt102', FILEBOT_CMD_UID: '0', SYNOPKG_TEMP_LOGFILE: '/tmp/synopkgmgr.log-filebot-node ...

rednoah System is DS218+ using DSM 6.2.4, all up to date. FileBot up and working fine with FileBot Node 0.4.0. Uninstalled FileBot Node 0.4.0 and installed 'filebot-node-0.4.1.spk'. Rebooted and it came back with 'Unauthorised', permissions all OK. Unistalled 0.4.1 and rolled back to 0.4.0 ('filebot ...

Perfect.

Once again, thank you.

Dave

rednoah. Well all back up and running well. Have you any idea of what the new 'User Defined Script' should be to run FileBot from within the DSM Task Scheduler? I've tried the following without success: /volume1/@appstore/filebot/filebot.sh /usr/local/filebot-node/task 0 ((worked with the previous ...

Thank you. I'll have a play around and see if I can get FileBot back up and running again.

Ahh....I may have found the reason for not seeing the newly opened FileBot page when opening FileBot from within DSM. I use my Quickconnect ID to log into DSM. Just switched to using the local IP address and that opens FileBot in a new page and I can see all the settings. I've updated the input ...

And here is the result from 'sudo cat /volume1/@appstore/filebot-node/filebot-node.log' https://am3pap002files.storage.live.com/y4mMFCKUPg8FrwtSRyNVTYB6E4gGsGz8Is-m-AM9arhbAmqBRWFeMBnKl_k4R6SR4hwF2XKDPbUTDfcdbQUWCrhdNCPi6OTaPVQ-e9Lr8_UUJX6j0QNb4zoSDWjdL6kBCXw4CWbOqYa9r_jTcq ...

Ahh, found it under /var/log/packages/filebot-node.log Stopped the FileBot Node process at 1658hrs via DSM and restarted a couple of seconds later. https://am3pap002files.storage.live.com/y4mK0G2TdBFzRhFzurqYCAcNKngEg7vB3lfn9bSyV9fApEW021MKbEJK1M3an3K3c2d1np0Xtsu4zTsmBITio8iD ...

rednoah I've managed to SSH into the NAS but being a bit of a noob I've no idea how to open the file and I'm not so sure that it is there. Below is a dump from putty showing the contents of the directory. https://am3pap002files.storage.live.com ...

rednoah. Many thanks for the update but for me it failed. I set up a custom administrator account several months ago and disabled the old admin account. I manually installed the filebot-node-0.4.0-noarch.spk file and followed the on-screen instructions post the install allowing filebot Read/Write ...

For rednoah

I too have the same issue with FileBot post the 6.2.4 update last night.

I'm not that savvy when it comes to SSH or Docker, is it worth waiting for an update for FileBot to fix the issue or are you focussed on the forthcoming DSM 7 release (finger's crossed).

Regards

Dave

Many thanks, all sorted. Happy teddy bear