Node-Red Companion does not start after upgrade

Third party integrations Node-RED
1

Hi Everyone,

I’ve been using the Node-Red integration for years, and yesterday I updated it along with HA. Since then, it hasn’t started and is showing the following error. I’m not sure if the problem is caused directly by the latest upgrade, since the full backup taken before the upgrade also fails with the same error. What is causing the error? How can I fix this?

Thank you in advance for your help!

Gabor

===========================================================
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

App: Node-RED

Flow-based programming for the Internet of Things

App version: 21.0.5

You are running the latest version of this app.

System: Home Assistant OS 17.1 (amd64 / qemux86-64)

Home Assistant Core: 2026.4.0

Home Assistant Supervisor: 2026.03.2

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

[09:38:17] INFO: Starting installation of custom NPM/Node-RED packages…

s6-rc: info: service init-nginx successfully started

npm warn config optional Use --omit=optional to exclude optional dependencies, or

npm warn config --include=optional to include them.

npm warn config

npm warn config Default value does install optional deps unless otherwise omitted.

npm warn config only Use --omit=dev to omit dev dependencies from the install.

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_ENTRY_INVALID checksum failure

npm warn tar TAR_BAD_ARCHIVE: Unrecognized archive format

npm error code TAR_BAD_ARCHIVE

npm error TAR_BAD_ARCHIVE: Unrecognized archive format

npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-04T07_38_17_597Z-debug-0.log

[09:38:50] FATAL: Failed to install a specified npm package

s6-rc: warning: unable to start service init-customizations: command exited 1

/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 init-nginx: stopping

s6-rc: info: service init-nginx 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: warning: service s6rc-oneshot-runner is marked as essential, not stopping it

2

Is your docker/vm version outdated? There were associated issues with updates being compressed with a newer format that existing software couldn’t expand, hence missing files and update failure in last months releases too.

3

My apologies, I’m new to this forum and new to HA… I’m having the same issue with Node-Red. I’m currently running HA Core 2026.4.1, Supervisor 2026.03.2, OS 17.1 and Frontend 20260325.6. My Node-Red version showing in HA Apps is 21.0.3. System is persistently attempting to load 21.0.5 but each time shuts down Node-Red and unable to restart it. I’ve been restoring auto backup of 21.0.3 to continue operations. I’m new to HA so not quite sure if I’m running docker/vm. Appreciate any help. Thanks!

4

What is HA installed on?

5

Hi, similar problem when updating from 21.0.4 to 21.0.5 this morning. node-red is in endless startup following the update. restoring to 21.0.4 backup (only) did not resolve it. Rebooted entire machine (pi 4) which did not resolve (same symptoms). Restored full nightly backup (containing node red 21.0.4) with same issue and symptoms. restored app only backup of node-red 21.0.3, 21.0.2 and even 20.x.x with the same symptoms. After doing some research I learned that the musl package was updated overnight which broken some dependencies for the g++ system package which is necesary for building several node-red nodes: google home, invert node, ultimate timer. Adding system package ‘musl’ in the app’s configuration section of node-red resolved the issue. It’s bit scary that restoring from back-up doesn’t resolve this type of problem because the system is pulling from the alpine repository for the docker container. That docker container respository dependency was not understood by me:

 App version: 21.0.5
 You are running the latest version of this app.
 System: Home Assistant OS 17.1  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2026.3.4
 Home Assistant Supervisor: 2026.03.3
-----------------------------------------------------------
 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-nginx successfully started
v3.23.3-510-g6ab84063339 [https://dl-cdn.alpinelinux.org/alpine/v3.23/main]
v3.23.3-510-g6ab84063339 [https://dl-cdn.alpinelinux.org/alpine/v3.23/community]
OK: 27443 distinct packages available
( 1/10) Installing libbz2 (1.0.8-r6)
( 2/10) Installing libffi (3.5.2-r0)
( 3/10) Installing gdbm (1.26-r0)
( 4/10) Installing xz-libs (5.8.2-r0)
( 5/10) Installing mpdecimal (4.0.1-r0)
( 6/10) Installing libpanelw (6.5_p20251123-r0)
( 7/10) Installing python3 (3.12.13-r0)
( 8/10) Installing python3-pycache-pyc0 (3.12.13-r0)
( 9/10) Installing pyc (3.12.13-r0)
(10/10) Installing python3-pyc (3.12.13-r0)
Executing busybox-1.37.0-r30.trigger
OK: 165.2 MiB in 64 packages
(1/1) Installing make (4.4.1-r3)
Executing busybox-1.37.0-r30.trigger
OK: 165.5 MiB in 65 packages
(1/9) Installing jansson (2.14.1-r0)
(2/9) Installing binutils (2.45.1-r0)
(3/9) Installing libgomp (15.2.0-r2)
(4/9) Installing libatomic (15.2.0-r2)
(5/9) Installing gmp (6.3.0-r4)
(6/9) Installing isl26 (0.26-r1)
(7/9) Installing mpfr4 (4.2.2-r0)
(8/9) Installing mpc1 (1.3.1-r1)
(9/9) Installing gcc (15.2.0-r2)
Executing busybox-1.37.0-r30.trigger
OK: 316.7 MiB in 74 packages
ERROR: unable to select packages:
  musl-1.2.5-r21:
    breaks: musl-dev-1.2.5-r23[musl=1.2.5-r23]
    satisfies: world[musl=1.2.5-r21]
               ada-libs-3.3.0-r0[so:libc.musl-aarch64.so.1]
               apk-tools-3.0.3-r1[musl>=1.2.3_git20230424]
               apk-tools-3.0.3-r1[so:libc.musl-aarch64.so.1]
               bash-5.3.3-r1[so:libc.musl-aarch64.so.1]
               binutils-2.45.1-r0[so:libc.musl-aarch64.so.1]
               brotli-libs-1.2.0-r0[so:libc.musl-aarch64.so.1]
               busybox-1.37.0-r30[so:libc.musl-aarch64.so.1]
               c-ares-1.34.6-r0[so:libc.musl-aarch64.so.1]
               ca-certificates-20251003-r0[so:libc.musl-aarch64.so.1]
               curl-8.17.0-r1[so:libc.musl-aarch64.so.1]
               g++-15.2.0-r2[so:libc.musl-aarch64.so.1]
               gcc-15.2.0-r2[so:libc.musl-aarch64.so.1]
               gdbm-1.26-r0[so:libc.musl-aarch64.so.1]
               git-2.52.0-r0[so:libc.musl-aarch64.so.1]
               gmp-6.3.0-r4[so:libc.musl-aarch64.so.1]
               icu-libs-76.1-r1[so:libc.musl-aarch64.so.1]
               isl26-0.26-r1[so:libc.musl-aarch64.so.1]
               jansson-2.14.1-r0[so:libc.musl-aarch64.so.1]
               jq-1.8.1-r0[so:libc.musl-aarch64.so.1]
               libapk-3.0.3-r1[so:libc.musl-aarch64.so.1]
               libatomic-15.2.0-r2[so:libc.musl-aarch64.so.1]
               libbz2-1.0.8-r6[so:libc.musl-aarch64.so.1]
               libcrypto3-3.5.5-r0[so:libc.musl-aarch64.so.1]
               libcurl-8.17.0-r1[so:libc.musl-aarch64.so.1]
               libedit-20251016.3.1-r0[so:libc.musl-aarch64.so.1]
               libexpat-2.7.5-r0[so:libc.musl-aarch64.so.1]
               libffi-3.5.2-r0[so:libc.musl-aarch64.so.1]
               libgcc-15.2.0-r2[so:libc.musl-aarch64.so.1]
               libgomp-15.2.0-r2[so:libc.musl-aarch64.so.1]
               libidn2-2.3.8-r0[so:libc.musl-aarch64.so.1]
               libncursesw-6.5_p20251123-r0[so:libc.musl-aarch64.so.1]
               libpanelw-6.5_p20251123-r0[so:libc.musl-aarch64.so.1]
               libpsl-0.21.5-r3[so:libc.musl-aarch64.so.1]
               libssl3-3.5.5-r0[so:libc.musl-aarch64.so.1]
               libstdc++-15.2.0-r2[so:libc.musl-aarch64.so.1]
               libunistring-1.4.1-r0[so:libc.musl-aarch64.so.1]
               make-4.4.1-r3[so:libc.musl-aarch64.so.1]
               mpc1-1.3.1-r1[so:libc.musl-aarch64.so.1]
               mpdecimal-4.0.1-r0[so:libc.musl-aarch64.so.1]
               mpfr4-4.2.2-r0[so:libc.musl-aarch64.so.1]
               musl-utils-1.2.5-r21[so:libc.musl-aarch64.so.1]
               nghttp2-libs-1.68.0-r0[so:libc.musl-aarch64.so.1]
               nghttp3-1.13.1-r0[so:libc.musl-aarch64.so.1]
               nginx-1.28.3-r0[so:libc.musl-aarch64.so.1]
               nodejs-24.14.1-r0[so:libc.musl-aarch64.so.1]
               oniguruma-6.9.10-r0[so:libc.musl-aarch64.so.1]
               openssh-client-common-10.2_p1-r0[so:libc.musl-aarch64.so.1]
               openssh-client-default-10.2_p1-r0[so:libc.musl-aarch64.so.1]
               openssh-keygen-10.2_p1-r0[so:libc.musl-aarch64.so.1]
               patch-2.8-r0[so:libc.musl-aarch64.so.1]
               pcre2-10.47-r0[so:libc.musl-aarch64.so.1]
               python3-3.12.13-r0[so:libc.musl-aarch64.so.1]
               readline-8.3.1-r0[so:libc.musl-aarch64.so.1]
               scanelf-1.3.8-r2[so:libc.musl-aarch64.so.1]
               simdjson-3.12.0-r0[so:libc.musl-aarch64.so.1]
               simdutf-7.5.0-r1[so:libc.musl-aarch64.so.1]
               sqlite-libs-3.51.2-r0[so:libc.musl-aarch64.so.1]
               ssl_client-1.37.0-r30[so:libc.musl-aarch64.so.1]
               xz-libs-5.8.2-r0[so:libc.musl-aarch64.so.1]
               zlib-1.3.1-r2[so:libc.musl-aarch64.so.1]
               zstd-libs-1.5.7-r2[so:libc.musl-aarch64.so.1]
[09:43:31] FATAL: Failed installing system package g++
s6-rc: warning: unable to start service init-customizations: command exited 1
/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.```
6

I’m also having the same issue, Node-Red is stuck in a startup loop after the latest Hass OS and Node red updates.

OS version: 2026.4.2
Node Red: 21.0.5
This is installed on a mini PC.

Node Red log:

 App: Node-RED
 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 App version: 21.0.5
 You are running the latest version of this app.
 System: Home Assistant OS 17.2  (amd64 / generic-x86-64)
 Home Assistant Core: 2026.4.2
 Home Assistant Supervisor: 2026.04.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
[09:42:39] INFO: Starting installation of custom NPM/Node-RED packages...
s6-rc: info: service init-nginx successfully started
npm warn config optional Use `--omit=optional` to exclude optional dependencies, or
npm warn config `--include=optional` to include them.
npm warn config
npm warn config       Default value does install optional deps unless otherwise omitted.
npm warn config only Use `--omit=dev` to omit dev dependencies from the install.
npm error code ETARGET
npm error notarget No matching version found for undefined@-.
npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-15T15_42_39_143Z-debug-0.log
[09:42:39] FATAL: Failed to install a specified npm package
s6-rc: warning: unable to start service init-customizations: command exited 1
/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 init-nginx: stopping
s6-rc: info: service init-nginx 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: warning: service s6rc-oneshot-runner is marked as essential, not stopping it
7

If you start in safe mode, will NR start? On the configuration tab switch on safe mode and restart.

8

Just tried starting it in safe mode with a couple HASS restarts and still no joy, I’m getting the same errors.