Hi, I'm very much a NR newbie and I've followed the tutorial for setting up a dashboard (https://randomnerdtutorials.com/getting-started-with-node-red-dashboard/) and the nodes Deploy without a problem. However, when I attempt to view the dashboard using 192.168.0.9:1880/ui all I get is a welcome screen with:
" Welcome to the Node-RED Dashboard
Please add some UI nodes to your flow and redeploy."
I'm running on a Mac and have tried using both Safari and Firefox but get the same result.
The html on the dashboard screen elements & console are provided as follows:
What flow have you got that contains dashboard nodes?
Have you made sure you have configured the dashboard nodes you are using (double click on the node)
Hi ukmoose, thanks for your prompt response. I followed to the letter, the tutorial I referenced earlier. There are three dashboard nodes with flows to/from MQTT nodes. When I deploy the nodes, NR confirms that deployment was successful. I have an MQTT process going and have verified that MQTT is communicating between different terminals.
My flow is shown in the attached. The point is that when I try and view the dashboard in a separate browser tab (192.168.0.9:1880/ui) I get the message I stated earlier.
Regarding versions, I have the following:
16 Oct 09:17:58 - [info] Node-RED version: v1.0.0
16 Oct 09:17:58 - [info] Node.js version: v12.10.0
16 Oct 09:17:58 - [info] Linux 4.19.66-v7l+ arm LE
16 Oct 09:17:59 - [info] Loading palette nodes
16 Oct 09:18:00 - [info] Dashboard version 2.16.3 started at /ui
16 Oct 09:18:01 - [info] Settings file : /home/pi/.node-red/settings.js
16 Oct 09:18:01 - [info] Context store : 'default' [module=memory]
16 Oct 09:18:01 - [info] User directory : /home/pi/.node-red
16 Oct 09:18:01 - [warn] Projects disabled : editorTheme.projects.enabled=false
16 Oct 09:18:01 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
16 Oct 09:18:01 - [error] Unable to listen on http://127.0.0.1:1880/
16 Oct 09:18:01 - [error] Error: port in use
127.0.0.1 is just the loopback address. I should explain my current configuration:
I'm, running Node Red on my Raspberry Pi, which is connected to my home LAN. I'm accessing the NR service via a browser on my Mac .
Both Safari & Firefox give the same result when I try and view the NR Dashboard via 192.168.0.9:1880/ui
The bit @colin was talking about was the error message. The reason that it couldn’t listen on port 1880 is generally because node-red is already running and is already using that port.
OK, perhaps I'm missing something. Why would Node Red be trying to use the same port that it knows it's already using. I'm attaching the Node Red console output, which shows that MQTT is running on port 8083. Could this be a source of the conflict?
15 Oct 17:56:43 - [info] Starting flows
15 Oct 17:56:43 - [info] Started flows
15 Oct 17:56:43 - [info] [debug:Time-Now1]
15 Oct 17:57:19 - [info] [debug:Time-Now1]
15 Oct 17:57:27 - [info] [debug:Time-Now1]
15 Oct 18:20:35 - [info] Stopping flows
15 Oct 18:20:35 - [info] Stopped flows
15 Oct 18:20:35 - [info] Starting flows
15 Oct 18:20:35 - [info] Started flows
15 Oct 18:20:35 - [info] [mqtt-broker:f16796aa.830258] Connected to broker: mqtt://localhost:1883
15 Oct 18:27:41 - [info] Stopping flows
15 Oct 18:27:41 - [info] [mqtt-broker:f16796aa.830258] Disconnected from broker: mqtt://localhost:1883
15 Oct 18:27:41 - [info] Stopped flows
15 Oct 18:27:41 - [info] Starting flows
15 Oct 18:27:41 - [info] Started flows
15 Oct 18:27:41 - [info] [mqtt-broker:f16796aa.830258] Connected to broker: mqtt://localhost:1883
15 Oct 18:28:01 - [info] Stopping flows
15 Oct 18:28:01 - [info] [mqtt-broker:f16796aa.830258] Disconnected from broker: mqtt://localhost:1883
No it is because you tried starting Node-RED whilst another copy was already running.
Getting back to the initial issue…
Have you installed other “dashboards”
eg node-red-contrib-mdashboard ?
Have you tried updating to the latest
version of node-red-dashboard?
If you are planning on doing other things in node-RED i would also suggest moving to nodejsv10 (the LTS version) as already suggested as contrib nodes may have issues with v12
The version of NR etc. are shown below and I haven't installed node-red-contrib-mdashboard.
16 Oct 13:26:28 - [info] Node-RED version: v1.0.0
16 Oct 13:26:28 - [info] Node.js version: v12.10.0
16 Oct 13:26:28 - [info] Linux 4.19.66-v7l+ arm LE
16 Oct 13:26:29 - [info] Loading palette nodes
16 Oct 13:26:31 - [info] Dashboard version 2.16.3 started at /ui
16 Oct 13:26:32 - [info] Settings file : /home/pi/.node-red/settings.js
16 Oct 13:26:32 - [info] Context store : 'default' [module=memory]
16 Oct 13:26:32 - [info] User directory : /home/pi/.node-red
16 Oct 13:26:32 - [warn] Projects disabled : editorTheme.projects.enabled=false
16 Oct 13:26:32 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
16 Oct 13:26:32 - [info] Server now running at http://127.0.0.1:1880/
I'm also attaching below the relevant processes running at the moment. I also rebooted the Pi and started Nodes Red. I still get the same problem.
Hi bakman2, that's the very one that I used originally; so I'm not sure that's going to resolve anything. I'd rather try and understand what's going on.
If it's still the general opinion that port conflict is the key issues then I don't see how port 1880 could be already used when there's only one instance of NR running and the Mosquito server is using port 1883. I'm listing the port usage below, which shows that only one instance of NR is using port 1880. This could be a red-herring, as the "unable to listen" error report came as a result of checking versions. Any suggestions?
This is what the NR console shows after a deploy the Flow. It seems to make sense to me but I still get the same message, as originally posted, on the Dashboard screen. ???
16 Oct 14:54:34 - [info] Stopping flows
16 Oct 14:54:34 - [info] [mqtt-broker:f16796aa.830258] Disconnected from broker: mqtt://localhost:1883
16 Oct 14:54:34 - [info] Stopped flows
16 Oct 14:54:34 - [info] Starting flows
16 Oct 14:54:34 - [info] Started flows
16 Oct 14:54:34 - [info] [mqtt-broker:f16796aa.830258] Connected to broker: mqtt://localhost:1883
OK, I've updated the NR Dashboard to current version 2.17.1 and installed nodes 10./16.3 LTS but the problem persists.
16 Oct 17:34:54 - [info] Node-RED version: v1.0.0
16 Oct 17:34:54 - [info] Node.js version: v10.16.3
16 Oct 17:34:54 - [info] Linux 4.19.66-v7l+ arm LE
16 Oct 17:34:54 - [info] Loading palette nodes
16 Oct 17:34:56 - [info] Dashboard version 2.17.1 started at /ui
16 Oct 17:34:56 - [warn] ------------------------------------------------------
16 Oct 17:34:56 - [warn] [node-red-node-serialport/serialport] Error: The module '/home/pi/.node-red/node_modules/@serialport/bindings/build/Release/bindings.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 72. This version of Node.js requires
NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
the module (for instance, using npm rebuild or npm install).
16 Oct 17:34:56 - [warn] ------------------------------------------------------
16 Oct 17:34:56 - [info] Settings file : /home/pi/.node-red/settings.js
16 Oct 17:34:56 - [info] Context store : 'default' [module=memory]
16 Oct 17:34:56 - [info] User directory : /home/pi/.node-red
16 Oct 17:34:56 - [warn] Projects disabled : editorTheme.projects.enabled=false
16 Oct 17:34:56 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
16 Oct 17:34:57 - [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.
16 Oct 17:34:57 - [info] Starting flows
16 Oct 17:34:57 - [info] Started flows
16 Oct 17:34:57 - [info] Server now running at http://127.0.0.1:1880/
16 Oct 17:34:57 - [info] [mqtt-broker:f16796aa.830258] Connected to broker: mqtt://localhost:1883
16 Oct 17:35:10 - [info] Stopping flows
16 Oct 17:35:10 - [info] [mqtt-broker:f16796aa.830258] Disconnected from broker: mqtt://localhost:1883
16 Oct 17:35:10 - [info] Stopped flows
16 Oct 17:35:10 - [info] Starting flows
16 Oct 17:35:10 - [info] Started flows
16 Oct 17:35:10 - [info] [mqtt-broker:f16796aa.830258] Connected to broker: mqtt://localhost:1883
As the error says, you need to rebuild nodes that were compiled with the other version. Go into the .node-red folder and npm rebuild
then restart node-red.
