Bug on Synology DSM 6.2.4-25556

[marosell]

Updated to Synology DSM 6.2.4-25556 this afternoon, and Filebot Node will launch but won't run. It wiped the license and OpenSubtitle login, and it won't save the license file when I try to load it and nothing will execute. In fact, the interface won't do much at all. SSHed into the log file to check, and I have dozens of the following in a repeating pattern, and the internal IP address listed isn't an address associated with the NAS at all, it's one of the smart light-switches I have on my network so not sure why it's pinging it:

2021-03-29T18:43:32-0500 /usr/syno/synoman/webman/modules/authenticate.cgi
2021-03-29T18:43:32-0500 {
HTTP_COOKIE: 'id=null',
HTTP_X_SYNO_TOKEN: 'eTjRJzaLaBsDE',
REMOTE_ADDR: '10.0.1.22'
}

Posting just in case I'm the first person to have the issue. Thoughts appreciated. Thanks!

[rednoah]

Unfortunately, DSM 6.2.4 fundamentally breaks FileBot Node cookie authentication:
viewtopic.php?t=12453


The only known workaround is to disable authentication, but that's only viable if you have a completely secure local network that only you use:
viewtopic.php?p=53906#p53906

[marosell]

It's a local home network, and I'm the only one that uses it, but that scares me a bit. I'll look into it a bit more before I decide to try it. Any ETA on developing an update for the newer DSM authentication method(s), or is this the end of FileBot on Synology?

[rednoah]

It's a local home network, and I'm the only one that uses it, but that scares me a bit. I'll look into it a bit more before I decide to try it. Any ETA on developing an update for the newer DSM authentication method(s), or is this the end of FileBot on Synology?

There is no ETA for DSM 6.2.4 support, mainly due to DSM 6.2.4 not being available for the majority (?) of Synology devices yet. Plus DSM 7.0 is right around the corner which is already supported.

[drsteveplatt]

Well that sucks! 6.2.4 is in increasingly wider release, and 7.0 won't be out for months. Even then, we choose to delay major release upgrades until (a) we are sure they are stable, and (b) we have tested in-house.

We've lost one Syno's ability to run filebot. We cannot upgrade our other one to 6.2.4 until filebot is running on it. I'm hoping the filebot staff will prioritize the repair for 6.2.4.

Yes, I'm a permanent license holder, and I would appreciate the support!

[rednoah]

We've lost one Syno's ability to run filebot. We cannot upgrade our other one to 6.2.4 until filebot is running on it. I'm hoping the filebot staff will prioritize the repair for 6.2.4.

Well, filebot itself is running fine. FileBot Node is just a WebUI that generates commands, so advanced users can skip FileBot Node entirely, either by writing commands manually, or by using FileBot Node in a docker container to generate commands that you can then copy & paste into SSH or Synology Task Scheduler.


Do you have an armv7 / aarch64 device that got the DSM 6.2.4 upgrade? Based on the forum posts here, that update seems to be exclusive to Intel-based devices, and docker is always an option for Intel-based devices, as opposed to ARM based devices where docker is indeed not an option. If one of my DS213J or DS120J test devices gets the upgrade, then I will be able to reproduce and debug the problem.


A key concern is making things work on DSM 6.2.4 without breaking things for everyone else, without maintaining multiple repositories, which may not be possible based on our DSM 7 experience.

[rednoah]

[FileBot Node] DSM 6.2.4 workaround

[drsteveplatt]

Many thanks, rednoah, the beta is working on my 916+. My 1515+ is still on the old OS version, I think I'll leave it there for a while.

Good job in getting the update out. Muchly appreciated!