I can't open the addon nor any of Automations are working

[Jens-Wymeersch]

Problem/Motivation

Yesterday, I couldn't access the iframe any more, but I was able to see the flows. Today, the automations aren't working any more.

Expected behavior

I expect to be able to work with NR within homeassistant and all automations would be working.

Actual behavior

I now can't open the addon and none of the automations are working.

Steps to reproduce

In the last few days, just an update for the new version of Home Assistant and last week the latest version of Node Red.

logs

2024/10/07 10:55:37 [error] 326#326: *826 upstream prematurely closed connection while reading response header from upstream, client: 172.30.32.2, server: number-nodered, request: "GET /red/images/grip.svg HTTP/1.1", upstream: "http://127.0.0.1:46836/red/images/grip.svg", host: "ha.local:8123"
2024/10/07 10:55:37 [error] 326#326: *828 upstream prematurely closed connection while reading response header from upstream, client: 172.30.32.2, server: number-nodered, request: "GET /plugins?_=1728287736819 HTTP/1.1", upstream: "http://127.0.0.1:46836/plugins?_=1728287736819", host: "ha.local:8123", referrer: "https://ha.local:8123/api/hassio_ingress/1fmqrxR3gs1MccX5vpcRsp7Is5FWfR8B7pp3TbE9QFc/"
2024/10/07 10:55:37 [error] 326#326: *815 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 172.30.32.2, server: number-nodered, request: "GET /red/images/deploy-full-o.svg HTTP/1.1", upstream: "http://127.0.0.1:46836/red/images/deploy-full-o.svg", host: "ha.local:8123", referrer: "https://ha.local:8123/api/hassio_ingress/1fmqrxR3gs1MccX5vpcRsp7Is5FWfR8B7pp3TbE9QFc/"
2024/10/07 10:55:37 [error] 326#326: *814 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 172.30.32.2, server: number-nodered, request: "GET /red/images/spin.svg HTTP/1.1", upstream: "http://127.0.0.1:46836/red/images/spin.svg", host: "ha.local:8123", referrer: "https://ha.local:8123/api/hassio_ingress/1fmqrxR3gs1MccX5vpcRsp7Is5FWfR8B7pp3TbE9QFc/"
2024/10/07 10:55:37 [error] 326#326: *809 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /red/images/deploy-full.svg HTTP/1.1", upstream: "http://127.0.0.1:46836/red/images/deploy-full.svg", host: 
"ha.local:8123", referrer: "https://ha.local:8123/api/hassio_ingress/1fmqrxR3gs1MccX5vpcRsp7Is5FWfR8B7pp3TbE9QFc/"
2024/10/07 10:55:37 [error] 326#326: *830 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: number-nodered, request: "GET /red/images/deploy-flows.svg HTTP/1.1", upstream: "http://127.0.0.1:46836/red/images/deploy-flows.svg", host: "ha.local:8123", referrer: "https://ha.local:8123/api/hassio_ingress/1fmqrxR3gs1MccX5vpcRsp7Is5FWfR8B7pp3TbE9QFc/"
2024/10/07 10:55:37 [error] 326#326: *809 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "ha.local:8123"
2024/10/07 10:55:37 [error] 326#326: *809 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: number-nodered, request: "GET /red/images/deploy-nodes.svg HTTP/1.1", upstream: "http://127.0.0.1:46836/red/images/deploy-nodes.svg", host: "ha.local:8123", referrer: "https://ha.local:8123/api/hassio_ingress/1fmqrxR3gs1MccX5vpcRsp7Is5FWfR8B7pp3TbE9QFc/"
2024/10/07 10:55:37 [error] 326#326: *830 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: number-nodered, request: "GET /red/images/deploy-reload.svg HTTP/1.1", upstream: "http://127.0.0.1:46836/red/images/deploy-reload.svg", host: "ha.local:8123", referrer: "https://ha.local:8123/api/hassio_ingress/1fmqrxR3gs1MccX5vpcRsp7Is5FWfR8B7pp3TbE9QFc/"
[10:55:37] INFO: Service Node-RED exited with code 256 (by signal 9)
2024/10/07 10:55:38 [error] 326#326: *830 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: number-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "ha.local:8123"

[spamsal]

I'm having a similar issue where Node Red seems to not want to start at all. When you go into your addons, is it running at all?

 Add-on version: 18.1.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.1  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.10.1
 Home Assistant Supervisor: 2024.09.1

Here's the logs:

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
fatal error: mallocgc called without a P or outside bootstrapping
runtime: panic before malloc heap initialized
s6-rc: warning: unable to start service init-nginx: command exited 2
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting

up to date, audited 8 packages in 3s

found 0 vulnerabilities
npm notice
npm notice New minor version of npm available! 10.7.0 -> 10.9.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.0
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
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service nodered: stopping
[20:55:47] INFO: Service Node-RED exited with code 256 (by signal 15)

I've looked up this particular line s6-rc failed to properly bring all the services up! and found that turning off SSL seems to fix the issue for some users, but I've had no luck with that. I've also attempted to start it in safe mode, but with the same result.