Another 'Cannot GET /ui'

I have very limited experience with RPi and Linux, and usually depend on others to create scripts or 'how to's ' on the web to get things up and running.

Firstly, let me describe what I'm dealing with:-

  • RPi 3 (updated and fully upgraded a day or so ago),
  • NPM version 10.9.2,
  • Node-RED version v4.0.9,
  • Node.js v23.11.0, Linux 6.12.20+rpt-rpi-v8 arm64 LE

Node-RED (version unrecorded) used to work on this RPi, along with the associated UI.
Since the upgrade, Node-RED is working (sensor data coming from a WiFi sensor via MQTT broker is being received and showing in the relevant debug nodes).
Incidentally, the first thing I did when I got Node-RED working this time, I imported a saved flow from the previous incarnation, but most if not all of the nodes were not known, and I could not deploy. I deleted all of the unknown nodes and flows and created a new flow and was able to deploy successfully (with the result described above).
But ..... I cannot display the ui (as I did previously) - I get the venerable "Cannot GET /ui'.
Is someone able to guide me through a troubleshooting session? (its disappointing the response 'Cannot GET /ui' doesn't include any supporting information like why?
If in the end I have to 'rebuild' Node-RED, can this be done without affecting other applications/programs?
Thank you in anticipation of some help.
Cheers, Steve from Oz

Welcome to the forum.

That is not a supported version of node.js, though that is probably not this specific problem.

If you want to do that then I suggest running the recommended node-red install script, adding the parameter --node20 on the end which fill downgrade you to a supported nodejs version.

If you want to try and get what you have running then show us what you see when you start node-red in a command window.

If you import a flow and it shows unknown nodes, those nodes are not installed.
The dashboard (node-red-dashboard) is not a core component of Node-red, you have to install it via the hamburger menu | Manage Palette.

Starting with a fresh installation might be a good time to consider switching to an alternative dashboard since node-red-dashboard is deprecated.
Available alternatives are Uibuilder and @flowfuse/node-red-dashboard.
Unfortunately it's not a pain free transition.

Hi, Thanks for your input.
When I read your post and saw one of the recommendations was '@flowfuse/node-red-dashboard' I thought 'I recognise that!' and checked my current Node-RED and I indeed have that installed. I wonder if it could be a part of the problem??

In the mean time, I'll use Colins recommendation and do the install with --node20 and see what happens.

Cheers

The flowfuse dashboard is at :1880/dashboard not 1880:/ui

You can have both node-red-dashboard and @flowfuse/node-red-dashboard installed without any ill effects. Uibuilder too I believe.

I hesitate to call @flowfuse/node-red-dashboard a recommendation! :upside_down_face:

Hi,
Well, I tried :1880/dashboard, and I could see the output of the sensors doing their thing. Looks like I'll have to study how to make the screen look like it was in the /ui (originally).
Where can I find any doco on the @flowfuse/node-red-dashboard?
Once again, thank you for such a valuable and quick support.
Cheers

Hi, Sorry, I was so excited to get the dashboard working, I should have paid more attention and realise the @flowfuse/node-red-dashboard was in fact Node-RED Dashboard v2.0 !! And I know when to find all of the relevant details. So, I'm in for a long night!!!

PS, am I able to recover the nodes/flows that were save in the previous dashboard??
Cheers

If you import a flow and get "unknown nodes", just use Manage Palette to install the missing components. Nothing should be lost. Edit: - except you will have to re-enter any saved credentials.