# Fatal error: cannot acces dashboard
**URL:** https://discourse.nodered.org/t/fatal-error-cannot-acces-dashboard/79893
**Category:** General
**Created:** [18 July 2023 03:00 UTC](https://discourse.nodered.org/t/fatal-error-cannot-acces-dashboard/79893 "2023-07-18T03:00:36Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@Observatory\_Gromme](https://discourse.nodered.org/u/Observatory_Gromme)
#### Post date: [18 July 2023 03:00 UTC](https://discourse.nodered.org/t/fatal-error-cannot-acces-dashboard/79893/1 "2023-07-18T03:00:36Z")
Dear All,
I was working with my node-red application and installing an old flow with out the palettes installed.
When installing some philips Hue nodes suddenly node-red crashed and can not start up again.
Got en error from PM2 log:
`Api Error: Unexpected response status; 404`
` at requireStatusCode200 (/home/MASTERM09/.node-red/node_modules/node-hue-api/hue-api/httpPromise.js:100:15)`
` at _fulfilled (/home/MASTERM09/.node-red/node_modules/q/q.js:787:54)`
` at /home/MASTERM09/.node-red/node_modules/q/q.js:816:30`
` at Promise.promise.promiseDispatch (/home/MASTERM09/.node-red/node_modules/q/q.js:749:13)`
` at /home/MASTERM09/.node-red/node_modules/q/q.js:557:44`
` at flush (/home/MASTERM09/.node-red/node_modules/q/q.js:108:17)`
` at process.processTicksAndRejections (node:internal/process/task_queues:77:11)`
What is my solution? I can not access node-red any more for the moment.
Thank you.
---
### Author:  [@bakman2](https://discourse.nodered.org/u/bakman2)
#### Post date: [18 July 2023 06:35 UTC](https://discourse.nodered.org/t/fatal-error-cannot-acces-dashboard/79893/2 "2023-07-18T06:35:13Z")
you can use `node-red --safe` it will start node-red without starting the flows, then you can modify the flows (remove the hue nodes) and deploy
---
### Author:  [@edje11](https://discourse.nodered.org/u/edje11)
#### Post date: [18 July 2023 06:37 UTC](https://discourse.nodered.org/t/fatal-error-cannot-acces-dashboard/79893/3 "2023-07-18T06:37:58Z")
Start node red up with the safe option `node-red --safe`
Now you can remove the nodes that gives you problems.
---
### Author:  [@Observatory\_Gromme](https://discourse.nodered.org/u/Observatory_Gromme)
#### Post date: [18 July 2023 22:14 UTC](https://discourse.nodered.org/t/fatal-error-cannot-acces-dashboard/79893/4 "2023-07-18T22:14:29Z")
Thank you, but the program is runned without sudo
so using node-red --save gives me error:
```auto
>
> MASTERM09@OBSGROMMEM09MASTER:~ $ node-red --safe
> 18 Jul 22:11:19 - [info]
>
> Welcome to Node-RED
> ===================
>
> 18 Jul 22:11:19 - [info] Node-RED version: v3.0.2
> 18 Jul 22:11:19 - [info] Node.js version: v20.3.1
> 18 Jul 22:11:19 - [info] Linux 6.1.21-v8+ arm64 LE
> 18 Jul 22:11:19 - [info] Loading palette nodes
> 18 Jul 22:11:24 - [info] Dashboard version 3.5.0 started at /ui
> 18 Jul 22:11:25 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
> 18 Jul 22:11:25 - [info] Settings file : /home/MASTERM09/.node-red/settings.js
> 18 Jul 22:11:25 - [info] Context store : 'default' [module=memory]
> 18 Jul 22:11:25 - [info] User directory : /home/MASTERM09/.node-red
> 18 Jul 22:11:25 - [warn] Projects disabled : editorTheme.projects.enabled=false
> 18 Jul 22:11:25 - [info] Flows file : /home/MASTERM09/.node-red/flows.json
> 18 Jul 22:11:25 - [info] Server now running at http://127.0.0.1:1880/
> 18 Jul 22:11:25 - [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.
> ---------------------------------------------------------------------
>
> 18 Jul 22:11:25 - [info] *****************************************************************
> 18 Jul 22:11:25 - [info] Flows stopped in safe mode. Deploy to start.
> 18 Jul 22:11:25 - [info] *****************************************************************
> 18 Jul 22:11:25 - [red] Uncaught Exception:
> 18 Jul 22:11:25 - [error] Api Error: Unexpected response status; 404
> at requireStatusCode200 (/home/MASTERM09/.node-red/node_modules/node-hue-api/hue-api/httpPromise.js:100:15)
> at _fulfilled (/home/MASTERM09/.node-red/node_modules/q/q.js:787:54)
> at /home/MASTERM09/.node-red/node_modules/q/q.js:816:30
> at Promise.promise.promiseDispatch (/home/MASTERM09/.node-red/node_modules/q/q.js:749:13)
> at /home/MASTERM09/.node-red/node_modules/q/q.js:557:44
> at flush (/home/MASTERM09/.node-red/node_modules/q/q.js:108:17)
> at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
```
---
### Author:  [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)
#### Post date: [18 July 2023 22:55 UTC](https://discourse.nodered.org/t/fatal-error-cannot-acces-dashboard/79893/5 "2023-07-18T22:55:09Z")
Which node are you using and how did you install it ?
---
### Author:  [@Observatory\_Gromme](https://discourse.nodered.org/u/Observatory_Gromme)
#### Post date: [18 July 2023 23:12 UTC](https://discourse.nodered.org/t/fatal-error-cannot-acces-dashboard/79893/6 "2023-07-18T23:12:45Z")
Dear, i have node v20.3.1 installed.
I installed node-red with the official install page:
[https://nodered.org/docs/getting-started/raspberrypi](https://nodered.org/docs/getting-started/raspberrypi)
It worked fine for long. But when i entered some "old" flows i got the error.
```auto
> 18 Jul 22:11:25 - [error] Api Error: Unexpected response status; 404
> at requireStatusCode200 (/home/MASTERM09/.node-red/node_modules/node-hue-api/hue-api/httpPromise.js:100:15)
> at _fulfilled (/home/MASTERM09/.node-red/node_modules/q/q.js:787:54)
> at /home/MASTERM09/.node-red/node_modules/q/q.js:816:30
```
wrong API code maybe? I was installing node-red etc on a new computer, and also the Hue brigde etc.
I copied the old flows, but maybe there is the error coming from?
---
### Author:  [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)
#### Post date: [18 July 2023 23:19 UTC](https://discourse.nodered.org/t/fatal-error-cannot-acces-dashboard/79893/7 "2023-07-18T23:19:54Z")
I actually mean the hue node eg is it **node-red-contrib-node-hue**
However for node-red you should be using node 16 or 18, not 20
---
### Author:  [@Observatory\_Gromme](https://discourse.nodered.org/u/Observatory_Gromme)
#### Post date: [15 August 2023 14:47 UTC](https://discourse.nodered.org/t/fatal-error-cannot-acces-dashboard/79893/8 "2023-08-15T14:47:45Z")
Thank you all. I just ended up with reinstalling the version of node red. The problem was the identification code with the Hue Bridge. Everything is working now as expected.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [14 October 2023 14:47 UTC](https://discourse.nodered.org/t/fatal-error-cannot-acces-dashboard/79893/9 "2023-10-14T14:47:47Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.