NodeRed 502: Bad Gateway IP Wechsel

Hallo zusammen,

ich musste meinen Router ohne Backup wegen eines defekt wechseln. Seit dem Wechsel komme ich nicht mehr in NodeRed und bekomme beim Starten den Fehler “502:Bad Gateway” angezeigt.

Mein HASS sowie alle anderen Programme und Geräte habe leider eine neue IP bekommen.

Folgende Sachen wurde bereits getestet.

  • Neustart von HASS
  • Neustart vom kompletten Server
  • Neue Installation von Node Red
  • Altes Backup von vor 2 Monaten auf gespielt

Alles leider ohne Erfolg hat jemand noch ein Idee was ich machen kann?

Folgendes bekomme ich aus dem Protokoll von Node Red.

10 Jun 14:40:37 - [info] node-red-contrib-ccu version: 3.4.2
10 Jun 14:40:39 - [info] Dashboard version 3.5.0 started at /endpoint/ui
10 Jun 14:40:39 - [info] Settings file  : /etc/node-red/config.js
10 Jun 14:40:39 - [info] Context store  : 'default' [module=memory]
10 Jun 14:40:39 - [info] User directory : /config/node-red/
10 Jun 14:40:39 - [warn] Projects disabled : editorTheme.projects.enabled=false
10 Jun 14:40:39 - [info] Flows file     : /config/node-red/flows.json
10 Jun 14:40:39 - [info] Server now running at http://127.0.0.1:46836/
[14:40:39] INFO: Starting NGinx...
10 Jun 14:40:39 - [info] Starting flows
10 Jun 14:40:39 - [error] [ccu-connection:CCU] Local address 192.168.0.71 not available. Using 192.168.0.53 instead.
10 Jun 14:40:40 - [info] [ccu-connection:CCU] paramsets loaded from /config/node-red/paramsets.json
10 Jun 14:40:40 - [info] [ccu-connection:CCU] metadata loaded from /config/node-red/ccu_192.168.0.40.json
10 Jun 14:40:40 - [info] [ccu-connection:CCU] regadata loaded from /config/node-red/ccu_rega_192.168.0.40.json
10 Jun 14:40:40 - [info] [ccu-connection:CCU] values loaded from /config/node-red/ccu_values_192.168.0.40.json
10 Jun 14:40:40 - [info] [hue-bridge:Philips hue] Initializing the bridge (192.168.0.29)…
10 Jun 14:40:40 - [error] [mqtt out:8a47044a46724a31] missing broker configuration
10 Jun 14:40:40 - [info] Started flows
10 Jun 14:40:40 - [warn] [alexa-remote-account:975d4e4eeba46056] ENOENT: no such file or directory, open 'Sicherung'
10 Jun 14:40:40 - [info] [alexa-remote-account:975d4e4eeba46056] intialising with the PROXY method and NO saved data...
10 Jun 14:40:40 - [warn] [alexa-remote-account:975d4e4eeba46056] open 192.168.0.71:3456 in your browser
10 Jun 14:40:40 - [error] [api-current-state:3D Drucker2] InputError:  sensor.shelly_shplg_s_6e7364_current_consumption
10 Jun 14:40:40 - [error] [api-current-state:3D Drucker] InputError:  sensor.shelly_shplg_s_577a47_current_consumption
10 Jun 14:40:40 - [info] [hue-bridge:Philips hue] Error: connect ECONNREFUSED 192.168.0.29:443
10 Jun 14:40:40 - [error] [ccu-connection:CCU] Error: rega getChannels connect ECONNREFUSED 192.168.0.40:8181
10 Jun 14:40:40 - [info] [ccu-connection:CCU] Interfaces: ReGaHSS, BidCos-RF, HmIP-RF
10 Jun 14:40:40 - [info] [ccu-connection:CCU] Interface ReGaHSS connected
10 Jun 14:40:40 - [info] [ccu-connection:CCU] init BidCos-RF http://192.168.0.71:2075 nr_GfzUNy_BidCos-RF
10 Jun 14:40:40 - [info] [ccu-connection:CCU] init HmIP-RF http://192.168.0.71:2075 nr_GfzUNy_HmIP-RF
10 Jun 14:40:40 - [info] [ccu-connection:CCU] xmlrpc server listening on http://192.168.0.71:2075
10 Jun 14:40:40 - [error] [ccu-connection:CCU]     < BidCos-RF init Error: connect ECONNREFUSED 192.168.0.40:2001
10 Jun 14:40:40 - [error] [ccu-connection:CCU] init BidCos-RF Error: connect ECONNREFUSED 192.168.0.40:2001
10 Jun 14:40:40 - [info] [ccu-connection:CCU] Interface BidCos-RF disconnected
10 Jun 14:40:40 - [error] [ccu-connection:CCU]     < HmIP-RF init Error: connect ECONNREFUSED 192.168.0.40:2010
10 Jun 14:40:40 - [error] [ccu-connection:CCU] init HmIP-RF Error: connect ECONNREFUSED 192.168.0.40:2010
10 Jun 14:40:40 - [info] [ccu-connection:CCU] Interface HmIP-RF disconnected
10 Jun 14:40:40 - [info] [ccu-connection:CCU] Interface ReGaHSS disconnected
10 Jun 14:40:40 - [error] [ccu-connection:CCU] getRegaVariables Error: connect ECONNREFUSED 192.168.0.40:8181
10 Jun 14:40:41 - [error] [ccu-connection:CCU] getRegaPrograms Error: connect ECONNREFUSED 192.168.0.40:8181
10 Jun 14:40:41 - [info] [ccu-connection:CCU] regadata saved to /config/node-red/ccu_rega_192.168.0.40.json
10 Jun 14:40:41 - [error] [api-current-state:3D Drucker2] InputError:  sensor.shelly_shplg_s_6e7364_current_consumption
10 Jun 14:40:41 - [error] [api-current-state:3D Drucker] InputError:  sensor.shelly_shplg_s_577a47_current_consumption
10 Jun 14:40:42 - [warn] [miio-roborock-server:Robo] Miio Roborock Error: Could not connect to device, handshake timeout
10 Jun 14:40:42 - [error] [api-current-state:3D Drucker2] InputError:  sensor.shelly_shplg_s_6e7364_current_consumption
10 Jun 14:40:42 - [error] [api-current-state:3D Drucker] InputError:  sensor.shelly_shplg_s_577a47_current_consumption
10 Jun 14:40:43 - [error] [api-current-state:3D Drucker2] InputError:  sensor.shelly_shplg_s_6e7364_current_consumption
10 Jun 14:40:43 - [error] [api-current-state:3D Drucker] InputError:  sensor.shelly_shplg_s_577a47_current_consumption
10 Jun 14:40:43 - [info] [mqtt-broker:386055f0e8a7b678] Connection failed to broker: mqtt://192.168.0.73:1883
10 Jun 14:40:44 - [error] [api-current-state:3D Drucker2] InputError:  sensor.shelly_shplg_s_6e7364_current_consumption
10 Jun 14:40:44 - [error] [api-current-state:3D Drucker] InputError:  sensor.shelly_shplg_s_577a47_current_consumption
10 Jun 14:40:44 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Jun 14:40:45 - [info] [server:Home Assistant] Connected to http://supervisor/core
10 Jun 14:40:45 - [info] [debug:debug 14] 
{ payload: 0, _msgid: '4c1954f1cc4f695f' }
10 Jun 14:40:45 - [info] [debug:debug 13] 
{ payload: 0, _msgid: 'b687186ea0effa1e' }
10 Jun 14:40:46 - [info] [debug:debug 14] 
{ payload: 0, _msgid: 'f3b1643fc47d21e4' }
10 Jun 14:40:46 - [info] [debug:debug 13] 
{ payload: 0, _msgid: '61e76bf845c5aae7' }
10 Jun 14:40:47 - [info] [debug:debug 14] 
{ payload: 0, _msgid: '3ae0784850922fd2' }
10 Jun 14:40:47 - [info] [debug:debug 13] 
{ payload: 0, _msgid: 'a1f2fe8ba4437f34' }
10 Jun 14:40:48 - [info] [debug:debug 14] 
{ payload: 0, _msgid: '7656b2bc076b3032' }
10 Jun 14:40:48 - [info] [debug:debug 13] 
{ payload: 0, _msgid: '1ab258005979bce8' }
10 Jun 14:40:49 - [info] [debug:debug 14] 
{ payload: 0, _msgid: '3642fcef997cdcfa' }
10 Jun 14:40:49 - [info] [debug:debug 13] 
{ payload: 0, _msgid: '12c70cb04fb660cd' }
10 Jun 14:40:50 - [red] Uncaught Exception:
10 Jun 14:40:50 - [error] TypeError: Cannot read properties of undefined (reading 'status')
    at /config/node-red/node_modules/node-red-contrib-huemagic/huemagic/utils/api.js:102:37
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[14:40:50] 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:40:50] 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 nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nginx successfully stopped
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
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Ich würde mich freuen wenn mir wer helfen kann

Wie wäre es, wenn Du Deinem HASS wieder die alte IP zuordnest.
Es empfiehlt sich ohne hin, für derlei Geräte feste IP’s zu setzen.

Das hat leider auch nichts gebracht.

Ich kann Node Red wieder verwenden in dem in die folgende Sachen mache

  • Backup ohne NodeRed auf frische HASS aufspielen
  • NodeRed deinstallieren, Ordner von NodeRed umbenennen und neu Installieren

Hat jemand eine Ahnung wie ich meine Flows wieder herstellen kann oder muss ich nun alles neu schreiben?

Kannst du denn - z.B. per SSL - auf das Dateisystem deines HA-Servers zugreifen? Die Flows sind ja dort im Verzeichnis .node-red gespeichert. Schau dir mal folgenden Link an, der mir schon mal geholfen hat: Beginners Guide to Node-Red Flows

Funktioniert wieder alles Danke zusammen!

hier das vorgehen

  • NodeRed Ordner in nodered.Old umbennen
  • NodeRed neu installieren
  • Flows aus /config/node-red.old/.flows.json.backup in die neue flows.json kopieren
  • NodeRed starten und alle nicht vorhandenen Flows installieren
  • ggf. noch IP-Adressen anpassen

Wenn man weiß wie eigentlich ganz Simple