To address all issues (including breaking changes), run:
npm audit fix --force
Run npm audit for details.
npm notice
npm notice New minor version of npm available! 10.5.0 → 10.8.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.1
npm notice Run npm install -g [email protected] to update!
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:18:42] INFO: Starting Node-RED…
start
node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
3 Jun 13:18:45 - [info]
Welcome to Node-RED
3 Jun 13:18:45 - [info] Node-RED version: v3.1.9
3 Jun 13:18:45 - [info] Node.js version: v18.20.2
3 Jun 13:18:45 - [info] Linux 6.6.29-haos x64 LE
3 Jun 13:18:46 - [info] Loading palette nodes
3 Jun 13:18:48 - [info] Node-RED Contrib Theme Collection version: v3.1.11
3 Jun 13:18:51 - [info] Dashboard version 3.6.2 started at /endpoint/ui
3 Jun 13:18:54 - [info] Settings file : /etc/node-red/config.js
3 Jun 13:18:54 - [info] Context store : ‘default’ [module=memory]
3 Jun 13:18:54 - [info] User directory : /config/
3 Jun 13:18:54 - [warn] Projects disabled : editorTheme.projects.enabled=false
3 Jun 13:18:54 - [info] Flows file : /config/flows.json
3 Jun 13:18:54 - [info] Server now running at http://127.0.0.1:46836/
3 Jun 13:18:54 - [warn]
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the ‘credentialSecret’ option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
3 Jun 13:18:54 - [info] Starting flows
[13:18:55] INFO: Starting NGinx…
3 Jun 13:18:56 - [error] [poll-state:f43f15f9510c133a] ConfigError: An entity ID is required
3 Jun 13:18:56 - [info] Started flows
3 Jun 13:18:56 - [info] [udp in:22c79cc691fe61ca] udp listener at 0.0.0.0:999
3 Jun 13:18:56 - [info] [udp in:aa9155c3668ec8e9] udp listener at 0.0.0.0:713
3 Jun 13:18:56 - [info] [udp in:0ad47b05eed46aba] udp listener at 0.0.0.0:808
3 Jun 13:18:56 - [info] [server:Home Assistant] Connecting to http://supervisor/core
3 Jun 13:18:56 - [info] [udp out:8a3076552c117704] udp ready: 10.192.1.15:900
3 Jun 13:18:56 - [info] [udp out:603a09d62b38ddf3] udp re-use socket: → 10.100.105.10:713
3 Jun 13:18:56 - [info] [udp out:7a797c264f6085c9] udp re-use socket: → 10.192.1.15:808
3 Jun 13:18:57 - [info] [mqtt-broker:6ceaf0aea716d579] Connection failed to broker: mqtt://localhost:1883
3 Jun 13:18:57 - [red] Uncaught Exception:
3 Jun 13:18:57 - [error] RangeError: The value of “offset” is out of range. It must be >= 0 and <= 79998. Received 80000
at new NodeError (node:internal/errors:405:5)
at boundsError (node:internal/buffer:88:9)
at checkBounds (node:internal/buffer:57:5)
at checkInt (node:internal/buffer:76:3)
at writeU_Int16BE (node:internal/buffer:834:3)
at Buffer.writeUInt16BE (node:internal/buffer:842:10)
at ModbusServerResponseHandler._handleWriteSingleHoldingRegister (/opt/node_modules/jsmodbus/dist/modbus-server-response-handler.js:183:34)
at ModbusServerResponseHandler.handle (/opt/node_modules/jsmodbus/dist/modbus-server-response-handler.js:42:33)
at ModbusServerClient._onData (/opt/node_modules/jsmodbus/dist/modbus-server-client.js:33:35)
at Socket.emit (node:events:517:28)
[13:18:57] 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:18:57] 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
Seems i made an mistake by configuring Modbus Server. Now i cant start Node Red. Restore from Backup changes nothing. Some one has an idea ?