Nod-red don´t start, probably after auto update to 17.0.13

About two weeks ago, when on holiday, Nod-red stopped working. Probably after auto update. I did not change anything else.

Hass runs on a Pi4, as you can see in the log.
What can be the reason and who can I repair it without data loss? I have a backup before the issue.

Log below

Regads
Geert

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
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Node-RED
Flow-based programming for the Internet of Things

Add-on version: 17.0.13
You are running the latest version of this add-on.
System: Home Assistant OS 12.3 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2024.6.3
Home Assistant Supervisor: 2024.06.0

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started

up to date, audited 8 packages in 2s

found 0 vulnerabilities
npm notice
npm notice New minor version of npm available! 10.7.0 → 10.8.1
npm notice Changelog: Release v10.8.1 · npm/cli · GitHub
npm notice To update run: npm install -g [email protected]
npm notice
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[13:01:15] INFO: Starting Node-RED…

start
node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

17 Jun 13:01:17 - [info]

Welcome to Node-RED

17 Jun 13:01:17 - [info] Node-RED version: v3.1.9
17 Jun 13:01:17 - [info] Node.js version: v18.20.3
17 Jun 13:01:17 - [info] Linux 6.6.28-haos-raspi arm64 LE
17 Jun 13:01:18 - [info] Loading palette nodes
17 Jun 13:01:18 - [info] Node-RED Contrib Theme Collection version: v3.1.11
17 Jun 13:01:22 - [info] Dashboard version 3.6.5 started at /endpoint/ui
17 Jun 13:01:23 - [info] Settings file : /etc/node-red/config.js
17 Jun 13:01:23 - [info] Context store : ‘default’ [module=memory]
17 Jun 13:01:24 - [info] User directory : /config/
17 Jun 13:01:24 - [warn] Projects disabled : editorTheme.projects.enabled=false
17 Jun 13:01:24 - [info] Flows file : /config/flows.json
17 Jun 13:01:24 - [info] Server now running at http://127.0.0.1:46836/
[13:01:24] INFO: Starting NGinx…
17 Jun 13:01:24 - [info] Starting flows
17 Jun 13:01:24 - [info] Started flows
17 Jun 13:01:25 - [red] Uncaught Exception:
17 Jun 13:01:25 - [error] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason “#”.
[13:01:25] 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
[13:01:25] 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

After updating to version 18 last night, my node red does not start. Tried a full reboot and manually starting the addon, however nothing works. I reverted back to the last 17 version and it now works again