# Node red GUI won't load after update

**URL:** <https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673>\
**Category:** General\
**Created:** [14 October 2019 06:46 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673 "2019-10-14T06:46:37Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjdula](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mjdula](https://discourse.nodered.org/u/mjdula)\
**Post date:** [14 October 2019 06:46 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/1 "2019-10-14T06:46:38Z")

</div>

I have recently attempted to update to node red 1.0.0 on pi 3 and zero w. I used the bash script to upgrade. After complete I start node red and when I attempt to open through local ip and server addresses but the pages gui won't load.

I am new to node red and the pi and had the process working prior to the 1.0.0 update. Can anyone help me work through this.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [14 October 2019 06:54 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/2 "2019-10-14T06:54:09Z")

</div>

Did you [search](https://discourse.nodered.org/t/dashboard-gone-blank-after-upgrade/16542) the forum ?  
Verify the versions of npm, nodejs, dashboard.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [14 October 2019 07:56 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/3 "2019-10-14T07:56:33Z")

</div>

what does the `/var/log/nodered-install.log` file contain ?

---

<div class="post-metadata">

**Author:** ![mjdula](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mjdula](https://discourse.nodered.org/u/mjdula)\
**Post date:** [14 October 2019 08:17 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/4 "2019-10-14T08:17:05Z")

</div>

# Welcome to Node-RED

14 Oct 19:15:54 - [info] Node-RED version: v1.0.1  
14 Oct 19:15:54 - [info] Node.js version: v10.16.3  
14 Oct 19:15:54 - [info] Linux 4.19.75-v7+ arm LE  
14 Oct 19:15:56 - [info] Loading palette nodes  
14 Oct 19:16:04 - [info] Dashboard version 2.17.1 started at /ui  
14 Oct 19:16:05 - [info] Settings file : /home/pi/.node-red/settings.js  
14 Oct 19:16:05 - [info] Context store : 'default' [module=memory]  
14 Oct 19:16:05 - [info] User directory : /home/pi/.node-red  
14 Oct 19:16:05 - [warn] Projects disabled : editorTheme.projects.enabled=false  
14 Oct 19:16:05 - [info] Flows file : /home/pi/.node-red/flows\_raspberrypi.json  
14 Oct 19:16:05 - [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.

14 Oct 19:16:05 - [info] Starting flows  
14 Oct 19:16:05 - [info] Started flows  
14 Oct 19:16:05 - [info] [inject:Temp Check] repeat = 5000  
14 Oct 19:16:06 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)  
14 Oct 19:16:06 - [info] [rpi-gpio out:Heat Lamp 1] out: 0

---

<div class="post-metadata">

**Author:** ![mjdula](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mjdula](https://discourse.nodered.org/u/mjdula)\
**Post date:** [14 October 2019 19:45 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/5 "2019-10-14T19:45:02Z")

</div>

Im sorry guys, I'm very to new to all this tech being pi and node red and I'm self teaching. I have a var/log/nodered-install.log but there is to much to post. I have attempted to start fresh from new noobs install and would appreciate best practice to move on from here.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [14 October 2019 19:56 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/6 "2019-10-14T19:56:13Z")

</div>

Follow the docs. There is a page for the raspberry pi with instructions

---

<div class="post-metadata">

**Author:** ![mjdula](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mjdula](https://discourse.nodered.org/u/mjdula)\
**Post date:** [14 October 2019 20:09 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/7 "2019-10-14T20:09:53Z")

</div>

I have followed the docs from raspberry pi to update node.js and node-red and nom through the bash script but everytime I do upgrade. I am then unable to log into the server or the local address. Nodered boots in the terminal window as a systemd. But when I point a browser to the ip address shown in terminal it will not load.

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [14 October 2019 20:17 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/8 "2019-10-14T20:17:21Z")

</div>

> [@mjdula](#):
>
> I have followed the docs from raspberry pi

Just to be clear - do you mean these docs?

[https://nodered.org/docs/getting-started/raspberrypi](https://nodered.org/docs/getting-started/raspberrypi)

---

<div class="post-metadata">

**Author:** ![mjdula](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mjdula](https://discourse.nodered.org/u/mjdula)\
**Post date:** [14 October 2019 20:32 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/9 "2019-10-14T20:32:47Z")

</div>

Yes, that's the process and doc I used to install and attempt to run. Can I just ask, I reread the section on freeing up extra memory. Is node-red-pi --max-old-space-size=256 a one off terminal entry have the free space changed or should it be used on every boot of nodered

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [14 October 2019 20:40 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/10 "2019-10-14T20:40:20Z")

</div>

are you pointing a browser on a different computer at 127.0.0.1:1880 ?

That means “this machine” you need to find out the ip address that the node-red machine has on your network and use that

---

<div class="post-metadata">

**Author:** ![mjdula](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mjdula](https://discourse.nodered.org/u/mjdula)\
**Post date:** [14 October 2019 20:59 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/11 "2019-10-14T20:59:29Z")

</div>

Yes I am. I have tried using that server address and also using the local ip through chromium on the pi itself. I have even tried login into the pi through vnc.

I will try a full format and start again.

---

<div class="post-metadata">

**Author:** ![mjdula](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mjdula](https://discourse.nodered.org/u/mjdula)\
**Post date:** [15 October 2019 10:14 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/12 "2019-10-15T10:14:23Z")

</div>

Found the issue with the upgrade. After running noobs I allow the system to update recommended software. For some reason this caused instability.

After a fresh install, updating raspian, node red and node.js through terminal evetything is aok.

---

<div class="post-metadata">

**Author:** ![mjdula](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mjdula](https://discourse.nodered.org/u/mjdula)\
**Post date:** [13 November 2019 10:49 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/13 "2019-11-13T10:49:06Z")

</div>

Hey guys, need to start this over. After the full rebuilt of raspian, updated or and node red to latest versions the dashboard worked a couple of times. Now it will not load. Once came up saying add dashboard nodes to use, there nodes there. I have tried to loading it on different machines without luck. Also loading the node red editor using the local address is very very slow. Will not load using the server address 127.0.0.1

---

<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:** [13 November 2019 11:12 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/14 "2019-11-13T11:12:14Z")

</div>

Restart node red in a terminal and post the log here. Assuming you installed using the `bash <(curl` script then you can do that using

```auto
node-red-stop
node-red-start

```

---

<div class="post-metadata">

**Author:** ![mjdula](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mjdula](https://discourse.nodered.org/u/mjdula)\
**Post date:** [14 November 2019 02:25 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/15 "2019-11-14T02:25:18Z")

</div>

pi@raspberrypi:~ $ node-red-start

Start Node-RED

Once Node-RED has started, point a browser at [http://192.168.0.25:1880](http://192.168.0.25:1880)  
On Pi Node-RED works better with the Firefox or Chrome browser

Use node-red-stop to stop Node-RED  
Use node-red-start to start Node-RED again  
Use node-red-log to view the recent log output  
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot  
Use sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to [http://flows.nodered.org](http://flows.nodered.org)

# Starting as a systemd service. 14 Nov 13:24:01 - [info] Welcome to Node-RED

## 14 Nov 13:24:02 - [info] Node-RED version: v1.0.2 14 Nov 13:24:02 - [info] Node.js version: v10.17.0 14 Nov 13:24:02 - [info] Linux 4.19.75-v7+ arm LE 14 Nov 13:24:03 - [info] Loading palette nodes 14 Nov 13:24:06 - [info] Dashboard version 2.17.1 started at /ui 14 Nov 13:24:07 - [info] Settings file : /home/pi/.node-red/settings.js 14 Nov 13:24:07 - [info] Context store : 'default' [module=memory] 14 Nov 13:24:07 - [info] User directory : /home/pi/.node-red 14 Nov 13:24:07 - [warn] Projects disabled : editorTheme.projects.enabled=false 14 Nov 13:24:07 - [info] Flows file : /home/pi/.node-red/flows\_raspberrypi.json 14 Nov 13:24:07 - [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.

14 Nov 13:24:07 - [info] Starting flows  
14 Nov 13:24:07 - [info] Started flows  
14 Nov 13:24:07 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)  
14 Nov 13:24:15 - [info] [debug:Temp 1] 31.25  
14 Nov 13:24:15 - [info] [debug:Temp 3] 26.312  
14 Nov 13:24:15 - [info] [debug:Temp 2] 28.812  
14 Nov 13:24:23 - [info] [debug:Temp 1] 31.312  
14 Nov 13:24:23 - [info] [debug:Temp 3] 26.312  
14 Nov 13:24:23 - [info] [debug:Temp 2] 28.875  
14 Nov 13:24:31 - [info] [debug:Temp 1] 31.312  
14 Nov 13:24:31 - [info] [debug:Temp 3] 26.375  
14 Nov 13:24:31 - [info] [debug:Temp 2] 28.875  
14 Nov 13:24:39 - [info] [debug:Temp 1] 31.375  
14 Nov 13:24:39 - [info] [debug:Temp 3] 26.375  
14 Nov 13:24:39 - [info] [debug:Temp 2] 28.875

---

<div class="post-metadata">

**Author:** ![mjdula](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mjdula](https://discourse.nodered.org/u/mjdula)\
**Post date:** [14 November 2019 02:31 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/16 "2019-11-14T02:31:38Z")

</div>

This also shows in the Browser F12 elements. "[Deprecation] Application Cache is restricted to secure contexts. Please consider migrating your application to HTTPS, and eventually shifting over to Service Workers. See [https://goo.gl/rStTGz](https://goo.gl/rStTGz) for more details"

---

<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:** [14 November 2019 08:07 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/17 "2019-11-14T08:07:27Z")

</div>

What is the exact symptom you are seeing now? Please try accessing via a browser not running on the Pi. Part of the problem may be that the browser is overloading the Pi (what model is it?).

---

<div class="post-metadata">

**Author:** ![mjdula](https://avatars.discourse-cdn.com/v4/letter/m/f4b2a3/32.png) [@mjdula](https://discourse.nodered.org/u/mjdula)\
**Post date:** [14 November 2019 22:51 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/18 "2019-11-14T22:51:49Z")

</div>

My symptoms are that the editor takes very long to load and deploy. The dashboard has 3 guages in it and will not load at all. I'm logging in using another pc and browser on the network. I have a pi 3 b+ and also pi zero w.

Can anyone tell me what the difference is when I run sudo-node-red compared to node-red-start. When run sudo-node-red the editor is lightening fast.

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [15 November 2019 06:45 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/19 "2019-11-15T06:45:49Z")

</div>

> My symptoms are that the editor takes very long to load and deploy.

How do you deploy ? If you only deploy the flows that have changed, it will speed up significantly.

 ![33](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/2/2a262aaabcb02d94d2ffb99232897ccb7a6b749e.jpeg)

---

<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:** [15 November 2019 07:16 UTC](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673/20 "2019-11-15T07:16:18Z")

</div>

In a terminal on the node red machine run `top`and I suspect you will find that something is hogging the processor. If so then if you are using mqtt then stop the mqtt server, if that fixes it then possibly you have an mqtt loop.  
As to running `sudo node-red` (I presume you meant that, not `sudo-node-red`) does that run the same flows file? You can see that in the log after starting it.  
If still no joy, post the log you get when starting node red.

**[edit]** Sorry, I was on the phone and didn't notice which thread this is in. The symptom you describe is not the original symptom where it was saying there were no dashboard nodes. You have already posted the log so no need to do that again.

[Next page](https://discourse.nodered.org/t/node-red-gui-wont-load-after-update/16673.md?page=2)