Keep getting error message "Cannot GET /dashboard" when trying to start Node-RED Dashboard 2.0

Today I took my first steps with Node-RED on my Victron system. Node-RED itself installed just fine and it seems to work ok. However, I can not get the Dashboard function to work. I keep getting the error message “Cannot GET /dashboard”.

Apparently others also have this problem, found some possible solutions on the internet. However none of these work in my case for some reason. There is a reference to the issue in this Node-RED for dummies topic, but I can not access the other topic that the author refers to because it is private or does not exist anymore.

All help would be much appreciated.

I don’t remember the details but thanks to this forum, I think I used a couple of dashboard 2.0 (the latest at the time) fake/dummy text nodes that do absolutely nothing. I didn’t have to install the nodes separately or do anything extra.

Thanks, tried that as well. Don’t know if the flow type matters, but I made a couple of very basic flows with some inject/delay/debug nodes. Same result.

Also noticed that my Dashboard 2.0 sidebar seems to be missing:

According to the Node-RED dashboard getting started guide, there should at least be some layout settings there:

Very strange. Re-installed the dashboard package at least three times so far (incl. Cerbo reboots) but nothing helps.

Dash 2 needs to be configured initially.
Can confirm it is working fine, it is all I use and version updates have not broken it.
You have likely missed a setup step to initialise it.

I had the same problem. When I logged in with 192.168.8.xxx:1881/Dashboard/Page1 the response was Cannot get /Dashboard. When I enter the address as https://192.168.8.xxx:1881/dashboard/page1 then the dashboard loads correctly. I am using Mac OS and Safari so it may be different with another operating system or browser.

Ok, thanks. Not sure what I missed then, executed the Node-RED installation steps mentioned in the Victron guide. According to this guide (but also the generic Node-RED one), installing the dashboard only requires the installation of the Flowfuse Dashboard 2.0 package using the Manage Palette menu.

There are some configuration files, but the Victron guide states that “the vast majority of systems using Node-RED will not, and should not (!), have to modify any of the files here described”. So I didn’t touch those.

I get the same error message when trying to access the dashboard via the VRM Portal and locally with the Cerbo IP address on port 1881.

Good point. Tried this as well, but unfortunately it doesn’t work for me.

Do you have a flow operating? If there are no deployed flows then dashboard does not operate. If there is no flows yet try putting a flow of battery voltage from whatever Victron source is available link that with say the Dashboard 2.0 Text Input Node, deploy and then view the dashboard from within the node red edit screen.

Yes, I have one flow that just sends some text to a debug node and another that reads my battery’s SoC. These work as expected.

@PhilipZetten sorry for the delayed reply. Account issues, I’m temporarily using a Win 10 laptop.

It appears I missed something in your posts. If you don’t see nodes, how are you then able to create flows?

No problem at all.

Node-RED works fine as far as I can see, but I just started using it so I can’t be sure. The problem is with the dashboard function, that doesn’t work at all. Every time I try to start it (either from the VRM Portal or by accessing the local IP address) I get the error message “Cannot GET /dashboard”.

Tried all suggestions given above by our Community colleagues.

On my NR workspace, I see Dashboard 2.0 nodes, among others, including Victron nodes. Do you see the form and text input nodes, as in the screenshot? Ignore the nodes on the right, that is the useless stuff.

Yes, I have a similar workspace:

Have you sent any data to the dashboard? It won’t populate without it.
Url is also (if configured correctly)

https://venus.local:1881/dashboard/page1

Well, that was indeed the problem. Very logical once you know it. My reasoning was that the dashboard function can be started right after installing it, but that’s not the case.

Thank you very much !