Cannot access dashboard from other devices

Dashboard
1

Hello everybody,

I'd like to access to Node-Red Dashboard via mobile phone but I have some problems:

A) If I try to connect to the Node-Red IP (192.168.1.59:1880/ui) from the Raspberry Pi itself (Chrome), the Dashboard page loads correctly.
B) If I try to open the same IP from any other device connected on the same network (e.g. my mobile phone or another laptop), the Dashboard page does not load.
C) This is the log that I get when I write the command "node-red-start":
node-red-start

Start Node-RED

Once Node-RED has started, point a browser at http://192.168.1.59: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.
2 Jan 22:47:38 - [info]
Welcome to Node-RED

2 Jan 22:47:39 - [info] Node-RED version: v1.0.6
2 Jan 22:47:39 - [info] Node.js version: v10.21.0
2 Jan 22:47:39 - [info] Linux 5.4.79-v7l+ arm LE
2 Jan 22:47:41 - [info] Loading palette nodes
2 Jan 22:47:43 - [info] Dashboard version 2.26.1 started at /ui
2 Jan 22:47:44 - [info] Settings file : /home/pi/.node-red/settings.js
2 Jan 22:47:44 - [info] Context store : 'default' [module=memory]
2 Jan 22:47:44 - [info] User directory : /home/pi/.node-red
2 Jan 22:47:44 - [warn] Projects disabled : editorTheme.projects.enabled=false
2 Jan 22:47:44 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
2 Jan 22:47:44 - [info] Starting flows
2 Jan 22:47:44 - [info] Started flows
2 Jan 22:47:44 - [info] Server now running at http://127.0.0.1:1880/

D) This is the log that I get when I write the command "node-red-log"
node-red-log

2 Jan 18:20:45 - [info] Starting flows
2 Jan 18:20:45 - [info] Started flows
2 Jan 18:20:45 - [info] Server now running at http ://127.0.0.1:1880/
Stopping Node-RED graphical event wiring tool...
2 Jan 22:47:32 - [info] Stopping flows
2 Jan 22:47:32 - [info] Stopped flows
nodered.service: Succeeded.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
2 Jan 22:47:38 - [info]
Welcome to Node-RED

2 Jan 22:47:39 - [info] Node-RED version: v1.0.6
2 Jan 22:47:39 - [info] Node.js version: v10.21.0
2 Jan 22:47:39 - [info] Linux 5.4.79-v7l+ arm LE
2 Jan 22:47:41 - [info] Loading palette nodes
2 Jan 22:47:43 - [info] Dashboard version 2.26.1 started at /ui
2 Jan 22:47:44 - [info] Settings file : /home/pi/.node-red/settings.js
2 Jan 22:47:44 - [info] Context store : 'default' [module=memory]
2 Jan 22:47:44 - [info] User directory : /home/pi/.node-red
2 Jan 22:47:44 - [warn] Projects disabled : editorTheme.projects.enabled=false
2 Jan 22:47:44 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
2 Jan 22:47:44 - [info] Starting flows
2 Jan 22:47:44 - [info] Started flows
2 Jan 22:47:44 - [info] Server now running at http ://127.0.0.1:1880/

FURTHER INFORMATION

i) I tried already to uninstall and install back Node-Red but the issue stays
ii) I checked already and all node packages inside "Manage palette" are up to date
iii) I checked already to use package "contrib-ui" instead of "dashboard" but did not solve the issue.

QUESTIONS

  1. Is there anything else I can check (e.g. missing libraries, missing files, wrong paths, etc...)?
  2. Am I missing some necessary steps to access Dashboard via mobile?

Thank you in advance for your help

Best Regards
Manuel

2

I suspect that it is not the cause of the problem, but I see you are using an old version of node-red. Did you use the recommended method for installing node-red on a pi?

3

Hello @Colin,

thank you for your advice.

I uninstalled Node-Red and installed it back using the recommended method but the issue is still present.
This is the log I get right after command "node-red-start":

Start Node-RED

Once Node-RED has started, point a browser at http ://192.168.1.59: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.
3 Jan 21:28:47 - [info]
Welcome to Node-RED

3 Jan 21:28:47 - [info] Node-RED version: v1.2.6
3 Jan 21:28:47 - [info] Node.js version: v12.20.0
3 Jan 21:28:47 - [info] Linux 5.4.79-v7l+ arm LE
3 Jan 21:28:47 - [info] Loading palette nodes
3 Jan 21:28:49 - [info] Dashboard version 2.26.1 started at /ui
3 Jan 21:28:49 - [info] Settings file : /home/pi/.node-red/settings.js
3 Jan 21:28:49 - [info] Context store : 'default' [module=memory]
3 Jan 21:28:49 - [info] User directory : /home/pi/.node-red
3 Jan 21:28:49 - [warn] Projects disabled : editorTheme.projects.enabled=false
3 Jan 21:28:49 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
3 Jan 21:28:49 - [info] Server now running at http ://127.0.0.1:1880/
3 Jan 21:28:49 - [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 Jan 21:28:49 - [info] Starting flows
3 Jan 21:28:49 - [info] Started flows

Is there anything else I should check to make Dashboard work on my mobile as well?

Thank you
Manuel

4

What do you see in the browser on the PC when the dashboard won't load?
Are you able to open the node red editor from the PC?
Also, from a pc, are you able to ping 192.168.1.59?

5

I can ping the IP from an external laptop, but if I try to open the IP, the browser page shows the message "impossible to reach the website: 192.169.1.59 required too much time - ERR_CONNECTION_TIMED_OUT".
As a consequence, I cannot either open the editor from the external laptop.
The same situation can be verified if I use my mobile phone instead of the external laptop.

6

If you are absolutely certain that that is the correct ip for the pi then I think that must mean that port 1880 is blocked on the pi. Have you enabled a firewall?

7

Are you using http://192.168.1.59 or http://192.168.1.59:1880? (it is not clear to me)

8

Thank you @Colin! I enabled port 1880 on my pi using "sudo ufw allow 1880" and after it worked!

9

Hello @zenofmud, I was using the former for pinging while the latter is the dashboard IP.
I solved the issue by enabling port 1880 with the command "sudo ufw allow 1880".

1 Like
10

That is the problem with enabling a firewall, you have to remember to allow through the things you want to do :slight_smile:

11

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