i have a problem with nodered Node-RED 10.2.0. I try to install it but when I go to open the web page it gives me error 502 bad gateway. I also installed ngnix but with previous versions it didn’t give any errors.
How could I solve?
1 Like
Do you have any hue nodes install by chance?
no i don’t have
this is log that not allow start node red.
12 Dec 12:36:56 - [warn] ------------------------------------------------------
12 Dec 12:36:56 - [info] Settings file : /etc/node-red/config.js
12 Dec 12:36:56 - [info] Context store : ‘default’ [module=memory]
12 Dec 12:36:56 - [info] User directory : /config/node-red/
12 Dec 12:36:56 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Dec 12:36:56 - [info] Flows file : /config/node-red/flows.json
12 Dec 12:36:56 - [info] Server now running at http://127.0.0.1:46836/
12 Dec 12:37:18 - [info] Starting flows
12 Dec 12:37:39 - [warn] [thingzi-twinkly-get:Twinky] POST http://192.168.1.157/xled/v1/login
12 Dec 12:37:39 - [warn] [thingzi-twinkly-get:Twinky] {“challenge”:“00000000000000000000000000000000000000000000”}
12 Dec 12:37:39 - [warn] [thingzi-twinkly-set:3307216e80877f25] POST http://192.168.1.157/xled/v1/login
12 Dec 12:37:39 - [warn] [thingzi-twinkly-set:3307216e80877f25] {“challenge”:“00000000000000000000000000000000000000000000”}
12 Dec 12:37:39 - [warn] [thingzi-twinkly-get:Twinky] POST http://192.168.1.157/xled/v1/login
12 Dec 12:37:39 - [warn] [thingzi-twinkly-get:Twinky] {“challenge”:“00000000000000000000000000000000000000000000”}
12 Dec 12:37:39 - [warn] [thingzi-twinkly-set:03b562f64c69efe8] POST http://192.168.1.157/xled/v1/login
12 Dec 12:37:39 - [warn] [thingzi-twinkly-set:03b562f64c69efe8] {“challenge”:“00000000000000000000000000000000000000000000”}
12 Dec 12:37:39 - [warn] [thingzi-twinkly-get:Twinky] POST http://192.168.1.157/xled/v1/login
12 Dec 12:37:39 - [warn] [thingzi-twinkly-get:Twinky] {“challenge”:“00000000000000000000000000000000000000000000”}
12 Dec 12:37:39 - [warn] [thingzi-twinkly-set:d53168b53b55c8be] POST http://192.168.1.157/xled/v1/login
12 Dec 12:37:39 - [warn] [thingzi-twinkly-set:d53168b53b55c8be] {“challenge”:“00000000000000000000000000000000000000000000”}
12 Dec 12:37:44 - [warn] [thingzi-twinkly-get:a09079.ed4b1f88] POST http://192.168.1.14/xled/v1/login
12 Dec 12:37:44 - [warn] [thingzi-twinkly-get:a09079.ed4b1f88] {“challenge”:“00000000000000000000000000000000000000000000”}
12 Dec 12:37:44 - [warn] [thingzi-twinkly-set:9b83bdf4.9742c] POST http://192.168.1.157/xled/v1/login
12 Dec 12:37:44 - [warn] [thingzi-twinkly-set:9b83bdf4.9742c] {“challenge”:“00000000000000000000000000000000000000000000”}
12 Dec 12:37:44 - [info] [fritzbox-callmonitor:49ea9337.0f9fdc] Connecting to fritzbox…
12 Dec 12:37:44 - [error] [pushbullet-config:FabsPushbullet] No credentials set for pushbullet config.
12 Dec 12:37:49 - [info] Started flows
(node:643) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 129 state listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
(Use node --trace-warnings ... to show where the warning was created)
(node:643) [DEP0128] DeprecationWarning: Invalid ‘main’ field in ‘/config/node-red/node_modules/node-red-dashboard/package.json’ of ‘none’. Please either fix that or report it to the module author
12 Dec 12:37:51 - [warn] [miio-roborock-server:roborock s6] Miio Roborock Error: Could not connect to device, handshake timeout
12 Dec 12:37:51 - [warn] [miio-roborock-server:Xiaomi Robot] Miio Roborock Error: Could not connect to device, handshake timeout
12 Dec 12:37:51 - [warn] [miio-humidifier-server:Umidificatore] Miio humiditifier Error: Could not connect to device, handshake timeout
12 Dec 12:37:51 - [red] Uncaught Exception:
12 Dec 12:37:51 - [error] Error: Could not connect to device, handshake timeout
at Timeout._onTimeout (/config/node-red/node_modules/node-red-contrib-miio-humidifier/node_modules/miio/lib/network.js:427:17)
at listOnTimeout (node:internal/timers:557:17)
at processTimers (node:internal/timers:500:7)
2021/12/12 12:37:51 [error] 624#624: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: “GET / HTTP/1.1”, upstream: “http://127.0.0.1:46836/”, host:
First thing would be to restore your backup. Then go to each flow tab and double click on them. Bottom left on the dialog box, disable. Do this to all your flow tabs, then upgrade.
It looks like there are several nodes that are not connecting. Overloading to the point HA resets your connection. Enable a page at a time and see if it is a node that is causing the problem.
1 Like