Node red keeps crashing after adding node

General
1

I added a new websocket node.
after deploy my node red install keep crashing and i cannot start NR
How can i solve this?
The log show this:

26 Oct 18:19:00 - [error] Error: listen EACCES: permission denied 0.0.0.0:80
    at Server.setupListenHandle [as _listen2] (net.js:1314:21)
    at listenInCluster (net.js:1379:12)
    at Server.listen (net.js:1465:7)
    at Server.attach (/home/pi/.node-red/node_modules/socket.io/dist/index.js:173:17)
    at Server.listen (/home/pi/.node-red/node_modules/socket.io/dist/index.js:146:21)
    at new socketIoConfig (/home/pi/.node-red/node_modules/node-red-contrib-socketio/socketio.js:24:10)
    at Object.createNode (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/util.js:87:27)
    at Flow.start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/Flow.js:180:44)
    at start (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/flows/index.js:371:33)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
2

You can start node-red in failsafe mode node-red --safe
Then correct the configuration that leads to listening on port 80.

The process that runs node-red does not have the rights to occupy port 80, given its use among network services.

1 Like
3

It would be great to report this issue against the socketio node - it really needs to be handling this error.

3 Likes
4

Thanks a lot!!

5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.