Page 1 of 1

Node red error. Don´t want launch

Posted: 17 Mar 2025, 11:10
by sfdiaz
When trying to launch Node red through the revpi status screen I get the following message 'Node-RED service not ready yet ... please retry ...' The star icon appears green, but every time you click on it the same error appears.

We have already tried to remove the "Group=pi" line and reboot but the result is the same.

if I try to access through the terminal (node-red -v), it does access me.

Welcome to Node-RED
===================

17 Mar 11:04:40 - [info] Node-RED version: v3.0.2
17 Mar 11:04:40 - [info] Node.js version: v16.19.1
17 Mar 11:04:40 - [info] Linux 4.19.95-rt38-v7 arm LE
17 Mar 11:04:42 - [info] Loading palette nodes
17 Mar 11:04:51 - [info] Settings file : /home/pi/.node-red/settings.js
17 Mar 11:04:51 - [info] Context store : 'default' [module=memory]
17 Mar 11:04:51 - [info] User directory : /home/pi/.node-red
17 Mar 11:04:51 - [warn] Projects disabled : editorTheme.projects.enabled=false
17 Mar 11:04:51 - [info] Flows file : /home/pi/.node-red/flows.json
(node:10780) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
(Use `node --trace-warnings ...` to show where the warning was created)
17 Mar 11:04:51 - [info] Server now running at http://127.0.0.1:1880/
17 Mar 11:04:51 - [warn] Using unencrypted credentials
17 Mar 11:04:52 - [info] Starting flows
....

17 Mar 11:04:55 - [red] Uncaught Exception:
17 Mar 11:04:55 - [error] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "AxiosError: Request failed with status code 403".

someone can help me, I have been unable to access for several days.

Thanks

Re: Node red error. Don´t want launch

Posted: 17 Mar 2025, 11:43
by nicolaiB
[error] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "AxiosError: Request failed with status code 403".
There seems to be something which breaks your NodeRed. Try with an empty flow and disable unnecessary nodes. This error can also occur if you use nodes which require a more recent nodejs version.

Nicolai

Re: Node red error. Don´t want launch

Posted: 17 Mar 2025, 12:11
by sfdiaz
Hi Nicolai,

Thank you very much for your answer

How can I deactivate the nodes through terminal?
Is there any way to copy all the flows through terminal and delete them to add them again one by one?

Kind regards

Re: Node red error. Don´t want launch

Posted: 17 Mar 2025, 15:35
by RevPiModIO
Can you try to access Node-RED directly?

Node-RED should run on https://revpiXXXXX.local:41880/. It's exactly the same URL as RevPi status, but on port 41880. It could be that the dialog in RevPi status has an error and Node-RED is actually running.

Re: Node red error. Don´t want launch

Posted: 17 Mar 2025, 20:13
by sfdiaz
Hi,

I enter the ip address of the rev pi followed by :41880 and it gives error, i have also tried with:1880 which was the one i used to enter before and it also gives error.

Re: Node red error. Don´t want launch

Posted: 18 Mar 2025, 08:00
by RevPiModIO
Would it be possible for you to flash the RevPi with our Bookworm image?

Node-RED is already installed in the default image, including the GUI. If you do not need the GUI, you can use the Lite image and install Node-RED in the cockpit (web configuration). The version of Node-RED is there v4 and is regularly updated via package updates.

https://revolutionpi.com/en/support/downloads#c1069

Re: Node red error. Don´t want launch

Posted: 18 Mar 2025, 14:06
by sfdiaz
we always work with the graphical interface, in fact I don't know how we can delete nodes and flows without accessing the graphical interface.