Considering all of my automations are built in NodeRED, this is extremely inconvenient. This is what I see in the NodeRED add-on log. This just keeps going, over and over again, resulting in a 503 Bad Gateway message in the UI. I have no idea what to do. I’ve already uninstalled and re-installed it.
Welcome to Node-RED
17 Jun 11:27:57 - [info] Node-RED version: v3.0.2
17 Jun 11:27:57 - [info] Node.js version: v18.16.0
17 Jun 11:27:57 - [info] Linux 6.1.29 x64 LE
17 Jun 11:27:58 - [info] Loading palette nodes
[11:28:07] INFO: Service Node-RED exited with code 256 (by signal 9)
[11:28:08] INFO: Setting safe mode startup
[11:28:08] INFO: Starting Node-RED…
start
node $NODE_OPTIONS node_modules/node-red/red.js --safe --settings /etc/node-red/config.js
17 Jun 11:28:12 - [info]
Welcome to Node-RED
===================
17 Jun 11:28:12 - [info] Node-RED version: v3.0.2
17 Jun 11:28:12 - [info] Node.js version: v18.16.0
17 Jun 11:28:12 - [info] Linux 6.1.29 x64 LE
17 Jun 11:28:16 - [info] Loading palette nodes
[11:28:25] INFO: Service Node-RED exited with code 256 (by signal 9)
[11:28:26] INFO: Setting safe mode startup
[11:28:26] INFO: Starting Node-RED…
start
node $NODE_OPTIONS node_modules/node-red/red.js --safe --settings /etc/node-red/config.js
17 Jun 11:28:30 - [info]
Welcome to Node-RED
===================
17 Jun 11:28:30 - [info] Node-RED version: v3.0.2
17 Jun 11:28:30 - [info] Node.js version: v18.16.0
17 Jun 11:28:30 - [info] Linux 6.1.29 x64 LE
17 Jun 11:28:33 - [info] Loading palette nodes
[11:28:40] INFO: Service Node-RED exited with code 256 (by signal 9)
[11:28:41] INFO: Setting safe mode startup
[11:28:41] INFO: Starting Node-RED…