Dashboard is not accessible from other devices in the network

#1

Hi,

I can only display the dashboard on the pc where nodered is running. On my mobile device nothing appears.

Does anyone know the reason?

Thanks

Georg

#2

Are you typing in the ip address in the url?

if so are you sure it’s the address of your pc on the network? You can normally get a list of connected machines and their up addresses from your home router

#3

yes i am sure it´s the address of the pc, because i can reach the nodered editor. But not the dashboard

#4

Are you trying to get to the dashboard from the link in the editor or by entering the url directly? Whichever it is, try the other.

#5

Both ways do not work

#6

What does it show when it does not work?

Have you got another PC on the network, if so then can that connect?

#7

Also can you post what is in the node red log when you start node red? If on a pi or debian based system you should see this by running node-red-log. Not sure how you get it on Windows.

#8

NodeRed is running on a pi
This is what appears by node-red-log

26 Oct 12:01:50 - [info] Server now running at http://127.0.0.1:1880/
26 Oct 12:01:51 - [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.

26 Oct 12:01:51 - [info] Starting flows
26 Oct 12:01:51 - [error] [users_config:a2551b5d.fc4a48] Node users list is not set
2018-10-26 18:01:51: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
2018-10-26 18:01:51: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
2018-10-26 18:01:51: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
2018-10-26 18:01:51: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
26 Oct 12:01:53 - [info] Started flows
26 Oct 12:01:53 - [info] [mqtt-broker:9a315e4.715c1a] Connected to broker: mqtt://localhost:1883
26 Oct 12:01:53 - [info] [mqtt-broker:56e5467d.468e38] Connected to broker: mqtt://localhost:1883
2018-10-26 18:01:54: [object Object]
26 Oct 12:01:54 - [error] [modbustcp-read:I1-I8] ModbusTCPClient: {"err":"Offline","message":"no connection to modbus server"}
26 Oct 12:01:54 - [error] [modbustcp-server:9f1acf74.bae39] socket error: undefined: Locally emitted error
{ err: 'Offline', message: 'no connection to modbus server' }
2018-10-26 18:01:54: I1-I8 was disconnected or was unable to connect

#9

The bit before that would be useful please. Run node-red-log in one terminal then restart node red in another.

#10

Do you mean this ?

Welcome to Node-RED

26 Oct 12:44:13 - [info] Node-RED version: v0.19.4
26 Oct 12:44:13 - [info] Node.js version: v8.12.0
26 Oct 12:44:13 - [info] Linux 4.14.70-v7+ arm LE
26 Oct 12:44:14 - [info] Loading palette nodes
html-pdf: Failed to load PhantomJS module. { Error: Cannot find module 'phantomjs-prebuilt'
at Function.Module._resolveFilename (module.js:548:15)
at Function.Module._load (module.js:475:25)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18)
at Object. (/home/pi/.node-red/node_modules/html-pdf/lib/pdf.js:7:19)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3) code: 'MODULE_NOT_FOUND' }
26 Oct 12:44:20 - [info] UI started at /ui
26 Oct 12:44:20 - [info] UI started at /ui
26 Oct 12:44:21 - [info] Dashboard version 2.10.0 started at /ui
26 Oct 12:44:22 - [warn] ------------------------------------------------------
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_button] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_switch] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_slider] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_numeric] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_text] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_text_input] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_gauge] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_chart] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_toast] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_link] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_template] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui/ui_tab] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_button] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_button_row] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_radio_button] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_switch] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_slider] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_numeric] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_text] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_text_input] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_gauge] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_chart] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_toast] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_link] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_template] Type already registered
26 Oct 12:44:22 - [warn] [node-red-contrib-ui_j/ui_tab] Type already registered
26 Oct 12:44:22 - [warn] ------------------------------------------------------
26 Oct 12:44:22 - [info] Settings file : /home/pi/.node-red/settings.js
26 Oct 12:44:22 - [info] HTTP Static : /home/pi/Pictures
26 Oct 12:44:22 - [info] Context store : 'default' [module=memory]
26 Oct 12:44:22 - [info] User directory : /home/pi/.node-red
26 Oct 12:44:22 - [warn] Projects disabled : editorTheme.projects.enabled=false
26 Oct 12:44:22 - [info] Flows file : /home/pi/.node-red/flows_H0028631.json
26 Oct 12:44:22 - [info] Server now running at http://127.0.0.1:1880/
26 Oct 12:44:22 - [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.

26 Oct 12:44:22 - [info] Starting flows
26 Oct 12:44:22 - [error] [users_config:a2551b5d.fc4a48] Node users list is not set
2018-10-26 18:44:22: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
2018-10-26 18:44:22: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
2018-10-26 18:44:22: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
2018-10-26 18:44:23: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
26 Oct 12:44:24 - [info] Started flows
2018-10-26 18:44:24: [object Object]
26 Oct 12:44:24 - [error] [modbustcp-read:I1-I8] ModbusTCPClient: {"err":"Offline","message":"no connection to modbus server"}
26 Oct 12:44:24 - [error] [modbustcp-server:9f1acf74.bae39] socket error: undefined: Locally emitted error
{ err: 'Offline', message: 'no connection to modbus server' }
2018-10-26 18:44:24: I1-I8 was disconnected or was unable to connect
26 Oct 12:44:24 - [info] [mqtt-broker:9a315e4.715c1a] Connected to broker: mqtt://localhost:1883
26 Oct 12:44:24 - [info] [mqtt-broker:56e5467d.468e38] Connected to broker: mqtt://localhost:1883

#11

I think you have two dashboard nodes installed, node-red-dashboard and nod-red-contrib-ui. You must remove one of them.
I suggest also sorting out the phantomjs problem.

#12

Ok thanks I will try it