# Dashboard blank after upgrade

**URL:** https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343
**Category:** Dashboard
**Created:** [27 October 2018 18:17 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343 "2018-10-27T18:17:59Z")
**Posts on this page:** 13
**Page:** 1

<div class="post-metadata">

### Author: ![Mats](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@Mats](https://discourse.nodered.org/u/Mats)
#### Post date: [27 October 2018 18:17 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/1 "2018-10-27T18:17:59Z")

</div>

My Dashboard is completely blank since my latest upgrade.  
Running Dashboard 2.10.0, Node-Red 0.19.4, Node 8.12.0

Can´t find any error messages anywhere in Node-Red.

When loading the UI page in Chrome i get the following error:

"app.min.js:140 TypeError: io is not a function  
at Object.connect (app.min.js:554)  
at Object. (app.min.js:553)  
at Object.invoke (app.min.js:63)  
at R.instance (app.min.js:112)  
at n (app.min.js:87)  
at g (app.min.js:80)  
at app.min.js:80  
at app.min.js:42  
at m.$eval (app.min.js:168)  
at m.$apply (app.min.js:168)"

I have uninstalled and reinstalled the dashboard node.

Ny ideas?

Thanks

/Mats

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [27 October 2018 18:37 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/2 "2018-10-27T18:37:08Z")

</div>

It's usually takes a couple hard reloads of the page to flush the browser cache.

---

<div class="post-metadata">

### Author: ![Mats](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@Mats](https://discourse.nodered.org/u/Mats)
#### Post date: [28 October 2018 09:21 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/3 "2018-10-28T09:21:50Z")

</div>

Tried that. Also tried different browsers on different devices. No luck so far...

---

<div class="post-metadata">

### Author: ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [28 October 2018 09:28 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/4 "2018-10-28T09:28:06Z")

</div>

It can be difficult to clear cashing.  
I've found the easiest way to 100% rule out caching is to load the site in chrome incognito mode...

---

<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: [28 October 2018 09:49 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/5 "2018-10-28T09:49:27Z")

</div>

> [@Mats](#):
>
> My Dashboard is completely blank since my latest upgrade.

What did you upgrade and how?

---

<div class="post-metadata">

### Author: ![Mats](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@Mats](https://discourse.nodered.org/u/Mats)
#### Post date: [30 October 2018 12:19 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/6 "2018-10-30T12:19:03Z")

</div>

I´m on a RPi so I used the script that updates node-red and node. I think i needed to reinstall the dashboard node manually after that, but I am not sure. It was some time ago.  
To try to remedy the problem I have since upgraded npm and then upgraded everything possible with "sudo apt-get upgrade". I have also uninstalled and reinstalled the dashboard node both through the palette manager and with npm.  
I have uninstalled all other "extra" nodes that are not in use. I have removed all dashboard nodes in my flow and started over with a simple test.  
I still get exactly the same problem all the time. Now I am running out of ideas other than reinstalling the complete rpi on a new memory card, which I would really like to avoid...

---

<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: [30 October 2018 13:25 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/7 "2018-10-30T13:25:44Z")

</div>

In a terminal run node-red-log, then in another terminal restart node-red. Then try to open the ui in a browser. Post the messages from the log terminal here. Someone may see something relevant.

---

<div class="post-metadata">

### Author: ![Mats](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@Mats](https://discourse.nodered.org/u/Mats)
#### Post date: [30 October 2018 20:45 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/8 "2018-10-30T20:45:20Z")

</div>

Ok, here is the log from a fresh restart of node-red. Unfortunately nothing happens in the log window when I open the ui in a browser.

# Starting Node-RED graphical event wiring tool... Started Node-RED graphical event wiring tool. 30 Oct 21:39:04 - [info] Welcome to Node-RED

## 30 Oct 21:39:04 - [info] Node-RED version: v0.19.4 30 Oct 21:39:04 - [info] Node.js version: v8.12.0 30 Oct 21:39:04 - [info] Linux 4.9.35-v7+ arm LE 30 Oct 21:39:05 - [info] Loading palette nodes 30 Oct 21:39:10 - [info] Dashboard version 2.10.0 started at /ui 30 Oct 21:39:11 - [info] Settings file : /home/pi/.node-red/settings.js 30 Oct 21:39:11 - [info] HTTP Static : /home/pi/bilder 30 Oct 21:39:11 - [info] Context store : 'default' [module=localfilesystem] 30 Oct 21:39:11 - [info] User directory : /home/pi/.node-red 30 Oct 21:39:11 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable 30 Oct 21:39:11 - [info] Flows file : /home/pi/.node-red/flows\_pitre.json 30 Oct 21:39:11 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/) 30 Oct 21:39:11 - [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.

30 Oct 21:39:11 - [info] Starting flows  
30 Oct 21:39:12 - [info] Started flows

---

<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: [30 October 2018 21:07 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/9 "2018-10-30T21:07:40Z")

</div>

That all looks ok, but you are still getting the error in the browser. I presume there is nothing in the log when you open the browser.  
In your situation I can't think of anything else to do other than completely uninstall node-red and reinstall it. I am not sure of the easiest way to do that though. Hopefully someone will chip in and tell us. I couldn't see it in the docs.

---

<div class="post-metadata">

### Author: ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [30 October 2018 23:41 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/10 "2018-10-30T23:41:34Z")

</div>

What nodes do you have installed? If you go to .node-red/node\_modules (`cd .node-red/node_modules`) and type `ls node-red*` what shows up?

Can you also supply your flow file? You will need to back up a level (`cd ..`) and enter `cat flows_pitre.json` tehn copy it and past it to a reply making sure to add three backtic's on the line before you past in the flow and the line after the flow.

---

<div class="post-metadata">

### Author: ![Phealc](https://avatars.discourse-cdn.com/v4/letter/p/b2d939/32.png) [@Phealc](https://discourse.nodered.org/u/Phealc)
#### Post date: [13 October 2019 11:21 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/11 "2019-10-13T11:21:16Z")

</div>

Might be a red herring but I got a similar issue when the SDHC card crashed and I had to rebuild the RPI. After all was re-installed I imported the diligently backed-up flow only to find the dashboard config was not backed up with the export. Same issue as you, all works but no UI. Can you check the dashboard menu on the RHS of the Node-Red IDE to see if your config is there?

---

<div class="post-metadata">

### Author: ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [13 October 2019 11:25 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/12 "2019-10-13T11:25:53Z")

</div>

@Phealc did you notice the last response on this thread was 12 months ago??

---

<div class="post-metadata">

### Author: ![Phealc](https://avatars.discourse-cdn.com/v4/letter/p/b2d939/32.png) [@Phealc](https://discourse.nodered.org/u/Phealc)
#### Post date: [24 October 2019 11:24 UTC](https://discourse.nodered.org/t/dashboard-blank-after-upgrade/4343/13 "2019-10-24T11:24:59Z")

</div>

Yes, after I responded!!
