Hi there
My main Node-Red installation - been using it wthout issue until today - I tried using the palette Manager to install Aedes MQTT - it failed.
When I checked 5 minutes later, the palette manager had disappeared. So, I tried a reboot - Node-Red is running fine - but no pallete manager. Ignore the connection to 192.168.1.198 issue below - thats a board not connected.
I'm looking for ideas that don't involve going back to a clone as I've not cloned this for weeks and I've been adding or modifying flows to Node-Red.
Note the line in the block below that says
10 Feb 13:47:10 - [info] Palette editor disabled : npm command not found
HELP anyone?
Once Node-RED has started, point a browser at http://192.168.1.19:1880
On Pi Node-RED works better with the Firefox or Chrome browser
Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot
To find more nodes and example flows - go to http://flows.nodered.org
Starting as a systemd service.
10 Feb 13:47:10 - [info]
Welcome to Node-RED
10 Feb 13:47:10 - [info] Node-RED version: v1.2.6
10 Feb 13:47:10 - [info] Node.js version: v10.23.1
10 Feb 13:47:10 - [info] Linux 5.10.11-v8+ arm LE
10 Feb 13:47:10 - [info] Palette editor disabled : npm command not found
10 Feb 13:47:10 - [info] Loading palette nodes
10 Feb 13:47:16 - [info] Worldmap version 2.6.0
10 Feb 13:47:17 - [info] Dashboard version 2.25.0 started at /ui
10 Feb 13:47:18 - [info] Settings file : /home/pi/.node-red/settings.js
10 Feb 13:47:18 - [info] HTTP Static : /home/pi/.node-red/public
10 Feb 13:47:18 - [info] Context store : 'default' [module=localfilesystem]
10 Feb 13:47:18 - [info] User directory : /home/pi/.node-red
10 Feb 13:47:18 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
10 Feb 13:47:18 - [info] Flows file : /home/pi/.node-red/flows.json
10 Feb 13:47:18 - [info] Server now running at http://127.0.0.1:1880/
10 Feb 13:47:18 - [info] Starting flows
10 Feb 13:47:31 - [info] [tcp out:6a1096d9.774ed8] connecting to 192.168.1.198:55443
10 Feb 13:47:31 - [info] [tcp in:5bbaf720.b78f58] connecting to 192.168.1.198:55443
10 Feb 13:47:32 - [info] Started flows
10 Feb 13:47:32 - [info] [sqlitedb:6e9a0125.59bc4] opened /home/pi/dbs/iot.db ok
10 Feb 13:47:32 - [info] [sqlitedb:fdbe27fe.fb7848] opened /home/pi/dbs/iot.db ok
10 Feb 13:47:32 - [info] [sqlitedb:33875a87.57ade6] opened /home/pi/dbs/iot.db ok
10 Feb 13:47:32 - [info] [tcp out:6a1096d9.774ed8] error: Error: connect ECONNREFUSED 192.168.1.198:55443
10 Feb 13:47:32 - [info] [tcp in:5bbaf720.b78f58] Error: connect ECONNREFUSED 192.168.1.198:55443
10 Feb 13:47:33 - [info] [tcp in:5bbaf720.b78f58] connection lost to 192.168.1.198:55443
10 Feb 13:47:33 - [info] [tcp out:6a1096d9.774ed8] connection lost to 192.168.1.198:55443
10 Feb 13:47:33 - [info] [mqtt-broker:4c682b3a.2ab5c4] Connected to broker: mqtt://127.0.0.1:1883
10 Feb 13:47:40 - [info] [e-mail:peterscargill@gmail.com] Message sent: 250 2.0.0 OK 1612961260 r12sm2821083wrp.13 -