# Dashboard is not working anymore
**URL:** https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804
**Category:** Dashboard
**Created:** [14 June 2018 08:25 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804 "2018-06-14T08:25:33Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@YT2310](https://discourse.nodered.org/u/YT2310)
#### Post date: [14 June 2018 08:25 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/1 "2018-06-14T08:25:33Z")
Hi community,
First of all: sorry for my english…
i got a Problem with my Dashboard, after i finished programming some Nodes and adding their data to the Dashboard, i shut my raspberry down.
After i reboot it this morning again and wanted to check my Dashboard, it doesn t worked any longer.
There is always this message:
Welcome to the Node-RED Dashboard
Please add some UI nodes to your flow and redeploy.
but i already added some ui Dashboard notes…
could any one help my to fix this Problem?
---
### Author:  [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [14 June 2018 08:41 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/2 "2018-06-14T08:41:36Z")
It would be useful to see the log that Node-RED prints when you start it.
Also have you installed any other nodes that include the word “dashboard”? If you have these unfortunately stop the node-red-dashboard from working. You should delete them and then restart Node-RED
---
### Author:  [@YT2310](https://discourse.nodered.org/u/YT2310)
#### Post date: [14 June 2018 08:52 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/3 "2018-06-14T08:52:59Z")
here is what node red prints:
> **Node-Red start**
>
> Start Node-RED
>
> Once Node-RED has started, point a browser at [http://192.168.1.44:1880](http://192.168.1.44: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. Started Node-RED graphical event wiring tool. 14 Jun 10:42:53 - [info] Welcome to Node-RED
>
> ## 14 Jun 10:42:53 - [info] Node-RED version: v0.18.6 14 Jun 10:42:53 - [info] Node.js version: v8.11.2 14 Jun 10:42:53 - [info] Linux 4.14.34-v7+ arm LE 14 Jun 10:42:54 - [info] Loading palette nodes 14 Jun 10:42:59 - [info] Dashboard version 2.9.4 started at /ui 14 Jun 10:43:00 - [warn] ------------------------------------------------------ 14 Jun 10:43:00 - [warn] [node-red-bluemix-nodes/tcp] ‘tcp request’ already registered by module node-red 14 Jun 10:43:00 - [warn] [node-red-bluemix-nodes/udp] ‘udp out’ already registered by module node-red 14 Jun 10:43:00 - [warn] ------------------------------------------------------ 14 Jun 10:43:00 - [info] Settings file : /home/pi/.node-red/settings.js 14 Jun 10:43:00 - [info] User directory : /home/pi/.node-red 14 Jun 10:43:00 - [warn] Projects disabled : editorTheme.projects.enabled=false 14 Jun 10:43:00 - [info] Flows file : /home/pi/.node-red/flows\_raspberrypi.json 14 Jun 10:43:00 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/) 14 Jun 10:43:00 - [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 Jun 10:43:01 - [info] Starting flows
> TypeError: Cannot read property ‘id’ of undefined
> at createSubflow (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/Flow.js:362:61)
> at Flow.start (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/Flow.js:97:41)
> at start (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/index.js:327:29)
> at tryCatchReject (/usr/lib/node\_modules/node-red/node\_modules/when/lib/makePromise.js:845:30)
> at runContinuation1 (/usr/lib/node\_modules/node-red/node\_modules/when/lib/makePromise.js:804:4)
> at Fulfilled.when (/usr/lib/node\_modules/node-red/node\_modules/when/lib/makePromise.js:592:4)
> at Pending.run (/usr/lib/node\_modules/node-red/node\_modules/when/lib/makePromise.js:483:13)
> at Scheduler.\_drain (/usr/lib/node\_modules/node-red/node\_modules/when/lib/Scheduler.js:62:19)
> at Scheduler.drain (/usr/lib/node\_modules/node-red/node\_modules/when/lib/Scheduler.js:27:9)
> at \_combinedTickCallback (internal/process/next\_tick.js:131:7)
> at process.\_tickCallback (internal/process/next\_tick.js:180:9)
> 14 Jun 10:43:02 - [info] Started flows
> 14 Jun 10:43:03 - [info] [sqlitedb:6573ca80.1e0d34] opened /tmp/sqlite ok
> 14 Jun 10:43:36 - [info] Stopping flows
> 14 Jun 10:43:36 - [info] Stopped flows
> 14 Jun 10:43:36 - [info] Starting flows
> TypeError: Cannot read property ‘id’ of undefined
> at createSubflow (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/Flow.js:362:61)
> at Flow.start (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/Flow.js:97:41)
> at start (/usr/lib/node\_modules/node-red/red/runtime/nodes/flows/index.js:327:29)
> at /usr/lib/node\_modules/node-red/red/runtime/nodes/flows/index.js:164:21
> at tryCatchReject (/usr/lib/node\_modules/node-red/node\_modules/when/lib/makePromise.js:845:30)
> at runContinuation1 (/usr/lib/node\_modules/node-red/node\_modules/when/lib/makePromise.js:804:4)
> at Fulfilled.when (/usr/lib/node\_modules/node-red/node\_modules/when/lib/makePromise.js:592:4)
> at Pending.run (/usr/lib/node\_modules/node-red/node\_modules/when/lib/makePromise.js:483:13)
> at Scheduler.\_drain (/usr/lib/node\_modules/node-red/node\_modules/when/lib/Scheduler.js:62:19)
> at Scheduler.drain (/usr/lib/node\_modules/node-red/node\_modules/when/lib/Scheduler.js:27:9)
> at \_combinedTickCallback (internal/process/next\_tick.js:131:7)
> at process.\_tickCallback (internal/process/next\_tick.js:180:9)
> 14 Jun 10:43:38 - [info] Started flows
i don t have any other nodes including the word Dashboard…
---
### Author:  [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [14 June 2018 09:08 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/4 "2018-06-14T09:08:34Z")
Do you need the following nodes that you have installed?
> [@YT2310](#):
>
> node-red-bluemix-nodes
They are for use in Bluemix but you have it installed on a raspberry pi. Try deleting them and restarting node-red.
---
### Author:  [@YT2310](https://discourse.nodered.org/u/YT2310)
#### Post date: [14 June 2018 09:47 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/5 "2018-06-14T09:47:28Z")
i already tried to delet them but node red says they are in use, what they defenetly aren t…
---
### Author:  [@YT2310](https://discourse.nodered.org/u/YT2310)
#### Post date: [14 June 2018 09:47 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/6 "2018-06-14T09:47:51Z")
---
### Author:  [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [14 June 2018 10:02 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/7 "2018-06-14T10:02:49Z")
So that suggests you are using the mongoldb nodes. If you are definitely not…
In a terminal
`node-red-stop`
`cd ~/.node-red`
and then
`npm uninstall node-red-bluemix-nodes`
then restart Node-RED
---
### Author:  [@YT2310](https://discourse.nodered.org/u/YT2310)
#### Post date: [14 June 2018 11:08 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/8 "2018-06-14T11:08:53Z")
okay now the terminal says:
> **picture**
>
> 
but i defenitly had no node in my flow which is called mongoDB
---
### Author:  [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [14 June 2018 11:14 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/9 "2018-06-14T11:14:15Z")
If you look at the menubar in Node-RED there is a “Search flows” option and see if you can find it
Otherwise look at “Configuration nodes”
---
### Author:  [@YT2310](https://discourse.nodered.org/u/YT2310)
#### Post date: [14 June 2018 11:20 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/10 "2018-06-14T11:20:04Z")
yes thank u i fix it now 🙂
---
### Author:  [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [14 June 2018 11:21 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/11 "2018-06-14T11:21:43Z")
Which one was it? A node or a configuration node?
---
### Author:  [@YT2310](https://discourse.nodered.org/u/YT2310)
#### Post date: [14 June 2018 12:20 UTC](https://discourse.nodered.org/t/dashboard-is-not-working-anymore/804/12 "2018-06-14T12:20:20Z")
probably it was a configuration node which blocked my Dashboard ui. So i deleted all background nodes and stuff i don’t needed any more and now it works.
I hope it is still working tomorrow