Dashboard gone blank after upgrade

Dashboard
1

Hi all!

After upgrading node-red my dashboard is loading just a blank page. Interestingly, the UI-page loads and works fine. I have read other threads here and tried the following:

  1. flushing the cache
  2. using another browser
  3. running it in incognito mode
  4. hitting F12 during startup. Here it seems that all is loading well except for "comms" which stays on "pending" and does not load anything

image
image.png926Ă—180 8.58 KB

Any ideas what could be done?

2

what version of nodejs node-red and dashboard are you using?

3

I am using node-red version 0.20.5 and dashboard 2.17.0

4

and the version of nodejs?

5

Nodejs version is v10.16.0

6

You said you upgraded node-red but the version you specify is not the latest. How did you upgrade it? Also what OS are you running?

7

@Colin, thanks for chiming in. I have node-red installed on a Raspberry Pi (Linux RaspiCNXHome 4.19.42-v7+ #1219 SMP Tue May 14 21:20:58 BST 2019 armv7l). The upgrade was done on the dashboard (palette) and node-red version 0.20.5 seems to be the latest which is being offered.

I upgraded yesterday the dashboard from dashboard 2.17.0 to .1 but the problem remains the same

8

How did you install node-red? To upgrade node-red you can use the script provided in the docs for running on a Pi.
That will not necessarily fix whatever the problem is, but will at least make sure you are up to date.

9

Thanks Colin. I installed it from some description I have found here, but it is half a year ago and do not remember the details. Will see in the docs now on how to upgrade with the script and report back

10

Make sure you have your flows file backed up, but not doubt you already do anyway.

11

image

I have updated now as you can see. Node-red is now v 1.01. No change. Dashboard is still blank.

12

I have a backup of the entire SD-card in the Raspberry Pi and wondering if it will be easy enough to restore. Well, for right now I am running out of options and don´t know how to get the dashboard back

14

I thought you were going to use the recommended update script for the pi
https://nodered.org/docs/getting-started/raspberrypi

Also please use copy/paste wherever possible rather than screenshot.

1 Like
15

Also have a look in the browser console and see if there is anything suspicious there.

16

I did use something recommended for updates, not for a fresh install:

https://nodered.org/docs/getting-started/local#upgrading-node-red

I had a look in the browser console and it is still the "comms" file which is not loading. This is suspicious, I would say but I don´t know what needs to be done so it will load correctly.

image
image.png705Ă—245 13 KB

17

I’m by no means an expert, but had the same issue with latest dashboard on node-red 0.20, and had to update my nodejs and npm to get to update node-red itself (old npm wouldn’t work). So then I had to rebuild all the old node_modules too or else they wouldn’t all work. If you don’t have errors in the debug window in node-red it might not be it though.

Also I had to redo the configuration on several dashboard components after dashboard update.

Also check whether you upgraded node-red with the same user you previously ran node-red as.

18

If you say that you have had the same error, that means also "comms" wasn´t loading?

19

comms is a websocket - it doesn't actually load.

1 Like
20

uhmmm.... so what I am seeing in the console above (see screenshot) that "comms" is pending is normal?

21

In my logs of the Raspberry it says the following

Oct 16 04:56:28 RaspiCNXHome bash[468]: [+] 0.2.197 16-10-2019 04:56:28 AM [CMD-NAME]        94:65:2D:2C:43:EC OnePlus 3T  Unknown
Oct 16 04:56:28 RaspiCNXHome bash[468]: [+] 0.2.197 16-10-2019 04:56:28 AM [CMD-MQTT]        cnx/monitor/raspi_monitor/oneplus { ... confidence : 10
Oct 16 04:56:34 RaspiCNXHome Node-RED[373]: 16 Oct 04:56:34 - [red] Uncaught Exception:
Oct 16 04:56:34 RaspiCNXHome Node-RED[373]: 16 Oct 04:56:34 - TypeError: Cannot read property 'warn' of undefined
Oct 16 04:56:34 RaspiCNXHome Node-RED[373]:     at /home/pi/.node-red/node_modules/node-red-contrib-mdashboard/nodes/ui_base.js:93:29
Oct 16 04:56:34 RaspiCNXHome Node-RED[373]:     at /usr/lib/node_modules/node-red/node_modules/express/lib/response.js:434:22
Oct 16 04:56:34 RaspiCNXHome Node-RED[373]:     at SendStream.onerror (/usr/lib/node_modules/node-red/node_modules/express/lib/response.js:1044:5)
Oct 16 04:56:34 RaspiCNXHome Node-RED[373]:     at SendStream.emit (events.js:198:13)
Oct 16 04:56:34 RaspiCNXHome Node-RED[373]:     at SendStream.error (/usr/lib/node_modules/node-red/node_modules/send/index.js:270:17)
Oct 16 04:56:34 RaspiCNXHome Node-RED[373]:     at SendStream.onStatError (/usr/lib/node_modules/node-red/node_modules/send/index.js:421:12)
Oct 16 04:56:34 RaspiCNXHome Node-RED[373]:     at onstat (/usr/lib/node_modules/node-red/node_modules/send/index.js:726:26)
Oct 16 04:56:34 RaspiCNXHome Node-RED[373]:     at FSReqWrap.oncomplete (fs.js:153:21)
Oct 16 04:56:40 RaspiCNXHome systemd[1]: nodered.service: Main process exited, code=exited, status=1/FAILURE
Oct 16 04:56:40 RaspiCNXHome systemd[1]: nodered.service: Unit entered failed state.
Oct 16 04:56:40 RaspiCNXHome systemd[1]: nodered.service: Failed with result 'exit-code'.
Oct 16 04:56:40 RaspiCNXHome systemd[1]: nodered.service: Service hold-off time over, scheduling restart.
Oct 16 04:56:40 RaspiCNXHome systemd[1]: Stopped Node-RED graphical event wiring tool.
Oct 16 04:56:40 RaspiCNXHome systemd[1]: Started Node-RED graphical event wiring tool.

Any ideas what this could be?