Raspberry Pi opens Node-red with an error


I tried to use open Node-red, but it failed。What should I do to solve this problem?

root@RevPi64360:/home/pi# node-red-start

Start Node-RED
Once Node-RED has started, point a browser at
On Pi Node-RED works better with the Firefox or Chrome browser
Use   sudo systemctl enable nodered.service  to autostart Node-RED at every boot
Use   sudo systemctl disable nodered.service to disable autostart on boot
To find more nodes and example flows - go to http://flows.nodered.org
Starting as root systemd service.
27 Apr 05:37:56 - [info]
Welcome to Node-RED
27 Apr 05:37:56 - [info] Node-RED version: v1.3.5
27 Apr 05:37:56 - [info] Node.js  version: v14.17.1
27 Apr 05:37:56 - [info] Linux 4.19.95-rt38-v7 arm LE
27 Apr 05:37:57 - [info] Loading palette nodes
27 Apr 05:38:01 - [info] Settings file  : /home/pi/.node-red/settings.js
27 Apr 05:38:01 - [info] Context store  : 'default' [module=memory]
27 Apr 05:38:01 - [info] User directory : /home/pi/.node-red
27 Apr 05:38:01 - [warn] Projects disabled : editorTheme.projects.enabled=false
27 Apr 05:38:01 - [info] Flows file     : /home/pi/.node-red/flows_RevPi64360.json
27 Apr 05:38:01 - [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.
27 Apr 05:38:01 - [info] Server now running at
27 Apr 05:38:01 - [info] Starting flows
Connecting to WS Server wss://localhost:8000
27 Apr 05:38:02 - [info] Started flows
27 Apr 05:38:02 - [red] Uncaught Exception:
27 Apr 05:38:02 - Error: listen EADDRNOTAVAIL: address not available
    at Server.setupListenHandle [as _listen2] (net.js:1303:21)
    at listenInCluster (net.js:1368:12)
    at doListen (net.js:1505:7)
    at processTicksAndRejections (internal/process/task_queues.js:83:21)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.

Is this first time loading Node red , did you sudo reboot after installing if this is a fresh install?

Search your flows for (use CTRL+F)

Find the node or config node with that value.

What is it?

It is likely whatever node is using this address is not handling situations where the IP is unavailable. If you can identify the node, you can find its repository and report the issue.

To start node-red regardless of this error, use the --safe argument to start up e.g. node-red --safe instead of node-red-start

1 Like

I used it all day yesterday, but it had a problem before I left work.

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