Node-red will not start after NPM installation

#1

Hi.

I have installed a NPM - node-red-contrib-sonoff-server.

After that it all crashed. When I start up it now just stops as listed below.

**
pi@raspberrypi:~ $ node-red
10 Feb 01:20:06 - [info]

Welcome to Node-RED

10 Feb 01:20:06 - [info] Node-RED version: v0.19.5
10 Feb 01:20:06 - [info] Node.js version: v10.15.1
10 Feb 01:20:06 - [info] Linux 4.14.97-v7+ arm LE
10 Feb 01:20:09 - [info] Loading palette nodes
10 Feb 01:20:25 - [info] Dashboard version 2.13.2 started at /ui
10 Feb 01:20:27 - [info] Settings file : /home/pi/.node-red/settings.js
10 Feb 01:20:27 - [info] Context store : 'default' [module=memory]
10 Feb 01:20:27 - [info] User directory : /home/pi/.node-red
10 Feb 01:20:27 - [warn] Projects disabled : editorTheme.projects.enabled=false
10 Feb 01:20:27 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.j son
10 Feb 01:20:27 - [warn]


Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

10 Feb 01:20:27 - [info] Starting flows
10 Feb 01:20:27 - [info] [knx-controller:knx] connecting to knxjs server at 100. 0.0.160:3671 in mode[tunnel/unicast]
10 Feb 01:20:27 - [info] [knx-controller:knx] already connected to knxjs server at 100.0.0.160:3671 in mode[tunnel/unicast]
10 Feb 01:20:27 - [info] [knx-controller:knx] already connected to knxjs server at 100.0.0.160:3671 in mode[tunnel/unicast]
10 Feb 01:20:27 - [info] [knx-controller:knx] already connected to knxjs server at 100.0.0.160:3671 in mode[tunnel/unicast]
10 Feb 01:20:28 - [info] Started flows
10 Feb 01:20:28 - [info] [sonoff-server:910b980e.0b69d8] SONOFF Server Started O n Port 1080
10 Feb 01:20:28 - [red] Uncaught Exception:
10 Feb 01:20:28 - Error: listen EACCES: permission denied 0.0.0.0:443
at Server.setupListenHandle [as _listen2] (net.js:1260:19)
at listenInCluster (net.js:1325:12)
at Server.listen (net.js:1412:7)
at Server.listen (/home/pi/.node-red/node_modules/nodejs-websocket/Server.js :119:14)
at Object.module.exports.createServer (/home/pi/.node-red/node_modules/simpl e-sonoff-server/sonoff.server.module.js:263:8)
at new SonoffServer (/home/pi/.node-red/node_modules/node-red-contrib-sonoff -server/config-server/config-server.js:33:61)
at createNode (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/Flow.j s:305:18)
at Flow.start (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/Flow.j s:67:31)
at start (/usr/lib/node_modules/node-red/red/runtime/nodes/flows/index.js:32 8:29)
at tryCatchReject (/usr/lib/node_modules/node-red/node_modules/when/lib/make Promise.js:845:30)
at runContinuation1 (/usr/lib/node_modules/node-red/node_modules/when/lib/ma kePromise.js:804:4)
at Fulfilled.when (/usr/lib/node_modules/node-red/node_modules/when/lib/make Promise.js:592:4)
at Pending.run (/usr/lib/node_modules/node-red/node_modules/when/lib/makePro mise.js:483:13)
at Scheduler._drain (/usr/lib/node_modules/node-red/node_modules/when/lib/Sc heduler.js:62:19)
at Scheduler.drain (/usr/lib/node_modules/node-red/node_modules/when/lib/Sch eduler.js:27:9)
at process._tickCallback (internal/process/next_tick.js:61:11)
pi@raspberrypi:~ $
**

0 Likes

#2

This is an error that the node hasn't caught. It is trying to start on port 443 - this requires root access generally (any port below 1024 requires elevated rights). I don't know that node, I would guess that you've missed some prerequisite for its installation or configuration.

0 Likes

#3

As @TotallyInformation says it is an error that the node hasn’t caught that the author need to fix. You can open an issue with the author by following the link to the idea github page from the nodes page on flows.nodered.org.

If you want to get Node-RED working againInwould suggest deleting the node with you can do using the npm delete command from the same directory you installed it from

0 Likes

#4

Hi.
Change Websocket port in node from 443 to 1443.
sonoff.config.json

0 Likes