Manage Palette Is Missing

Hi, i'm new in node-red.

a few days ago i want to install some palette but can't find the option "Manage Palette" on the menu.

does anybody know how to solved the problem ?
thank you

Check the node-red log when it starts. It will tell you if/why the manage palette option is unavailable. Most likely - it cannot find the npm command on your path.

here is my node-red log,
the npm is too old

3 Jun 16:29:18 - [info] Node-RED version: v0.20.5
3 Jun 16:29:18 - [info] Node.js version: v8.11.1
3 Jun 16:29:18 - [info] Linux 4.19.42-v7+ arm LE
3 Jun 16:29:21 - [info] Palette editor disabled : npm version too old. Requires npm >= 3.x
3 Jun 16:29:21 - [info] Loading palette nodes
3 Jun 16:29:26 - [info] Dashboard version 2.13.2 started at /ui
3 Jun 16:29:26 - [warn] ------------------------------------------------------
3 Jun 16:29:26 - [warn] [node-red-contrib-opcua/OpcUa-Item] Error: Cannot find module 'chalk'
3 Jun 16:29:26 - [warn] [node-red-contrib-opcua/OpcUa-Client] Error: Cannot find module 'chalk'
3 Jun 16:29:26 - [warn] [node-red-contrib-opcua/OpcUa-Browser] Error: Cannot find module 'chalk'
3 Jun 16:29:26 - [warn] [node-red-contrib-opcua/OpcUa-Server] Error: Cannot find module 'chalk'
3 Jun 16:29:26 - [warn] [node-red-contrib-opcua/OpcUa-Event] Error: Cannot find module 'chalk'
3 Jun 16:29:26 - [warn] ------------------------------------------------------
3 Jun 16:29:26 - [info] Settings file : /home/pi/.node-red/settings.js
3 Jun 16:29:26 - [info] Context store : 'default' [module=memory]
3 Jun 16:29:26 - [info] User directory : /home/pi/.node-red
3 Jun 16:29:26 - [warn] Projects disabled : editorTheme.projects.enabled=false
3 Jun 16:29:26 - [info] Flows file : /home/pi/.node-red/log
3 Jun 16:29:26 - [info] Creating new flow file
3 Jun 16:29:26 - [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.

3 Jun 16:29:26 - [info] Starting flows
3 Jun 16:29:26 - [info] Started flows
3 Jun 16:29:26 - [error] Unable to listen on http://127.0.0.1:1880/
3 Jun 16:29:26 - [error] Error: port in use

As you are on a pi, try running the upgrade script on the raspberry pi page in the docs.

yes i'am. i'v tried this command

npm install npm@latest -g

but it didn't work, still version of 2.x

From https://nodered.org/docs/hardware/raspberrypi

Install / Upgrade

If you have a version of Raspbian, or other Debian based install, such as Ubuntu, or Diet-Pi, that doesn’t have Node-RED already installed, you can install or upgrade using the Node-RED upgrade script command

bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)
On really minimal Debian installs you may need to run sudo apt-get install build-essential before running the script so that the serialport builds and installs OK. This is optional.
1 Like

ukmoose, thank you very much. it worked :smile:

but all of my node is gone

What do you mean?

All your flows have disappeared?
Or all the nodes you had installed have disappeared?

Both of it. Its just come to default again, like we install it for the first time

When you last posted the log you had started node-red as:

node-red log

which has created a new flows file named log, your old flows file will be in your .node-red directory.

cd into that directory and list all the files

a

here is what i got. it seems like my files not in it

can my files back again ?

Running the command will not have deleted your flows files.

So your need to explain all the steps you did
(the unix command history might help)

Also please post the startup log younnow get.

first i follow the instruction to type this command:
bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)

then it loading to upgrade, but the process i see tell that it remove the old npm and install the new one. after it finish i check the version of npm (npm -v), it upgraded to 6.x version.

i check the node-red, and all of my flow are gone.

here is my node-red log

pi@raspberrypi:~ $ node-red log
6 Jun 01:42:29 - [info]

Welcome to Node-RED

6 Jun 01:42:29 - [info] Node-RED version: v0.20.5
6 Jun 01:42:29 - [info] Node.js version: v10.16.0
6 Jun 01:42:29 - [info] Linux 4.19.42-v7+ arm LE
6 Jun 01:42:30 - [info] Loading palette nodes
6 Jun 01:42:34 - [info] Dashboard version 2.13.2 started at /ui
6 Jun 01:42:34 - [warn] ------------------------------------------------------
6 Jun 01:42:34 - [warn] [node-red-contrib-opcua/OpcUa-Item] Error: Cannot find module 'chalk'
6 Jun 01:42:34 - [warn] [node-red-contrib-opcua/OpcUa-Client] Error: Cannot find module 'chalk'
6 Jun 01:42:34 - [warn] [node-red-contrib-opcua/OpcUa-Browser] Error: Cannot find module 'chalk'
6 Jun 01:42:34 - [warn] [node-red-contrib-opcua/OpcUa-Server] Error: Cannot find module 'chalk'
6 Jun 01:42:34 - [warn] [node-red-contrib-opcua/OpcUa-Event] Error: Cannot find module 'chalk'
6 Jun 01:42:34 - [warn] ------------------------------------------------------
6 Jun 01:42:34 - [info] Settings file : /home/pi/.node-red/settings.js
6 Jun 01:42:34 - [info] Context store : 'default' [module=memory]
6 Jun 01:42:34 - [info] User directory : /home/pi/.node-red
6 Jun 01:42:34 - [warn] Projects disabled : editorTheme.projects.enabled=false
6 Jun 01:42:34 - [info] Flows file : /home/pi/.node-red/log
6 Jun 01:42:34 - [info] Creating new flow file
6 Jun 01:42:34 - [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.

6 Jun 01:42:34 - [info] Starting flows
6 Jun 01:42:34 - [info] Started flows
6 Jun 01:42:35 - [error] Unable to listen on http://127.0.0.1:1880/
6 Jun 01:42:35 - [error] Error: port in use

pi@raspberrypi:~ $ node-red-log

6 Jun 01:34:01 - [info] [mqtt-broker:lokal] Connected to broker: mqtt://127.0.0.1:1883
6 Jun 01:34:25 - [info] Stopping flows
6 Jun 01:34:25 - [info] [mqtt-broker:lokal] Disconnected from broker: mqtt://127.0.0.1:1883
6 Jun 01:34:25 - [info] Stopped flows
6 Jun 01:34:25 - [info] Starting flows
6 Jun 01:34:25 - [info] Started flows
6 Jun 01:34:25 - [info] [mqtt-broker:lokal] Connected to broker: mqtt://127.0.0.1:1883
6 Jun 01:34:41 - [info] Stopping flows
6 Jun 01:34:41 - [info] [mqtt-broker:lokal] Disconnected from broker: mqtt://127.0.0.1:1883
6 Jun 01:34:41 - [info] Stopped flows
6 Jun 01:34:41 - [info] Starting flows
6 Jun 01:34:41 - [info] Started flows
6 Jun 01:34:41 - [info] [mqtt-broker:lokal] Connected to broker: mqtt://127.0.0.1:1883
6 Jun 01:35:15 - [info] Stopping flows
6 Jun 01:35:15 - [info] [mqtt-broker:lokal] Disconnected from broker: mqtt://127.0.0.1:1883
6 Jun 01:35:15 - [info] Stopped flows
6 Jun 01:35:15 - [info] Starting flows
6 Jun 01:35:15 - [info] Started flows
6 Jun 01:35:15 - [info] [mqtt-broker:lokal] Connected to broker: mqtt://127.0.0.1:1883
6 Jun 01:35:28 - [info] Stopping flows
6 Jun 01:35:28 - [info] [mqtt-broker:lokal] Disconnected from broker: mqtt://127.0.0.1:1883
6 Jun 01:35:28 - [info] Stopped flows
6 Jun 01:35:28 - [info] Starting flows
6 Jun 01:35:28 - [info] Started flows
6 Jun 01:35:28 - [info] [mqtt-broker:lokal] Connected to broker: mqtt://127.0.0.1:1883

what should i do then to bring it back

You aren’t using the right command to start node-RED

As you are on a pi. you you should be using

node-red-start

node-red-stop

node-red-log

You used

node-red log which starts node-red with a new flows file called log.

Make sure node-red isn’t running and then try starting with the correct command

sorry, i don't get it.

i've stop the node-red (node-red-stop), then i run that command ? (node-red-log). like this?

root@raspberrypi:~# node-red-stop

Stop Node-RED

Use node-red-start to start Node-RED again

root@raspberrypi:~# node-red-log

6 Jun 02:38:42 - [warn] ------------------------------------------------------
6 Jun 02:38:42 - [info] Settings file : /root/.node-red/settings.js
6 Jun 02:38:42 - [info] Context store : 'default' [module=memory]
6 Jun 02:38:42 - [info] User directory : /root/.node-red
6 Jun 02:38:42 - [warn] Projects disabled : editorTheme.projects.enabled=false
6 Jun 02:38:42 - [info] Flows file : /root/.node-red/flows_raspberrypi.json
6 Jun 02:38:42 - [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.

6 Jun 02:38:42 - [info] Starting flows
6 Jun 02:38:43 - [info] Started flows
6 Jun 02:38:43 - [info] Server now running at http://127.0.0.1:1880/
6 Jun 02:38:43 - [info] [mqtt-broker:lokal] Connected to broker: mqtt://127.0.0.1:1883
Stopping Node-RED graphical event wiring tool...
6 Jun 02:43:14 - [info] Stopping flows
6 Jun 02:43:14 - [info] [mqtt-broker:lokal] Disconnected from broker: mqtt://127.0.0.1:1883
6 Jun 02:43:14 - [info] Stopped flows
Stopped Node-RED graphical event wiring tool.

To start node-red you should use the command

node-red-start

Your latest paste also show you are now logged in as root whereas before you were logged in as pi.

Which one were you logged in as when you had your old flows?

Please also describe the reason you are logged in as root.

Also look at the two logs you have posted. Look at the User directory and the flows file each of them are using...

when i logged in as root or pi it was not effect my flow, my flow still exist.

i have also run that command as pi, but it didn't do anything. my old flow are not show up.

there is no specific reason, its just make me easy to run command without type sudo everytime