Node Red Keep Crashing, can't resolve error

Hi !

For a long time my nodered extension from HomeAssistant OS was working well, but since 2 week, each 2 or 3 days, it crash.

Here is the log, i am not sure if the error connect is the source of the problem, but this error appear so often in the log, i prefer start my analyse by correct it.

But i have no idea witch node is the problem, i have nothing configured on "0.0.0.0", port 8009 is for google home, but all my google home config had an IP ( 192.168.x.x).

How can i find this faulty node ?

Any help would be greatly appreciated !!! Thanks !

s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: Node-RED
 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 Add-on version: 13.3.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 8.5  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2022.8.7
 Home Assistant Supervisor: 2022.08.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/customizations.sh
cont-init: info: /etc/cont-init.d/customizations.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/node-red.sh
patching file nodes/ui_base.html
Hunk #1 succeeded at 1164 (offset 633 lines).
up to date, audited 836 packages in 24s
33 packages are looking for funding
  run `npm fund` for details
34 vulnerabilities (1 low, 12 moderate, 14 high, 7 critical)
To address issues that do not require attention, run:
  npm audit fix
To address all issues possible (including breaking changes), run:
  npm audit fix --force
Some issues need review, and may require choosing
a different dependency.
Run `npm audit` for details.
cont-init: info: /etc/cont-init.d/node-red.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun nodered (no readiness notification)
s6-rc: info: service legacy-services successfully started
[14:42:08] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
28 Aug 14:42:13 - [info] 
Welcome to Node-RED
===================
28 Aug 14:42:13 - [info] Node-RED version: v3.0.2
28 Aug 14:42:13 - [info] Node.js  version: v16.16.0
28 Aug 14:42:13 - [info] Linux 5.15.32-v8 arm64 LE
28 Aug 14:42:15 - [info] Loading palette nodes
28 Aug 14:42:25 - [info] Dashboard version 3.1.7 started at /endpoint/ui
28 Aug 14:42:26 - [warn] Missing node modules:
28 Aug 14:42:26 - [warn]  - node-red-contrib-bool-gate (1.0.2): and-gate, or-gate
28 Aug 14:42:26 - [info] Removing modules from config
28 Aug 14:42:26 - [info] Settings file  : /etc/node-red/config.js
28 Aug 14:42:26 - [info] Context store  : 'default' [module=memory]
28 Aug 14:42:26 - [info] User directory : /config/node-red/
28 Aug 14:42:26 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 Aug 14:42:26 - [info] Flows file     : /config/node-red/flows.json
28 Aug 14:42:26 - [info] Server now running at http://127.0.0.1:46836/
[14:42:27] INFO: Starting NGinx...
28 Aug 14:42:27 - [info] Starting flows
fileServer listening on ip 192.168.0.10 and port 8098
[...]
28 Aug 14:42:32 - [info] Started flows
28 Aug 14:42:32 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Aug 14:42:32 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Aug 14:42:32 - [info] [server:Home Assistant] Connecting to http://supervisor/core
Error: connect ECONNREFUSED 0.0.0.0:8009
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '0.0.0.0',
  port: 8009
}
28 Aug 14:42:34 - [info] [mqtt-broker:e1e0379ecc3b14df] Connected to broker: mqtt://core-mosquitto:1883
28 Aug 14:42:34 - [info] [server:Home Assistant] Connected to http://supervisor/core
28 Aug 14:42:34 - [info] [server:Home Assistant] Connected to http://supervisor/core
28 Aug 14:42:34 - [info] [server:Home Assistant] Connected to http://supervisor/core

Hi @pinkfloydFR,
I think it is better if you ask this on the HomeAssistant forum. Looks to me something with the nodes that have been developed to integrate Node-RED into HomeAssistant.
Good luck!
Bart