Node Red fails to start

Third party integrations Node-RED
1

Node Red on HA has been working well for a couple of years, but recently something has broken it - It - it won’t start and I get the message “502 Bad Gateway . nginx”.

The log file on startup shows:

“5 Dec 18:02:17 - [error] [api-call-service:Stairs Light On] Call-Service attempted without connection to server.
5 Dec 18:02:17 - [info] [server:Home Assistant] WebSocket Connected to http://supervisor/core
5 Dec 18:02:17 - [warn] [pushbullet-config:Jim] Unable to get history.
5 Dec 18:02:19 - [red] Uncaught Exception:
5 Dec 18:02:19 - [error] Error: Huejay: connect EHOSTUNREACH 192.168.1.142:80
at /config/node-red/node_modules/huejay/lib/Transport.js:106:15
at processTicksAndRejections (node:internal/process/task_queues:96:5)
[18:02:19] INFO: Starting Node-RED…”

I also get:
“5 Dec 18:30:29 - [error] [pushover:d0a83d36.35d8e8] No Pushover user key set
5 Dec 18:30:29 - [info] Started flows
(node:2721) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to ‘0’ makes TLS connections and HTTPS requests insecure by disabling certificate verification.”

Can anyone help me please - I’m now of an age where the grey cells aren’t so agile and problem solving doesn’t come easy!

Jim

2

It looks like the hue service maybe causing problems. From a few days ago

3

Thanks for the reply, ‘mikefila’.

I ‘cut the Gordian Knot’ by restoring an old backup and it’s back to working now.

It’s taught me not to install updates when everything is working OK!

Jim

4

I fixed it by removing this line of code in the Transport.js file in the huejay lib


throw new HuejayError({
            type:    result.error.type,
            message: result.error.description,
          });
1 Like