Skip to content
This repository was archived by the owner on May 31, 2021. It is now read-only.

Troubleshooting

Jump to bottom
JW edited this page Mar 22, 2019 · 8 revisions

Troubleshooting

Errors with node-sass

Errors due to migration from Node.js v8 to Node.js v9. Example: Module build failed: Error: ENOENT: no such file or directory, scandir '/srv/flood/node_modules/node-sass/vendor'. Another example:

Module build failed: Error: Missing binding /srv/flood/node_modules/node-sass/vendor/linux-x64-59/binding.node
Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 9.x

Fix:

  • npm update node-sass
  • npm run build

See Issue 533.

module build version

Example:

$ npm start

> [email protected] start /srv/flood
> node server/bin/start.js

Failed to start web server:
Error: The module '/srv/flood/node_modules/argon2/build/Release/argon2.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 59. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node server/bin/start.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/flood/.npm/_logs/2017-11-26T23_43_14_556Z-debug.log

Another example:

$ npm start

> [email protected] start /srv/flood
> node server/bin/start.js

Failed to start web server:
Error: The module '/srv/flood/node_modules/bcrypt/lib/binding/bcrypt_lib.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 59. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node server/bin/start.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/flood/.npm/_logs/2017-11-26T23_59_08_444Z-debug.log

Fix:

  • npm rebuild -a
  • npm run build

If not working try this:

  • rm -rf node_modules
  • npm i
  • npm run build

stuck after log in

See flood logs or check systemctl status flood if installed as a service.

If you get a line like npm[10172]: Connection refused at 127.0.0.1:5005. Check these values in config.js and ensure that rTorrent is running. that means that rTorrent is not running. So start it back.

Can't access web UI even though Flood starts correctly

If you are running Flood on a host other than your local machine, change the floodServerHost key in config.js to listen on all interfaces:

floodServerHost: '0.0.0.0'

I modified baseURI, it's not working anymore.

Each time you modify baseURI in config.js you need to recompile assets (npm run build). To be sure follow the Updating procedure each time you modify the config.js file.

node-gyp with sudo not working

Since #523 node-gyp is needed. If you understand the security implications of running any command with sudo, and you are absolutely certain you need sudo, use sudo npm i --unsafe-perm (see here for why --unsafe-perm) else installation will fail. If you don't need sudo just use npm i as usual.

The best is to install flood somewhere you have read/write permissions and never use sudo.

My system use python3 as default

If your system use python3 as default you will need to install python2 and use npm i --python="/usr/bin/python2".

Clone this wiki locally