Nodered update 2.2.3-2 keeps repeating

I am running node red on a raspberry pi 4b on a debian installation. For the last couple weeks i keep getting a notice through the usual update mechanism to update node red to 2.2.3-2. If I run the update, it reports successful but reappears within 15 seconds. I have node red installed on my machine but have not used it. I did start it to see if that resolved the issue but no change.

Why do you have it installed then? Can you uninstall it?
What is the usual update mechanism? (I have Raspberries with RPiOS but I've never seen an update notice)

The current version of Node-red is 3.0.2. If you run the installation script that's the version you will get, though it's just possible you will have to add a parameter --node16

It came with the Debian installation. I understand that Debian curates the features they include in their distribution and I trust them to include the components most useful to their target community withing a modest footprint.Therefore, while I haven't used it to date, I would if at all possible prefer to leave it in place.

When I launch Node red i get a header that identifies it as version 2.2.3, which tells me it is installed and functioning. Is there an issue with my installation of node red or the update script?

Below is the log file that displays at startup

25 Sep 09:25:59 - [info] Node-RED version: v2.2.3
25 Sep 09:25:59 - [info] Node.js version: v12.22.12
25 Sep 09:25:59 - [info] Linux 5.15.61-v7l+ arm LE
25 Sep 09:26:00 - [info] Loading palette nodes
25 Sep 09:26:03 - [info] Settings file : /home/pi/.node-red/settings.js
25 Sep 09:26:03 - [info] Context store : 'default' [module=memory]
25 Sep 09:26:03 - [info] User directory : /home/pi/.node-red
25 Sep 09:26:03 - [warn] Projects disabled : editorTheme.projects.enabled=false
25 Sep 09:26:03 - [info] Flows file : /home/pi/.node-red/flows.json
25 Sep 09:26:03 - [info] Creating new flow file
25 Sep 09:26:03 - [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.

25 Sep 09:26:03 - [warn] Encrypted credentials not found
25 Sep 09:26:03 - [info] Starting flows
25 Sep 09:26:03 - [info] Started flows
25 Sep 09:26:03 - [info] Server now running at

2.2.3 is the latest available via the apt repository.

If you want to upgrade to 3.x, you will need to use the script we provide in the docs.

Either way it is a Debian issue, not a node-red issue.

The version of node.js packaged by Debian is (probably) 12. The update may fail because a more up-to-date version of node-red requires at least v14.

Simplest if you don't want to uninstall is to run the NR installation script.

OK, so I am trying to uninstall it. In another thread on this forum I saw instructions to run the following commands in the console window;

sudo npm -g remove node-red
sudo npm -g remove node-red-admin
rm -R ~/.node-red

Ran the 3 commends in the order given with no change. Am i missing something?

And, BTW, I started my inquiries on the RPI forum. They sent me here.
If I cannot uninstall completely, is there a way to at least stop the update mechanism from repeatedly offering the update? I have begun ignoring the notices and fear I might miss a critical update .

You will have to remove it via apt since that is what is telling you there is an update.

As others have pointed out already for Debian there is an official script that will install the correct version of node.js and the latest version of node red.

sudo apt remove nodered
or if that says unable to locate package then try
sudo apt remove node-red

The first command given above removed the app and deleted the update request. Thanks for solving my problem.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.