At some point in time my Node Red flows stopped loading in quickly in the GUI, and just showed “Loading Plugins”. It can take upward of 10 minutes for it to get going again. The flows are working fine even while this is happening. I have no idea how to troubleshoot that in HA. Any tips?
What version are running? There was an issue 3 years ago that I found. Hopefully not running it 3 years out of date 
Otherwise you will probably want to post the logs.
It is completely up to date, and the weird thing that the change didn’t happen after an update. Suddenly it was just slow.
In the meantime I did some more experimenting and it turns out Firefox can somewhat reliable load the interface within minutes. Chrome etc. don’t seem to work at all now and just hang for hours.
What logfile do you need? Mind you I’m in no way shape or form a Linux guy, so if we need to go digging outside the HA interface, I’m going to need some pointers.
I assume you are running NR via add-on? I don’t remember exactly, but there are probably logs there.
Yes, there is a log-section directly in the HA interface for NR. I’ve tried looking at it before, but apart from some warnings about vulnerable packages (a bit weird), there is not much else standing out.
The log below is from a clean restart of NR. I tried loading the interface up at 09:45, but like before the log doesn’t log anything particular. The pings at the end is simply a flow checking for the availability of two devices. Apart from that nothing gets logged.
*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*
*-----------------------------------------------------------*
* Add-on: Node-RED*
* Flow-based programming for the Internet of Things*
*-----------------------------------------------------------*
* Add-on version: 16.0.2*
* You are running the latest version of this add-on.*
* System: Home Assistant OS 11.2 (aarch64 / raspberrypi4-64)*
* Home Assistant Core: 2023.12.1*
* Home Assistant Supervisor: 2023.11.6*
*-----------------------------------------------------------*
* 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-customizations successfully started*
*s6-rc: info: service init-nodered: starting*
*s6-rc: info: service init-nginx successfully started*
*up to date, audited 470 packages in 11s*
*46 packages are looking for funding*
* run `npm fund` for details*
*24 vulnerabilities (15 moderate, 9 high)*
*To address issues that do not require attention, run:*
* npm audit fix*
*To address all issues (including breaking changes), run:*
* npm audit fix --force*
*Run `npm audit` for details.*
*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*
*[09:43:45] INFO: Starting Node-RED...*
*> start*
*> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js*
*13 Dec 09:43:49 - [info] *
*Welcome to Node-RED*
*===================*
*13 Dec 09:43:49 - [info] Node-RED version: v3.1.0*
*13 Dec 09:43:49 - [info] Node.js version: v18.18.2*
*13 Dec 09:43:49 - [info] Linux 6.1.58-haos-raspi arm64 LE*
*13 Dec 09:43:51 - [info] Loading palette nodes*
*13 Dec 09:43:59 - [info] Dashboard version 3.6.1 started at /endpoint/ui*
*13 Dec 09:44:03 - [info] Settings file : /etc/node-red/config.js*
*13 Dec 09:44:03 - [info] Context store : 'default' [module=memory]*
*13 Dec 09:44:03 - [info] User directory : /config/*
*13 Dec 09:44:03 - [warn] Projects disabled : editorTheme.projects.enabled=false*
*13 Dec 09:44:03 - [info] Flows file : /config/flows.json*
*13 Dec 09:44:03 - [info] Server now running at http://127.0.0.1:46836/*
*13 Dec 09:44:03 - [info] Starting flows*
*13 Dec 09:44:03 - [info] [hue-bridge:Philips hue] Initializing the bridge (10.100.130.10)…*
*[09:44:03] INFO: Starting NGinx...*
*13 Dec 09:44:04 - [info] Started flows*
*13 Dec 09:44:04 - [error] [api-current-state:aff1e52e2d0213ba] InputError: Entity could not be found in cache for entityId: sensor.temperature_entrance_temperature*
*13 Dec 09:44:04 - [error] [api-current-state:89e5403b08c7250b] InputError: Entity could not be found in cache for entityId: sensor.temperature_cinema_temperature*
*13 Dec 09:44:04 - [info] [hue-bridge:Philips hue] Connected to bridge*
*13 Dec 09:44:05 - [info] [mqtt-broker:MQTT-broker] Connected to broker: mqtt://localhost:1883*
*13 Dec 09:44:05 - [info] [hue-bridge:Philips hue] Processing bridge resources…*
*13 Dec 09:44:05 - [info] [hue-bridge:Philips hue] Initial emit of resource states…*
*13 Dec 09:44:05 - [info] [hue-bridge:Philips hue] Keeping nodes up-to-date…*
*13 Dec 09:44:05 - [info] [hue-bridge:Philips hue] Subscribing to bridge events…*
*13 Dec 09:44:08 - [info] [server:Home Assistant] Connecting to http://supervisor/core*
*13 Dec 09:44:08 - [info] [server:Home Assistant] Connected to http://supervisor/core*
*13 Dec 09:44:40 - [info] [ping:Ping MPC04] ping - Host '10.100.115.24' process timeout - sending SIGINT*
*13 Dec 09:44:40 - [info] [ping:Ping MPC05] ping - Host '10.100.115.25' process timeout - sending SIGINT*
*13 Dec 09:45:10 - [info] [ping:Ping MPC04] ping - Host '10.100.115.24' process timeout - sending SIGINT*
*13 Dec 09:45:10 - [info] [ping:Ping MPC05] ping - Host '10.100.115.25' process timeout - sending SIGINT*
*13 Dec 09:45:40 - [info] [ping:Ping MPC04] ping - Host '10.100.115.24' process timeout - sending SIGINT*
*13 Dec 09:45:40 - [info] [ping:Ping MPC05] ping - Host '10.100.115.25' process timeout - sending SIGINT*
*13 Dec 09:46:10 - [info] [ping:Ping MPC04] ping - Host '10.100.115.24' process timeout - sending SIGINT*
*13 Dec 09:46:10 - [info] [ping:Ping MPC05] ping - Host '10.100.115.25' process timeout - sending SIGINT*
Is there an option for more verbose logs? Eg changing “Info” to “Debug”
I found the log level setting and tried debug. I get a lot more when NR is restarted, but afterwards it goes back to the info-level logs. Still nothing extra in the log when attempting to open the web interface in another browser and it hangs.
===================
13 Dec 21:34:00 - [info] Node-RED version: v3.1.0
13 Dec 21:34:00 - [info] Node.js version: v18.18.2
13 Dec 21:34:00 - [info] Linux 6.1.58-haos-raspi arm64 LE
13 Dec 21:34:02 - [info] Loading palette nodes
13 Dec 21:34:04 - [debug] Module: node-red-contrib-boolean-logic-ultimate 1.1.1 /config/node_modules/node-red-contrib-boolean-logic-ultimate
13 Dec 21:34:04 - [debug] Module: node-red-contrib-broadlink-control 2.1.6 /config/node_modules/node-red-contrib-broadlink-control
13 Dec 21:34:04 - [debug] Module: node-red-contrib-countdown 1.3.2 /config/node_modules/node-red-contrib-countdown
13 Dec 21:34:04 - [debug] Module: node-red-contrib-home-assistant-websocket 0.59.0 /config/node_modules/node-red-contrib-home-assistant-websocket
13 Dec 21:34:04 - [debug] Module: node-red-contrib-huemagic 4.2.2 /config/node_modules/node-red-contrib-huemagic
13 Dec 21:34:04 - [debug] Module: node-red-contrib-loop 1.0.1 /config/node_modules/node-red-contrib-loop
13 Dec 21:34:04 - [debug] Module: node-red-contrib-nordpool-api-plus 4.5.0 /config/node_modules/node-red-contrib-nordpool-api-plus
13 Dec 21:34:04 - [debug] Module: node-red-contrib-shelly 10.16.0 /config/node_modules/node-red-contrib-shelly
13 Dec 21:34:04 - [debug] Module: node-red-contrib-sonos-plus 6.7.3 /config/node_modules/node-red-contrib-sonos-plus
13 Dec 21:34:04 - [debug] Module: node-red-dashboard 3.6.1 /config/node_modules/node-red-dashboard
13 Dec 21:34:04 - [debug] Module: node-red-node-ping 0.3.3 /config/node_modules/node-red-node-ping
13 Dec 21:34:04 - [debug] Module: node-red-node-serialport 2.0.0 /config/node_modules/node-red-node-serialport
13 Dec 21:34:04 - [debug] Module: node-red-node-twilio 0.1.0 /config/node_modules/node-red-node-twilio
13 Dec 21:34:04 - [debug] Module: @node-red-contrib-themes/theme-collection 3.1.5 /opt/node_modules/@node-red-contrib-themes/theme-collection
13 Dec 21:34:04 - [debug] Module: node-red-contrib-bigtimer 2.8.5 /opt/node_modules/node-red-contrib-bigtimer
13 Dec 21:34:04 - [debug] Module: node-red-contrib-cast 0.2.17 /opt/node_modules/node-red-contrib-cast
13 Dec 21:34:04 - [debug] Module: node-red-contrib-counter 0.1.6 /opt/node_modules/node-red-contrib-counter
13 Dec 21:34:04 - [debug] ! Module: node-red-contrib-home-assistant-websocket 0.59.0 /opt/node_modules/node-red-contrib-home-assistant-websocket *ignored due to local copy*
13 Dec 21:34:04 - [debug] Module: node-red-contrib-influxdb 0.6.1 /opt/node_modules/node-red-contrib-influxdb
13 Dec 21:34:04 - [debug] Module: node-red-contrib-interval-length 0.0.6 /opt/node_modules/node-red-contrib-interval-length
13 Dec 21:34:04 - [debug] Module: node-red-contrib-modbus 5.27.2 /opt/node_modules/node-red-contrib-modbus
13 Dec 21:34:04 - [debug] Module: node-red-contrib-moment 5.0.0 /opt/node_modules/node-red-contrib-moment
13 Dec 21:34:04 - [debug] Module: node-red-contrib-persistent-fsm 1.2.1 /opt/node_modules/node-red-contrib-persistent-fsm
13 Dec 21:34:04 - [debug] Module: node-red-contrib-sunevents 3.1.1 /opt/node_modules/node-red-contrib-sunevents
13 Dec 21:34:04 - [debug] Module: node-red-contrib-time-range-switch 1.2.0 /opt/node_modules/node-red-contrib-time-range-switch
13 Dec 21:34:04 - [debug] ! Module: node-red-dashboard 3.6.1 /opt/node_modules/node-red-dashboard *ignored due to local copy*
13 Dec 21:34:04 - [debug] Module: node-red-node-base64 0.3.0 /opt/node_modules/node-red-node-base64
13 Dec 21:34:04 - [debug] Module: node-red-node-email 2.0.1 /opt/node_modules/node-red-node-email
13 Dec 21:34:04 - [debug] Module: node-red-node-feedparser 0.3.0 /opt/node_modules/node-red-node-feedparser
13 Dec 21:34:04 - [debug] ! Module: node-red-node-ping 0.3.3 /opt/node_modules/node-red-node-ping *ignored due to local copy*
13 Dec 21:34:04 - [debug] Module: node-red-node-random 0.4.1 /opt/node_modules/node-red-node-random
13 Dec 21:34:04 - [debug] ! Module: node-red-node-serialport 1.0.4 /opt/node_modules/node-red-node-serialport *ignored due to local copy*
13 Dec 21:34:04 - [debug] Module: node-red-node-smooth 0.1.2 /opt/node_modules/node-red-node-smooth
13 Dec 21:34:04 - [debug] Module: node-red-node-suncalc 1.1.0 /opt/node_modules/node-red-node-suncalc
13 Dec 21:34:04 - [debug] Module: node-red-node-twitter 1.2.0 /opt/node_modules/node-red-node-twitter
13 Dec 21:34:11 - [info] Dashboard version 3.6.1 started at /endpoint/ui
Go to the addon page → configuration and enable safe mode, save and restart. Go to NR choose manage palette (right hand side hamburger menu) and look to see if you have nodes that need to be updated.
If that is not the cause, disable all flows and enable a page at a time refreshing to see when loading begins to lag.
Unfortunately no, it is still the same problem. Using Firefox to load it it, but it is still very slow to get past the “Loading Plugins” part.
I tried Mikefila’s suggestion, but no joy. All nodes look good, no updates needed and disabling every single flow still resulted in the same slow startup.
Thanks for the replies guys. Weirdly disabling flows does not seem to stop them screwing up nodered/nginx/ingress in my case. I went in via putty and backed up my flows, then went back into the gui and deleted everything I didn’t need, including various unused servers, and it all came back to life.
The only thing left is 3rd party nodes but they should be disabled in safe mode. In safe mode you still have the lag? When you boot into safe mode, look at the logs and see what it is loading. If any 3rd party nodes load during, find them and remove them.
Yeah, unfortunately safe mode doesn’t have any effect at all.