It seems you can't have node-red running on the same IP as a chrome instance? This kinda stuffs it for me, as I want my node-red to listen as a different device, but on the same desktop box that chrome runs on.
Just checking that this is a known limitation before I give up (and also the encryption problem is there, but this is stopping me as well).
22 Jul 01:28:10 - [info] [join-server:4c69f98f.18ef38] Starting server on port 1820...
..
22 Jul 01:28:10 - [info] [join-server:4c69f98f.18ef38] Not registering device because IPs are the same.
That's a normal, expected message. It just means that the Node-RED device was already registered with the same IP so no need to send the registration again to the server. :)
Hey there,
It seems you can't have node-red running on the same IP as a chrome instance? This kinda stuffs it for me, as I want my node-red to listen as a different device, but on the same desktop box that chrome runs on.
Just checking that this is a known limitation before I give up (and also the encryption problem is there, but this is stopping me as well).