Node-red no longer starts after changing routers

My old router died yesterday and was replaced today. I’ve gone through an set everything up but the last piece is getting node-red to work again. The only address to HA was 192.168.178.19, it’s now 192.168.1.19. I’ve got HA on a static IP and I’ve gone into my flow.json and changed all the IPs to their new ones but it still fails to start. Here is the log

Welcome to Node-RED
===================

10 Nov 14:00:15 - [info] Node-RED version: v3.1.0
10 Nov 14:00:15 - [info] Node.js  version: v18.18.2
10 Nov 14:00:15 - [info] Linux 6.1.59 x64 LE
10 Nov 14:00:15 - [info] Loading palette nodes
10 Nov 14:00:20 - [info] RedBot version: 1.2.4 (node-red-contrib-chatbot)
10 Nov 14:00:21 - [info] Red Bot Mission Control is not enabled.
10 Nov 14:00:21 - [info]   Enable it running with the REDBOT_ENABLE_MISSION_CONTROL environment variable:
10 Nov 14:00:21 - [info]     REDBOT_ENABLE_MISSION_CONTROL=true node-red -u /my-user-dir

10 Nov 14:00:28 - [info] Dashboard version 3.6.1 started at /endpoint/ui
10 Nov 14:00:29 - [info] Settings file  : /etc/node-red/config.js
10 Nov 14:00:29 - [info] Context store  : 'default' [module=memory]
10 Nov 14:00:29 - [info] User directory : /config/node-red/
10 Nov 14:00:29 - [info] Projects directory: /config/node-red/projects
10 Nov 14:00:29 - [info] Server now running at http://127.0.0.1:46836/
10 Nov 14:00:29 - [info] Active project : HA
10 Nov 14:00:29 - [info] Flows file     : /config/node-red/projects/HA/flows.json
10 Nov 14:00:29 - [info] Starting flows
10 Nov 14:00:29 - [error] [server:2f1g8h7i.654321] Error: No credentials provided
10 Nov 14:00:29 - [error] [server:63517380.eb951c] Error: No credentials provided
Tesla API: No token found. Getting new token now...
Tesla API: doing api call to fetch new access token
[14:00:29] INFO: Starting NGinx...
10 Nov 14:00:30 - [info] Started flows
10 Nov 14:00:30 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:30 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:30 - [error] [api-call-service:on] Call-Service attempted without connection to server.
10 Nov 14:00:30 - [error] [api-call-service:quiet time off] Call-Service attempted without connection to server.
Tesla API: access token OK
10 Nov 14:00:34 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:34 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:34 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:34 - [error] [api-current-state:Season] InputError: Entity could not be found in cache for entityId: sensor.season
10 Nov 14:00:34 - [error] [api-current-state:Nest] InputError: Entity could not be found in cache for entityId: climate.hallway_2
10 Nov 14:00:35 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:35 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:39 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:39 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:39 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:39 - [error] [api-current-state:Jeremy] InputError: Entity could not be found in cache for entityId: binary_sensor.jeremy_presence
10 Nov 14:00:39 - [error] [api-current-state:Deanna] InputError: Entity could not be found in cache for entityId: binary_sensor.deanna_presence
10 Nov 14:00:40 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:40 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:44 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Nov 14:00:44 - [red] Uncaught Exception:
10 Nov 14:00:44 - [error] Error: Huejay: timeout of 15000ms exceeded
    at /config/node-red/node_modules/huejay/lib/Transport.js:106:15
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at listOnTimeout (node:internal/timers:538:9)
    at processTimers (node:internal/timers:512:7)
[14:00:44] INFO: Service Node-RED exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[14:00:44] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
1 Like

Same problem. I changed the IP of my hue bridge and now node-red is n a boot loop. Did you manage to solve it?

Go to the addon page, configuration tab. Turn on safe mode, save and restart. It should start up and then modify or delete the hue server nodes.