Node-RED fails to start after updating Tahoma

[wytsep]

Describe the bug and reproduction Yesterday I updated the Tahoma box and after that my whole Node-RED instance doesn't want to start anymore. In the logs I see the following message:

node-red_1 | 9 Apr 20:56:00 - [error] Error: connect EHOSTUNREACH 192.168.178.30:8443 node-red_1 | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)

Before the update. Everything worked perfect!

I've tried to remove the configuration node from the flows.json, and after that Node-RED can start normally. Then I tried to reconnect by completing the setup, but then it fails again.

The setup cannot find the ip address so I'm inserting that manually. I've checked the IP-address and that is still correct. Did the port change? How can I check that?

Expected behavior First that Node-Red doesn't crash when the plugin cannot get a connection. Second that the plugin can connect to the box.

Logs node-red_1 | 9 Apr 20:56:00 - [error] Error: connect EHOSTUNREACH 192.168.178.30:8443 node-red_1 | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)

Setup:

• Version of node-red: 3.0.2
• Version of node-red-contrib-tahoma: 3.0.0-beta.5
• Version of node (node -v): v16.16.0
• Version of npm (npm -v): 8.11.0
• Where is node-red installed (Raspberry, macOS...)? Raspberry pi
• How is node-red installed (Docker, via npm)? Docker

[wytsep]

Alright, by using the mdns command manually (discovery doesn't work in docker image) I found out that the ip-address did change. It is now working for me, but it's not really desirable that the whole Node-RED instance crashes if no connection can be made...