Node-RED icon

Node-RED on a Win10 machine may cause port conflicts with Hyper-V

I’ve installed Node-RED on my Win10 machine.
Although the installation process went straight and without any failures, the software refused to start properly.

The error message was like this:

[error] Uncaught Exception:
[error] Error: listen EACCES 0.0.0.0:1880
at Server.setupListenHandle as _listen2
at listenInCluster (net.js:1401:12)
at doListen (net.js:1510:7)
at _combinedTickCallback (internal/process/next_tick.js:142:11)
at process._tickCallback (internal/process/next_tick.js:181:9)


I did a little research and found some hints about problems with Node-RED and Hyper-V running on the same machine:
https://stackoverflow.com/questions/59264538/listening-to-port-1880-fails-on-windows

Obviously, Hyper-V in some cases blocks port 1880, which is the standard port for Node-RED.

You can check for blocked ports with the following cmd line:
netsh int ip show excludedportrange protocol=tcp


The output should look something like this:
Startport Endport
---------- --------
1131 1230
1231 1330
1331 1430
1431 1530
1735 1834
1835 1934

In my case 1880 was within the blocked range, so I had to change the port settings on which Node-RED is listening in the following file:
%userprofile%.node-red\settings.js


Changing the port from 1880 to 18800 worked well.


Leave a Comment

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert