# Messed up dashboard layout

**URL:** <https://discourse.nodered.org/t/messed-up-dashboard-layout/95824>\
**Category:** Dashboard\
**Tags:** node-red-dashboard, dashboard-2\
**Created:** [6 March 2025 10:55 UTC](https://discourse.nodered.org/t/messed-up-dashboard-layout/95824 "2025-03-06T10:55:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![MichelDeMeester](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@MichelDeMeester](https://discourse.nodered.org/u/MichelDeMeester)\
**Post date:** [6 March 2025 10:55 UTC](https://discourse.nodered.org/t/messed-up-dashboard-layout/95824/1 "2025-03-06T10:55:30Z")

</div>

Hello All,

Sorry for writing in "Bad English".

I have 2 flows with a "messed up dashboard", they were just working fine till now.  
One Node Red is running locally on a Raspberry Pi, the other is running on a free Ubuntu instance on the Google free tier platform.

Some Ideas?

I added 2 screenshots.

 ![NoderRed01](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/7/d7d92e1369bd42ce7f308ae469cd098a3a515245.jpeg)  
 ![NoderRed02](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/f/dfe458f54748ad2aa60ae72cdf31272618f63557.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:** [6 March 2025 13:15 UTC](https://discourse.nodered.org/t/messed-up-dashboard-layout/95824/2 "2025-03-06T13:15:31Z")

</div>

Welcome to the forum @MichelDeMeester

Do you mean you have two separate systems that were working, then suddenly they are not working, but you did nothing to them that could have caused it?

---

<div class="post-metadata">

**Author:** ![MichelDeMeester](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@MichelDeMeester](https://discourse.nodered.org/u/MichelDeMeester)\
**Post date:** [6 March 2025 13:50 UTC](https://discourse.nodered.org/t/messed-up-dashboard-layout/95824/3 "2025-03-06T13:50:27Z")

</div>

Hello Colin,

Yes indeed, I used several browsers to test including android phone, everywhere this strange behavior.  
The node red running on the Google VM Ubuntu instance, I was able to solve the problem by restarting the node red service (systemctl restart node-red).  
The node red, running local in my network (used for testing flows before publish them) on a RPI is still producing the scattered dashboard, even after rebooting.  
It seems that the complete link to the mgs.payload is displayed instead of the values.

Thanks for thinking along  
Michel

---

<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:** [6 March 2025 15:25 UTC](https://discourse.nodered.org/t/messed-up-dashboard-layout/95824/4 "2025-03-06T15:25:36Z")

</div>

Assuming that you installed node red using the recommended install script, then stop and restart node-red using  
`node-red-stop`  
`node-red-start`  
Note the dashes, it is not `node-red start`, and copy/paste the full startup log here please, copy/paste, not a screenshot.

---

<div class="post-metadata">

**Author:** ![MichelDeMeester](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@MichelDeMeester](https://discourse.nodered.org/u/MichelDeMeester)\
**Post date:** [7 March 2025 06:47 UTC](https://discourse.nodered.org/t/messed-up-dashboard-layout/95824/5 "2025-03-07T06:47:26Z")

</div>

Hi Colin,

Yesterday, I updated node-red on the RPI using:  
bash \<(curl -sL [https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered](https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered))

After updating, I wasn't even able to connect to the server Node-red server anymore.

This morning, stopping and starting node-red solved the problem (the dashboard looks fine again) and gave me this output:

```auto
Start Node-RED

Once Node-RED has started, point a browser at http://10.99.98.11: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

Starting as a systemd service.
Started Node-RED graphical event wiring tool.
7 Mar 07:34:53 - [info]
Welcome to Node-RED
===================
7 Mar 07:34:53 - [info] Node-RED version: v4.0.9
7 Mar 07:34:53 - [info] Node.js version: v18.17.1
7 Mar 07:34:53 - [info] Linux 6.1.21-v7+ arm LE
7 Mar 07:34:57 - [info] Loading palette nodes
7 Mar 07:35:02 - [info] Dashboard version 3.5.0 started at /ui
7 Mar 07:35:06 - [info] Settings file : /home/michel/.node-red/settings.js
7 Mar 07:35:06 - [info] Context store : 'default' [module=memory]
7 Mar 07:35:06 - [info] User directory : /home/michel/.node-red
7 Mar 07:35:06 - [warn] Projects disabled : editorTheme.projects.enabled=false
7 Mar 07:35:06 - [info] Flows file : /home/michel/.node-red/flows.json
7 Mar 07:35:06 - [info] Server now running at http://127.0.0.1:1880/
7 Mar 07:35:06 - [warn] Using unencrypted credentials
7 Mar 07:35:06 - [info] Starting flows
7 Mar 07:35:07 - [info] Started flows
7 Mar 07:35:08 - [info] [mqtt-broker:la66-usb-rangetest] Connected to broker: mq tt://eu1.cloud.thethings.network:1883
7 Mar 07:35:08 - [info] [mqtt-broker:jff-garagedoor] Connected to broker: mqtt:/ /eu1.cloud.thethings.network:1883

```

Thanks for helping me solving the problem,  
Michel

---

<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:** [6 April 2025 06:47 UTC](https://discourse.nodered.org/t/messed-up-dashboard-layout/95824/6 "2025-04-06T06:47:47Z")

</div>

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