Page 1 of 1
New to QNAP setting up Filebot questions.
Posted: 25 Jul 2025, 14:22
by nzdreamer55
Hello everyone. I have switched over to Qnap and am running hero OS. I started going down the path of setting up stuff in docker and using portainer, but am having some troubles with this route of not getting filebot to work. I chalk it up to me not really knowing what I am doing (with filebot and in life
So I ditched chatgpt for help and started looking on the forums and saw this!
viewtopic.php?t=6014
So I set up the repository and installed the 3 items that were available. I noted I don't have an ad blockers on my browsers. Restarted qNAP
When I click on the filebot app in the center, I was expecting to get the familiar web/app interface I have seen on windows installs then realized it is filebot node! So I opened this and see this info
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
So wondering what the next step is in my journey (other than trying to learn!)
Maybe some kind sole could point me in the right direction. Thank you.
Steve
P.S. Since I am using portainer for my other things (Sonarr, emby, etc) should I be setting up filebot in a container? Pro's...Con's...?
Re: New to QNAP setting up Filebot questions.
Posted: 25 Jul 2025, 14:43
by rednoah
1.

What does the log say?
FileBot Node Troubleshooting will get you started with troubleshooting the QNAP package.

Did you install the
Node.js or
Media Streaming Add-on package?
rednoah wrote: ↑05 Jul 2018, 02:53
FileBot Node requires
node. You will need to install the latest
Node.js package. Alternatively, you can also install the
Media Streaming Add-on which happens to include a viable
node executable.
2.

If you prefer to run a
docker container then you'll want to read the
docker manual for available containers. If you want to run the FileBot Desktop application in a remote Linux Desktop environment, then
filebot-xpra is what you want to run.
Re: New to QNAP setting up Filebot questions.
Posted: 25 Jul 2025, 14:51
by nzdreamer55
Thanks so much rednoah! You are always so helpful. I realize that this is might be impossible to answer, but if I have other apps in docker containers, should I stick with this pattern? I am new to containers so just learning. Hopefully picking a system that is not going to take a lot of upkeep so that I can put energy towards other things than system maintenance.
Re: New to QNAP setting up Filebot questions.
Posted: 25 Jul 2025, 15:00
by rednoah
docker is
not easy or user-friendly but it is the de-factor standard for deploying web applications. There is a lot of software for which you will not find a QNAP package.

If you want to run something like
filebot-xpra then
docker is your only choice. That said, I'd just use the FileBot Desktop application from my Desktop as usual and move / rename files remotely via SMB network shares.
EDIT:
Unattended Automation with FileBot Node might give you some ideas for setting up automation. A important factor here is how you acquire files in the first place, e.g. if you have a qBT container and want to run the
amc script on newly completed downloads then you will run into
this kind of problem.
Re: New to QNAP setting up Filebot questions.
Posted: 25 Jul 2025, 16:33
by nzdreamer55
Really appreciate the help. I found the log and got this...
Console Output: Select all
-------------------- Run /share/ZFS530_DATA/.qpkg/filebot-node/start (PID: 28127) -------------------- Fri Jul 25 06:58:35 PDT 2025
NODE=
[node: command not found] Please install 'Node.js' or 'Media Streaming Add-on' in the App Center.
/share/ZFS530_DATA/.qpkg/filebot-node/filebot-node-service.sh: line 26: kill: `': not a pid or valid job spec
-------------------- Run /share/ZFS530_DATA/.qpkg/filebot-node/start (PID: 26590) -------------------- Fri Jul 25 07:17:42 PDT 2025
NODE=
[node: command not found] Please install 'Node.js' or 'Media Streaming Add-on' in the App Center.
When I look at the AppCenter, it shows that it is installed. There are ! by them, but I think that is because they are not signed?
Steve
Re: New to QNAP setting up Filebot questions.
Posted: 25 Jul 2025, 17:01
by rednoah

The
node executable does not seem to be in any of the expected file paths:
https://github.com/filebot/filebot-node ... /start#L51

Does a
node executable exist anywhere on your system?
Shell: Select all
find / -type f -name node 2> /dev/null
Re: New to QNAP setting up Filebot questions.
Posted: 25 Jul 2025, 19:21
by nzdreamer55
Just ran this and I have no idea what this means!!!
Console Output: Select all
$ find / -type f -name node 2> /dev/null
/proc/irq/0/node
...
So yes?
Re: New to QNAP setting up Filebot questions.
Posted: 25 Jul 2025, 19:26
by nzdreamer55
Re: New to QNAP setting up Filebot questions.
Posted: 26 Jul 2025, 06:49
by rednoah

The console output above confirms that
no node executable is installed anywhere on your system.
/proc is just system information presented as file system.

I have looked at the screenshot and I do
not see a
Node.js package or a
Media Streaming Add-on package installed? Have you not yet tried installing the
Node.js package or the
Media Streaming Add-on package from the QNAP repository?
Console Output: Select all
[node: command not found] Please install 'Node.js' or 'Media Streaming Add-on' in the App Center.
Re: New to QNAP setting up Filebot questions.
Posted: 26 Jul 2025, 13:07
by nzdreamer55
Hi Noah. Thanks for taking a look at the image. I added the filebot repository (I think) and then "installed" the 3 items that were available to install so I kind of assumed that would do it. Should that have worked?
Re: New to QNAP setting up Filebot questions.
Posted: 26 Jul 2025, 13:12
by rednoah
nzdreamer55 wrote: ↑Today, 13:07
I added the filebot repository (I think) and then "installed" the 3 items that were available to install so I kind of assumed that would do it. Should that have worked?

If you want to run
FileBot Node then you need to install either the
Node.js package or the
Media Streaming Add-on package from the
QNAP Store as well.