Filebot Node 0.4.3 on Synology DSM 7.0.1-42218 Update 3: "Unauthorized"

[thomaswimmer]

Hi,

Filebot Node (0.4.3) stopped working on my Synology NAS. Worked a couple of weeks ago. Details:

Filebot Node 0.4.3
Filebot 4.9.6
DSM 7.0.1-42218 Update 3
Node.js v16 161.13.1-1006

On start of filebot node a pop-up windows states "Unauthorized" (also on everytime I tried to run filebot from filebot-node).

Running filebot on terminal (from ssh for example) workes fine).

The (system internal user) permissions for user filebot are set to Read/Write on the relevant share.
Re-installing filebot, filebot-node and restarting the NAS didn't help.

Any pointers? Deeper dive into DSM permissions?
Release note for DSM 7.0.1-42218 Update 3: Synology

Thomas

[rednoah]

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

[thomaswimmer]

Code: Select all

{
  cmd: '/usr/syno/synoman/webman/authenticate.cgi',
  env: {
    HTTP_COOKIE: 'id=4594c55b-c28c-4cbb-b103-f67e1fb51f4b&created=1651772564715&expire=1651773523419',
    REMOTE_ADDR: '172.16.26.1',
    HTTP_X_SYNO_TOKEN: undefined
  }
}

[rednoah]

Have you tried logging out of DSM, and the logging in again?


Since X-Syno-Token seems to be a problem here, you could try to disable that authentication feature:



If you can't get it working, then you can always disable authentication altogether:
viewtopic.php?t=12516

[thomaswimmer]

Logging out and in didn't work.

This is my current setting:


So that wasn't the solution either.

Disabling authentication: I tried the one you labelled "Option B", ignoring the statement "FileBot Node 0.3.1 and lower" and the fact that the tread is for DSM 6, but I don't have a "/var/packages/filebot-node/target/start":

Code: Select all

ls -l /var/packages/filebot-node/target/
total 0
drwxr-xr-x 1 FileBot FileBot  70 May 25  2021 bin
drwxr-xr-x 1 FileBot FileBot 344 May  4 20:48 client
drwxr-xr-x 1 FileBot FileBot 102 May  4 20:48 server

Anything more I can try?

[rednoah]

You will likely find the start script in the bin folder. It might be named filebot-node-start on DSM 7 but the script itself and the environment variables it configures should work the same on all platforms.



If the "Improve protection against cross-site request forgery attacks" was turned off already, then you could try turning it on (and then logging off on onto DSM again) to see if that makes a difference. At least that should get rid of the HTTP_X_SYNO_TOKEN: undefined problem. That would be the notably unusual thing.



EDIT:

On that note, does your log not start with the current date / time (that would be a clue) or did you selectively copy & paste only the last few lines?


e.g. I ran a test on my DS120J / DSM 7.0.1-42218 Update 3 and the log looks like this:

Code: Select all

$ cat /var/packages/filebot-node/var/filebot-node.log

-------------------- Run /volume1/@appstore/filebot-node/bin/filebot-node-start (PID: 19041) -------------------- Fri May  6 14:59:10 WIB 2022

ENVIRONMENT {
  FILEBOT_CMD: 'filebot',
  SYNOPKG_PKGVAR: '/volume1/@appdata/filebot-node',
  SYNOPKG_USERNAME: 'rednoah',
  OLDPWD: '/',
  SYNOPKG_PKGNAME: 'filebot-node',
  SYNOPKG_DSM_VERSION_MAJOR: '7',
  JAVA_OPTS: '-Xmx391m',
  FILEBOT_CMD_GID: '106247',
  SYNOPKG_PKGHOME: '/volume1/@apphome/filebot-node',
  SYNOPKG_DSM_VERSION_MINOR: '0',
  SYNOPKG_PKGTMP: '/volume1/@apptemp/filebot-node',
  SYNOPKG_DSM_VERSION_BUILD: '42218',
  SELF: 'filebot-node',
  PWD: '/var/packages/filebot-node/target',
  SYNOPKG_PKGVER: '0.4.3',
  FILEBOT_NODE_DATA: '/var/packages/filebot-node/var',
  SYNOPKG_DSM_LANGUAGE: 'enu',
  SYNOPKG_DSM_ARCH: 'armada37xx',
  FILEBOT_NODE_HTTP: 'YES',
  FILEBOT_NODE_AUTH: 'SYNO',
  SYNOPKG_PKGDEST_VOL: '/volume1',
  FILEBOT_TASK_CMD: 'filebot-node-task',
  SHLVL: '2',
  FILEBOT_CMD_CWD: '/volume1',
  SYNOPKG_PKG_STATUS: 'START',
  PATH: '/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin',
  FILEBOT_NODE_HOST: '127.0.0.1',
  FILEBOT_NODE_HTTP_PORT: '5452',
  FILEBOT_CMD_UID: '106247',
  SYNOPKG_TEMP_LOGFILE: '/tmp/synopkgmgr.log-filebot-node',
  SYNOPKG_PKGDEST: '/volume1/@appstore/filebot-node'
}
STATUS {
  pid: 19041,
  node: 'v12.22.7',
  uptime: '2',
  date: 'Fri, 06 May 2022 07:59:12 GMT'
}
USER { UID: 106247, GID: 106247 }
filebot-node listening at http://127.0.0.1:5452
{
  cmd: '/usr/syno/synoman/webman/authenticate.cgi',
  env: {
    HTTP_COOKIE: 'id=mpq...',
    REMOTE_ADDR: '10.0.0.26',
    HTTP_X_SYNO_TOKEN: 'ZAj...'
  }
}
{
  auth: {
    cookie: 'id=mpq...',
    'X-Syno-Token': 'ZAj...'
  },
  user: 'rednoah'
}

[thomaswimmer]

I did let it go for about a day, and now everything works again. Maybe one of the fiddling was the key.
To your points:
Thanks for your pointer where to find the filebot-node startup skript.
Again, one of the options switching on and off probabely did it.
I did cut the logfile to the relevant part, as there was a lot of repeating entries.

Again, thanks for your effort.

Thomas