Can't open node red

General
1

I cannot open node red. Here is the message appears:

RizkiMF@Rizki-MF-MBP ~ % node-red
21 Apr 17:04:58 - [info] 

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

21 Apr 17:04:58 - [info] Node-RED version: v3.1.2
21 Apr 17:04:58 - [info] Node.js  version: v16.20.1
21 Apr 17:04:58 - [info] Darwin 21.6.0 x64 LE
21 Apr 17:04:59 - [info] Loading palette nodes
   ***   connect-system function called
ipc initialize
21 Apr 17:04:59 - [warn] [RED.events] Deprecated use of "nodes-started" event from "/Users/RizkiMF/.node-red/node_modules/connect-nodes/ipc/ipc.js:66:20". Use "flows:started" instead.
21 Apr 17:04:59 - [warn] [RED.events] Deprecated use of "nodes-stopped" event from "/Users/RizkiMF/.node-red/node_modules/connect-nodes/ipc/ipc.js:67:20". Use "flows:stopped" instead.
serial2-ajax-gateway initialize
serialport-gateway initialize /dev/ttyS2
http-gateway initialize
modbus-rs485-gateway initialize
serial1-connect-gateway initialize. Block type: undefined. Block version: undefined
serialport-gateway initialize /dev/ttyS1
21 Apr 17:05:00 - [info] Dashboard version 3.2.0 started at /ui
on error
21 Apr 17:05:00 - [warn] ------------------------------------------------------
21 Apr 17:05:00 - [warn] [connect-nodes/CONNECT system] Error: EACCES: permission denied, mkdir '/etc/connect-nodes/zigbee'
21 Apr 17:05:00 - [warn] ------------------------------------------------------
21 Apr 17:05:00 - [info] Settings file  : /Users/RizkiMF/.node-red/settings.js
21 Apr 17:05:00 - [info] Context store  : 'default' [module=memory]
21 Apr 17:05:00 - [info] User directory : /Users/RizkiMF/.node-red
21 Apr 17:05:00 - [info] Projects directory: /Users/RizkiMF/.node-red/projects
21 Apr 17:05:00 - [warn] No active project : using default flows file
21 Apr 17:05:00 - [info] Flows file     : /Users/RizkiMF/.node-red/flows.json
21 Apr 17:05:01 - [info] Server now running at http://127.0.0.1:1880/
21 Apr 17:05:01 - [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.
---------------------------------------------------------------------

21 Apr 17:05:01 - [info] Starting flows
21 Apr 17:05:01 - [error] [mqttdb in:e81d72bbcaa20b27] missing broker configuration
21 Apr 17:05:01 - [info] Started flows
21 Apr 17:05:02 - [info] [mqtt-broker:af6fb6b65ea2fa1f] Connected to broker: mqtt://broker.mqtt-dashboard.com:1883
on error
on error
on error
on error
on error
on error

Can anyone help to solve this problems?

2

Welcome to the forum @rizkimf18

Please post the file /Users/RizkiMF/.node-red/.package.json so we can see what nodes you have installed. Copy/paste please, not screenshot. Us this technique when pasting it in so that forum will not interpret it as markdown: How to share code or flow json

3

Here is the file on package.json


{
    "name": "node-red-project",
    "description": "A Node-RED Project",
    "version": "0.0.1",
    "private": true,
    "dependencies": {
        "connect-nodes": "~0.0.2",
        "node-red-contrib-buffer-parser": "~3.2.2",
        "node-red-contrib-mqttdb": "~0.1.2",
        "node-red-contrib-remote-io": "~3.1.1",
        "node-red-dashboard": "~3.2.0",
        "node-red-node-msgpack": "~1.2.1",
        "node-red-node-serialport": "~1.0.1",
        "red-contrib-string-binary-parser": "~0.0.3"
    }
}
4

I suggest not using that, it is very old and looks as if it is no longer maintained. Use the node red built in mqtt nodes. If you want the data to persist then use Retained Topics. That is what they are for.

That also has not been updated for a while, but there is no link to a github repository, so no way to report issues. Wherever possible I avoid nodes that have not got public repositories. It seems likely that the 'connect-nodes' errors are coming from that node. You can confirm that by running, from the .node-red folder,
npm list connect-nodes
and it will tell you where it is used.

I don't know anything about Wago, but searching for that on the node red flows site has a number of hits so might be worth looking at those.

5

Thank you for your advce

I try to running

npm list connect-nodes

from the .node-red folder

Here is the screenshoot

image
image1132×358 23 KB

6

Oh, I have just realised you have manually installed connect-nodes as can be seen from the fact that it is referenced in package.json.

Why did you install it? If you don't need it then remove it by running, from the .node-red folder
npm remove connect-nodes
and restart node-red.

7

Great, thank you for your help. It works and I can run node red again. Thank you