Error: listen EADDRNOTAVAIL: address not available 1.1.1.1:10502

General
21

I'm also facing this issue:
i am using angular 7
listen EADDRNOTAVAIL: address not available 192.168.7.63:4200 Error: listen EADDRNOTAVAIL: address not available 192.168.7.63:4200 at Server.setupListenHandle [as _listen2] (net.js:1253:19) at listenInCluster (net.js:1318:12) at GetAddrInfoReqWrap.doListen [as callback] (net.js:1451:7) at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:61:10)

please help me to solve this... Thanks

22

Where in node-red are you seeing this? What nodes are you using?

23

I read an tried all above suggestions but unfortunately my node-red server refuse to launch.
The server was running normally and during the warm days the rasphbery pi 4 got overheated.
I bought an proper cooler and raspberry is running normal again but nod-red didn`t want to power up.

At the end I tried to install the latest version using the script from node-red:

bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)

after update the node-red server still didn`t to power up, see log file below:

19 Aug 20:17:00 - [info] Node-RED version: v3.0.2
19 Aug 20:17:00 - [info] Node.js  version: v18.7.0
19 Aug 20:17:00 - [info] Linux 5.10.103-v7l+ arm LE
19 Aug 20:17:01 - [info] Loading palette nodes
19 Aug 20:17:3 - [s7comm-Error] - Installation of Module net-keepalive failed because we might be on the wrong OS. OS=linux
19 Aug 20:17:3 - [s7comm-Info] - Debug configuration for logLevelNodeS7:{"debug":0,"silent":true}
19 Aug 20:17:3 - [s7comm-Info] - Debug configuration for logLevelNodeRED:{"debug":2,"silent":true}
19 Aug 20:17:03 - [info] Dashboard version 3.1.7 started at /ui
19 Aug 20:17:04 - [warn] Missing node modules:
19 Aug 20:17:04 - [warn]  - node-red-node-rbe (0.5.0): rbe
19 Aug 20:17:04 - [warn]  - node-red-node-tail (0.3.1): tail
19 Aug 20:17:04 - [info] Removing modules from config
19 Aug 20:17:04 - [info] Settings file  : /home/pi/.node-red/settings.js
19 Aug 20:17:04 - [info] Context store  : 'default' [module=memory]
19 Aug 20:17:04 - [info] User directory : /home/pi/.node-red
19 Aug 20:17:04 - [warn] Projects disabled : editorTheme.projects.enabled=false
19 Aug 20:17:04 - [warn] Flows file name not set. Generating name using hostname.
19 Aug 20:17:04 - [info] Flows file     : /home/pi/.node-red/flows_raspberrypi.json
19 Aug 20:17:04 - [error] Uncaught Exception:
19 Aug 20:17:04 - [error] Error: listen EADDRNOTAVAIL: address not available 192.168.1.50:1880
    at Server.setupListenHandle [as _listen2] (node:net:1415:21)
    at listenInCluster (node:net:1480:12)
    at doListen (node:net:1629:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)

anybody any idea how to proceed or any suggestions?
how to fix the S7comm error? is there any way to clear the entire node-red, to remove the flows and to installed modules?

24

It looks like you have configured something in your flows to communicate with IP 192.168.1.50 on port 1880. Since node-red is typically configured to run on port 1880, this is your problem.

start node-red using in safe mode

node-red --safe

search your flows for 192.168.1.50 or 1880, change it to something else, deploy.

alternatively, start node-red on a different port number

node-red -p 1881
25

thx for reply, so far as I recall there is nothing that should communicate with ip 192.168.1.50 inside my flow.
I changed the adres because before I had ending 109 and this ip had a conflict with a mobile on my network. So I searched for a free IP on my internal network and modified the node-red server ip inside settings.js to 192.168.1.50. At the moment I have no chance to edit any flow.

The log file shown above was already with node-red --safe mode

Is there any easy way to clean up node-red with the installed modules? I guess there can be a conflict that some modules are not compatible with the new update of node-red.

In the worst case I need to delete everything and reinstall everything again...

26

no, not necessary (I will show you how to make node-red clean without total reinstall)


show me what you changed in settings.js


did you try another port? ...

Also, can you share /home/pi/.node-red/flows_raspberrypi.json

27

If you want to start again with empty flow and no contrib nodes installed then delete (or rename) your .node-red directory and restart node red. It will create a new directory and an empty flows file.

As @Steve-Mcl says, there is no need to re-install.

28

This is not how you change the IP address of your Raspberry Pi.

You need to lookup how to change a Pis ip address (I'm not sure what the current recommended way of doing that is)

The value in settings.js sets which interface of the pi Node-RED will listen on. Undo the change you made to that setting - once you have properly configured the Pi to use the IP address you want, Node-RED will then work with that ip address

29

I changed the adres because before I had ending 109 and this ip had a conflict with a mobile on my network. So I searched for a free IP on my internal network and modified the node-red server ip inside settings.js to 192.168.1.50.

Assuming there are no other services on the Pi using port 1880, it should be possible to access Node-red by it's hostname without reference to it's ip address, for example http://raspberrypi.local:1880 (to do this from a Windows pc it has to have iTunes or Bonjour Print Services installed)

However it looks like you have tried to set a static IP address.
By far the best way to do that is in your router setup, reserve your chosen ip for the Pi's Mac address. Then remove any reference to the ip in settings.js and anywhere else in the Pi and reboot.
Now the Pi will always get the same IP and you can access it at (eg) 192.168.1.50:1880

30

Hello,

This was the issue, I need to modify the pis ip to a static ip and not to change the ip in the settings.js

Server came up again, after importing my backup flows, everything works again.

thank to everybody for your assistance !

1 Like
31

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