# Node-red UI problems

**URL:** <https://discourse.nodered.org/t/node-red-ui-problems/1778>\
**Category:** Dashboard\
**Created:** [24 July 2018 10:33 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778 "2018-07-24T10:33:34Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Duncan](https://avatars.discourse-cdn.com/v4/letter/d/ecc23a/32.png) [@Duncan](https://discourse.nodered.org/u/Duncan)\
**Post date:** [24 July 2018 10:33 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778/1 "2018-07-24T10:33:34Z")

</div>

Please help I have been up most of the night getting my node-red server back online. and now I have realized my dashboard has a problem aswell. The UI doesn't work, if you look at the attached screenshot you will see somthing isn't right. at the moment I have removed all ui's, somhow nod red things there is still somthing in use.

 ![ui%20dashboard%20in%20pallet](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/f/f887dea11020a8a19c27749f0998525b26549854.jpg)

---

<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:** [24 July 2018 12:24 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778/2 "2018-07-24T12:24:21Z")

</div>

If you open up the Configuration nodes sidebar tab from the drop-down menu, you should find a `ui_base` config node. Double click on it to open its edit dialog - do _not_ click the button to open the dashboard sidebar, but click the `Delete` button. Then deploy.

Note that if you open the dashboard sidebar it will automatically readd the ui\_base config node - so don't do that until you've sorted out the issue.

The `[object Object]` messages should be actual error messages encountered when loading the node - we've fixed the display of those messages for the next release. For now, yo'ull have to check the node-red log output for the actual errors.

---

<div class="post-metadata">

**Author:** ![Duncan](https://avatars.discourse-cdn.com/v4/letter/d/ecc23a/32.png) [@Duncan](https://discourse.nodered.org/u/Duncan)\
**Post date:** [4 August 2018 14:44 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778/3 "2018-08-04T14:44:31Z")

</div>

Hi, thanks for your answer. my problems are only getting bigger. I still couldn't get the UI working so I tried a fresh installation from backups. I have been the better part of 3 days trying to get a new installation working with an imported node-red flow that was always working perfectly. Node-red is continually starting and stopping. I really don't know were to look. Unfortunatly my whole house is running on the node-red installation.

best regards,  
Duncan.

 ![node-red%20crash](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/5/5f81ba449cfc634eb2b36708c8ef2a75545cfe60.jpg)

---

<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:** [4 August 2018 15:18 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778/4 "2018-08-04T15:18:02Z")

</div>

You are on an older version of NR and Node.js, you may want to run the update script found at:  
[https://nodered.org/docs/hardware/raspberrypi](https://nodered.org/docs/hardware/raspberrypi)

---

<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:** [4 August 2018 16:24 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778/5 "2018-08-04T16:24:11Z")

</div>

Looks like something is running out of memory. The solar edge node (whatever that is???) is throwing an exception and then the gc goes bang. Which causes which needs to be determined.

---

<div class="post-metadata">

**Author:** ![Duncan](https://avatars.discourse-cdn.com/v4/letter/d/ecc23a/32.png) [@Duncan](https://discourse.nodered.org/u/Duncan)\
**Post date:** [11 August 2018 17:48 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778/6 "2018-08-11T17:48:12Z")

</div>

After allot of invested time i managed to narrow the problem down to a modbus node. I had two modbus nodes installed, I think they were using up all memory resources until the pi crashed.

---

<div class="post-metadata">

**Author:** ![shrickus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/shrickus/32/517_2.png) [@shrickus](https://discourse.nodered.org/u/shrickus)\
**Post date:** [29 August 2018 22:21 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778/7 "2018-08-29T22:21:20Z")

</div>

> [@knolleary](#):
>
> The `[object Object]` messages should be actual error messages encountered when loading the node - we've fixed the display of those messages for the next release.

While you are fixing that in the Palette manager (and the red warning triangle confusion), any chance you can update the nodes list open/close symbols?

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/4/4fd69239fffb7113db5cea6547f886fcc61e2293.png)

I know it's a minor thing, but that _clearly_ shows that there are **greater than 54 nodes not supported on Windows** -- or at least that's the way my brain interprets it ;\*)

Might I suggest using the filled black triangles such as those used by the debug panel?  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/0/0549ae0fdaaccf068541be7cca6b064daab01581.png)

---

<div class="post-metadata">

**Author:** ![SwastiBrt](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@SwastiBrt](https://discourse.nodered.org/u/SwastiBrt)\
**Post date:** [12 July 2019 05:54 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778/8 "2019-07-12T05:54:14Z")

</div>

It is confirmation about the version of Node-red on IBM Cloud.

About node-red applications that have been running for a year  
A few days ago all versions of node-red on sydney have been automatically (intentionally) updated to 0.20.7. The original version was 0.18.7.  
It does not occur in other regions.  
What is the cause of this?

---

<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:** [12 July 2019 07:35 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778/9 "2019-07-12T07:35:43Z")

</div>

This is a different issue and not related to the post above. Can you open a new issue (although it sounds like a question for IBM cloud support)

---

<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:** [12 July 2019 08:30 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778/10 "2019-07-12T08:30:59Z")

</div>

If the (or any) cloud instance restarts completely (restages) - it will rebuild itself from the default package.json which is usually pointed to the latest. So obviously at some point they must have had a full reboot of the region.

---

<div class="post-metadata">

**Author:** ![SwastiBrt](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@SwastiBrt](https://discourse.nodered.org/u/SwastiBrt)\
**Post date:** [16 July 2019 00:58 UTC](https://discourse.nodered.org/t/node-red-ui-problems/1778/11 "2019-07-16T00:58:13Z")

</div>

I am sorry to ask different question than discussing in this forum. But very thankful to Mr. Dceejay to answering my question despite of another topic, It helped me a lot.