Flood 4.8.4 not starting

[joydashy]

I did a fresh seedbox install today (new user), getting this on flood logs:

Node.js v22.9.0
Flood server 4.8.4 starting on http://0.0.0.0:3000

Starting without builtin authentication

node:internal/process/promises:392
      new UnhandledPromiseRejection(reason);
      ^

UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "undefined".
    at throwUnhandledRejectionsMode (node:internal/process/promises:392:7)
    at processPromiseRejections (node:internal/process/promises:475:17)
    at process.processTicksAndRejections (node:internal/process/task_queues:106:32) {
  code: 'ERR_UNHANDLED_REJECTION'
}

In the web UI I get only "Bad Gateway".

[jfroment]

Hello, did you follow the documentation here: https://github.com/jfroment/seedbox/blob/v2.2/doc/apps/deluge-flood.md ?

Also, now that v2.2 is out, you also have the option to use qbittorrent instead. I do not use deluge anymore myself, but I'll try to see if I can reproduce your issue.

[Sigri44]

Gm, think need to add FLOOD_DELUGE_HOST=deluge var into .env.custom ?

[jfroment]

Hello, yes indeed.
You can also pull changes, there was a bug with Flood so I released 2.2.1.

[jfroment]

Well, maybe I answered too quickly on this issue. In fact no you should not set this variable in .env.custom.

This variable is automatically determined by the run-seedbox.sh script here.
Setting it manually should not have any side-effect (except set the wrong value), but it's better to let the script determine it automatically.

[jfroment]

Also, a new release v2.2.2 has now been released with other fixes on Deluge/Flood autoconfig.