Node Red startet nicht

Hallo, ich habe mir heute das node-red-contrib-whatsapp-link installiert, habe dann den Admin konfiguriert und dann war plötzlich NR nicht mehr erreichbar.

Hier mein Start log.

[11:01:48] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
14 Apr 11:01:49 - [info] 
Welcome to Node-RED
===================
14 Apr 11:01:49 - [info] Node-RED version: v4.0.9
14 Apr 11:01:49 - [info] Node.js  version: v22.13.1
14 Apr 11:01:49 - [info] Linux 6.6.66-haos x64 LE
14 Apr 11:01:49 - [info] Loading palette nodes
14 Apr 11:01:50 - [info] Node-RED Contrib Theme Collection version: v4.0.11
14 Apr 11:01:53 - [info] Dashboard version 3.4.0 started at /endpoint/ui
(node:311) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
14 Apr 11:01:54 - [info] node-red-contrib-home-assistant-websocket v0.74.2 nodes initialized
14 Apr 11:01:54 - [info] Settings file  : /etc/node-red/config.js
14 Apr 11:01:54 - [info] Context store  : 'default' [module=localfilesystem]
14 Apr 11:01:54 - [info] User directory : /config/
14 Apr 11:01:54 - [warn] Projects disabled : editorTheme.projects.enabled=false
14 Apr 11:01:54 - [info] Flows file     : /config/flows.json
14 Apr 11:01:54 - [info] Server now running at http://127.0.0.1:46836/
[11:01:55] INFO: Starting NGinx...
14 Apr 11:01:56 - [info] Starting flows
14 Apr 11:01:56 - [info] KNX-Unsecure: connection to insecure interface/router using node MDT KNX IP Interface 
14 Apr 11:01:56 - [info] [whatsappLink:Web] Status : Initializing Whatsapp..
14 Apr 11:01:57 - [info] [cronplus:d108c78ea917c815] createTask - index: 0, static: true, opt: {"name":"schedule1","topic":"Monatsende","payloadType":"jsonata","payload":"\"Ende Monat: \" & $moment().locale(\"de\").tz('Europe/Berlin').format('MMMM YYYY')","expressionType":"cron","expression":"0 0 0 L * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"}
14 Apr 11:01:57 - [error] [api-call-service:5e485ff7.db156] Error: Invalid server config
14 Apr 11:01:57 - [error] [api-call-service:9c978d1c.ee76] Error: Invalid server config
14 Apr 11:01:57 - [error] [function:function 5] SyntaxError: Unexpected token '=' (body:line 4)
14 Apr 11:01:58 - [info] Started flows
14 Apr 11:01:58 - [red] Uncaught Exception:
14 Apr 11:01:58 - [error] Error: Failed to launch the browser process! spawn /config/node_modules/puppeteer-core/.local-chromium/linux-1045629/chrome-linux/chrome ENOENT
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
    at onClose (/config/node_modules/puppeteer-core/src/node/BrowserRunner.ts:327:9)
    at ChildProcess.<anonymous> (/config/node_modules/puppeteer-core/src/node/BrowserRunner.ts:319:16)
    at ChildProcess.emit (node:events:524:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
    at onErrorNT (node:internal/child_process:483:16)
    at processTicksAndRejections (node:internal/process/task_queues:90:21)
[11:01:58] 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
[11:01:58] 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
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

Leider hab ich nur ein relativ altes Backup meiner Flows, kennt jemand eine Möglichkeit das NR wieder startet? Oder ich die Flows ohne das NR läuft sichern kann?

Lg

Hast du mal den “Safe”-Mode versucht?
Die Zeile sollte dir helfen deine Flows zu finden:
14 Apr 11:01:54 - [info] Flows file : /config/flows.json