# Dashboard takes 10 min to load

**URL:** <https://discourse.nodered.org/t/dashboard-takes-10-min-to-load/72338>\
**Category:** General\
**Tags:** docker\
**Created:** [16 December 2022 20:56 UTC](https://discourse.nodered.org/t/dashboard-takes-10-min-to-load/72338 "2022-12-16T20:56:09Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jjm9](https://avatars.discourse-cdn.com/v4/letter/j/c4cdca/32.png) [@jjm9](https://discourse.nodered.org/u/jjm9)\
**Post date:** [16 December 2022 20:56 UTC](https://discourse.nodered.org/t/dashboard-takes-10-min-to-load/72338/1 "2022-12-16T20:56:09Z")

</div>

Hey there,

been using Node-RED for literally years now, and this never happened to me:

I noticed, that the docker container was unhealthy. Checking the logs, I only got this at first:

```auto
16 Dec 20:41:01 - [info] 
Welcome to Node-RED
===================
16 Dec 20:41:01 - [info] Node-RED version: v3.0.2
16 Dec 20:41:01 - [info] Node.js version: v16.16.0
16 Dec 20:41:01 - [info] Linux 5.4.0-135-generic x64 LE
16 Dec 20:41:11 - [info] Loading palette nodes

```

Ten minutes later, the dashboard has finally loaded, but I cannot really figure out, whats the problem here (there are some errors though):

```auto
16 Dec 20:50:46 - [info] Dashboard version 3.1.7 started at /ui
16 Dec 20:50:48 - [info] Settings file : /data/settings.js
16 Dec 20:50:48 - [info] Context store : 'default' [module=memory]
16 Dec 20:50:48 - [info] User directory : /data
16 Dec 20:50:48 - [warn] Projects disabled : editorTheme.projects.enabled=false
16 Dec 20:50:48 - [info] Flows file : /data/flows.json
16 Dec 20:50:50 - [info] Server now running at http://127.0.0.1:1880/
16 Dec 20:50:50 - [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.
---------------------------------------------------------------------
16 Dec 20:50:50 - [info] Starting flows
16 Dec 20:50:53 - [info] [fritzbox-callmonitor:7490] Connecting to fritzbox...
16 Dec 20:50:53 - [error] [mqtt out:Garage] missing broker configuration
16 Dec 20:50:54 - [info] Started flows
16 Dec 20:50:54 - [warn] [fritzbox-in:DSL-Link-Info] Device not ready.
16 Dec 20:50:54 - [info] [mqtt-broker:MQTT-Docker] Connected to broker: NR@mqtt://10.1.1.188:1883
16 Dec 20:50:54 - [info] [mqtt-broker:Loxberry] Connected to broker: mqtt://10.1.1.101:1883
16 Dec 20:50:54 - [info] [fritzbox-callmonitor:7490] Connected to fritzbox
16 Dec 20:50:54 - [info] [loxone-miniserver:14a36708249aedb8] Miniserver connected (10.1.1.50:80) using Token-Enc
16 Dec 20:50:54 - [info] [loxone-miniserver:14a36708249aedb8] got structure file 2022-11-20 14:09:09
16 Dec 20:50:56 - [info] [filter:Finde 1] nr-regexp-filter: message dropped (not matching the '(?:1)' regular expression)
16 Dec 20:50:56 - [info] [filter:Finde 1-6] nr-regexp-filter: message dropped (not matching the '[1,\2\,3\,4\,5\,6]' regular expression)
16 Dec 20:50:56 - [info] [filter:Finde 2 (Akustisch)] nr-regexp-filter: message dropped (not matching the '(?:2)' regular expression)
16 Dec 20:51:05 - [error] [better-sonos-control:Pause] Error: HTTP response code 500 for "urn:schemas-upnp-org:service:AVTransport:1#Pause"
Error: HTTP response code 500 for "urn:schemas-upnp-org:service:AVTransport:1#Pause"
    at Request._callback (/data/node_modules/sonos/lib/sonos.js:216:23)
    at Request.self.callback (/data/node_modules/request/request.js:185:22)
    at Request.emit (node:events:527:28)
    at Request.<anonymous> (/data/node_modules/request/request.js:1154:10)
    at Request.emit (node:events:527:28)
    at IncomingMessage.<anonymous> (/data/node_modules/request/request.js:1076:12)
    at Object.onceWrapper (node:events:641:28)
    at IncomingMessage.emit (node:events:539:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
16 Dec 20:51:51 - [info] [mqtt-broker:Mosquitto Synology] Connection failed to broker: mqtt://10.1.1.10:1883
iot/atr/+/a46366b9-aa3a-44ec-9369-324694b50463/snxbvc/4Saj/j
16 Dec 20:52:09 - [info] [mqtt-broker:Mosquitto Synology] Connected to broker: mqtt://10.1.1.10:1883

```

I havent altered the flows in a long time (like weeks, or months).

My suspicion is, that since I am running watchtower, that there has been and update breaking things.

Appreciate any help!

---

<div class="post-metadata">

**Author:** ![hotNipi](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hotnipi/32/383_2.png) [@hotNipi](https://discourse.nodered.org/u/hotNipi)\
**Post date:** [16 December 2022 21:11 UTC](https://discourse.nodered.org/t/dashboard-takes-10-min-to-load/72338/2 "2022-12-16T21:11:17Z")

</div>

Any proxy?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [16 December 2022 21:37 UTC](https://discourse.nodered.org/t/dashboard-takes-10-min-to-load/72338/3 "2022-12-16T21:37:59Z")

</div>

Set the log level to trace in settings.js and see if that gives any clues as to where the delay is

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [17 December 2022 01:43 UTC](https://discourse.nodered.org/t/dashboard-takes-10-min-to-load/72338/4 "2022-12-17T01:43:32Z")

</div>

That length of time quite possibly implies a TCP timeout - something waiting for a TCP/IP response and not getting it then trying again with the same result. Just a guess though. As Colin says, a trace level log should give further clues.

---

<div class="post-metadata">

**Author:** ![jjm9](https://avatars.discourse-cdn.com/v4/letter/j/c4cdca/32.png) [@jjm9](https://discourse.nodered.org/u/jjm9)\
**Post date:** [6 January 2023 22:38 UTC](https://discourse.nodered.org/t/dashboard-takes-10-min-to-load/72338/5 "2023-01-06T22:38:20Z")

</div>

Everything works as expected again.  
Problem was with the docker instance under which NR is running.  
Thanks anyway!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [20 January 2023 22:39 UTC](https://discourse.nodered.org/t/dashboard-takes-10-min-to-load/72338/6 "2023-01-20T22:39:06Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.