Unable to connect to FileBot Node web interface

Support for Synology NAS, QNAP NAS and other Embedded Linux systems
Post Reply
macdis
Posts: 4
Joined: 02 Dec 2022, 22:36

Unable to connect to FileBot Node web interface

Post by macdis »

Hi. I have a newly installed Synology DS220+ running DSM 7.1.1-42962.

I'm trying to run FileBot Node 0.4.3 and I can't open the web interface. I get an "unable to connect" message. I'm logged in to an admin user account (but not the "admin" account).

The package interface works fine (if I just "open" the package in DSM).

Curl test returns this from a machine on my home network (same network as Synology):

Code: Select all

$ curl -v http://10.1.1.99:5452
*   Trying 10.1.1.99:5452...
* connect to 10.1.1.99 port 5452 failed: Connection refused
* Failed to connect to 10.1.1.99 port 5452 after 19 ms: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 10.1.1.99 port 5452 after 19 ms: Connection refused
I have no problem connecting to DSM via http://10.1.1.99:5000

FileBot Node log says this:

Code: Select all

$ cat /volume1/@appdata/filebot-node/filebot-node.log

-------------------- Run /volume1/@appstore/filebot-node/bin/filebot-node-start (PID: 3177) -------------------- Fri Dec  2 17:14:16 EST 2022

ENVIRONMENT {
  FILEBOT_CMD: 'filebot',
  SYNOPKG_PKGVAR: '/volume1/@appdata/filebot-node',
  SYNOPKG_USERNAME: 'iain',
  OLDPWD: '/',
  SYNOPKG_PKGNAME: 'filebot-node',
  SYNOPKG_DSM_VERSION_MAJOR: '7',
  JAVA_OPTS: '',
  FILEBOT_CMD_GID: '106247',
  SYNOPKG_PKGHOME: '/volume1/@apphome/filebot-node',
  SYNOPKG_DSM_VERSION_MINOR: '1',
  SYNOPKG_PKGTMP: '/volume1/@apptemp/filebot-node',
  SYNOPKG_DSM_VERSION_BUILD: '42962',
  SELF: 'filebot-node',
  PWD: '/var/packages/filebot-node/target',
  SYNOPKG_TEMP_REPLACE_FOLDER: '/volume1/@tmp/synopkg.tmp/filebot-node',
  SYNOPKG_PKGVER: '0.4.3',
  FILEBOT_NODE_DATA: '/var/packages/filebot-node/var',
  SYNOPKG_DSM_LANGUAGE: 'enu',
  SYNOPKG_DSM_ARCH: 'geminilake',
  SYNOPKG_PKG_PROGRESS_PATH: '/tmp/install_progress_filebot-node',
  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: 'INSTALL',
  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: 3177,
  node: 'v18.12.0',
  uptime: '0',
  date: 'Fri, 02 Dec 2022 22:14:16 GMT'
}
USER { UID: 106247, GID: 106247 }
filebot-node listening at http://127.0.0.1:5452
The weird thing is: if I uninstall the package and start FileBot Node via a docker-compose.yml file, the web interface opens no problem. For example, this works:

Code: Select all

$ docker-compose --version
docker-compose version 1.28.5, build 24fb474e

$ cat docker-compose.yml
services:
  filebot-node:
    container_name: filebot-node
    image: rednoah/filebot:node
    restart: unless-stopped
    volumes:
      - /volume1/media:/media
    ports:
      - 5452:5452

I have the following installed:
FileBot package v4.9.6
Node.js v18 (I tried v16 too)
openjdk 17.0.5 2022-10-18 (installed as per FileBot instructions)

I've also granted RW access to the media folder to system internal user FileBot.

The Synology firewall is not turned on.

FileBot sysinfo shows this:

Code: Select all

$ filebot -script fn:sysinfo
FileBot 4.9.6 (r9125)
JNA Native: 6.1.2
MediaInfo: 19.04
Tools: 7z/16.02 unrar/5.70
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2022-08-15 (r836)
Groovy: 3.0.9
JRE: OpenJDK Runtime Environment 17.0.5
JVM: OpenJDK 64-Bit Server VM
CPU/MEM: 2 Core / 446 MB Max Memory / 24 MB Used Memory
OS: Linux (amd64)
HW: Linux codex 4.4.180+ #42962 SMP Tue Oct 18 15:07:03 CST 2022 x86_64 GNU/Linux synology_geminilake_220+
CPU/MEM: Intel(R) Celeron(R) J4025 CPU @ 2.00GHz [MemTotal: 1.8 GB | MemFree: 226 MB | MemAvailable: 1.0 GB | SwapCached: 16 KB | SwapTotal: 3.3 GB | SwapFree: 3.2 GB]
STORAGE: ext4 [/] @ 6 GB | btrfs [/volume2] @ 4.3 TB | btrfs [/volume1] @ 7 TB
USER: iain
DATA: /var/packages/filebot/var/data/1026
Package: SPK
License: FileBot License XXXXXXXX (Valid-Until: 2070-01-04)
I’ve tried uninstalling, rebooting, reinstalling.

Any ideas? Thanks in advance!
User avatar
rednoah
The Source
Posts: 21521
Joined: 16 Nov 2011, 08:59

Re: Unable to connect to FileBot Node web interface

Post by rednoah »

macdis wrote: 02 Dec 2022, 23:11 The package interface works fine (if I just "open" the package in DSM).
FileBot Node requires DSM authentication, so you have to use FileBot Node like this. Since the WebUI is embedded as IFRAME you can however access it directly, assuming that you have DSM login cookies in your browser session already:

Code: Select all

http://<IP>:5000/webman/3rdparty/filebot-node/index.html

:idea: Use Right-Click ➔ View Frame Source to check the URL of any IFRAME.

Code: Select all

filebot-node listening at http://127.0.0.1:5452
:idea: This means that the FileBot Node service is bound to the localhost, so only the localhost (i.e. the NAS itself) can connect to the service. And you can only access the service indirectly via the DSM web service which internally proxies requests to the FileBot Node service.
:idea: Please read the FAQ and How to Request Help.
macdis
Posts: 4
Joined: 02 Dec 2022, 22:36

Re: Unable to connect to FileBot Node web interface

Post by macdis »

Ahhh, I see. I guess I was misled by the LAN-accessibility of the docker-compose method of using FileBot Node. May I ask, then, whether there any other interesting advantages or disadvantages to using either the package or docker-compose methods?
User avatar
rednoah
The Source
Posts: 21521
Joined: 16 Nov 2011, 08:59

Re: Unable to connect to FileBot Node web interface

Post by rednoah »

Accessing FileBot Node via DSM has the advantage that it'll work if DSM works, including DSM access via Synology QuickConnect.

If you use the docker container, then you can configure FileBot Node, e.g. use authentication or not, and no authentication is default. This can be a severe security issue, or a nice convenience if you don't care about security on your local network.
:idea: Please read the FAQ and How to Request Help.
Post Reply