• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
netPI _Node red issue
#1
Dear Sir,

We try to deploy the Docker Container (Node red) to netPI devices, but to access the Page 192.168.1.108:1880 IP address showing the attached error
   

netPI already TOSIBOX Container available .
   

Please see the log file-node red docker
Starting system message bus: dbus.,
Container is starting the first time,
23 Sep 06:17:38 - [info] ,
Welcome to Node-RED,
===================,
23 Sep 06:17:38 - [info] Node-RED version: v1.1.3,
23 Sep 06:17:38 - [info] Node.js  version: v12.18.3,
23 Sep 06:17:38 - [info] Linux 4.9.80-rt62 arm LE,
23 Sep 06:17:40 - [info] Loading palette nodes,
23 Sep 6:17:55 - [s7comm-Info] - Debug configuration for logLevelNodeS7:{"debug":0,"silent":true},
23 Sep 6:17:55 - [s7comm-Info] - Debug configuration for logLevelNodeRED:{"debug":2,"silent":true},
23 Sep 06:17:56 - [info] Dashboard version 2.22.1 started at /ui,
23 Sep 06:17:56 - [info] Settings file  : /root/.node-red/settings.js,
23 Sep 06:17:56 - [info] Context store  : 'default' [module=memory],
23 Sep 06:17:56 - [info] User directory : /root/.node-red,
23 Sep 06:17:56 - [warn] Projects disabled : editorTheme.projects.enabled=false,
23 Sep 06:17:56 - [info] Flows file    : /root/.node-red/flows_NTB827EB697608.json,
23 Sep 06:17:56 - [info] Creating new flow file,
23 Sep 06:17:56 - [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.,
---------------------------------------------------------------------,
23 Sep 06:17:56 - [info] Starting flows,
23 Sep 06:17:56 - [info] Started flows,
23 Sep 06:17:56 - [info] Server now running at https://127.0.0.1:1880/,
Removing stale PID file /var/run/dbus/pid..,
Starting system message bus: dbus.,
23 Sep 06:32:32 - [info] ,
Welcome to Node-RED,
===================,
23 Sep 06:32:32 - [info] Node-RED version: v1.1.3,
23 Sep 06:32:32 - [info] Node.js  version: v12.18.3,
23 Sep 06:32:32 - [info] Linux 4.9.80-rt62 arm LE,
23 Sep 06:32:35 - [info] Loading palette nodes,
23 Sep 6:33:4 - [s7comm-Info] - Debug configuration for logLevelNodeS7:{"debug":0,"silent":true},
23 Sep 6:33:4 - [s7comm-Info] - Debug configuration for logLevelNodeRED:{"debug":2,"silent":true},
23 Sep 06:33:06 - [info] Dashboard version 2.22.1 started at /ui,
23 Sep 06:33:06 - [info] Settings file  : /root/.node-red/settings.js,
23 Sep 06:33:06 - [info] Context store  : 'default' [module=memory],
23 Sep 06:33:06 - [info] User directory : /root/.node-red,
23 Sep 06:33:06 - [warn] Projects disabled : editorTheme.projects.enabled=false,
23 Sep 06:33:06 - [info] Flows file    : /root/.node-red/flows_NTB827EB697608.json,
23 Sep 06:33:06 - [info] Creating new flow file,
23 Sep 06:33:06 - [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.,
---------------------------------------------------------------------,
23 Sep 06:33:06 - [info] Starting flows,
23 Sep 06:33:06 - [info] Started flows,
23 Sep 06:33:06 - [info] Server now running at https://127.0.0.1:1880/,

Same procedure (https://hub.docker.com/r/hilschernetpi/netpi-nodered )with follow with NIOT-E-TPI51-EN-RE working fine .

BR,
Sandip
  Reply
#2
Well you have not read the "README" text file of the container well.

In the Chapter "Container access" it says


Code:
https://<device-ip-address>:1880

It says https and not http like your are using right now as I can see it in your screen shot.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  [SOLVED] Docker GUI login issue MGharat 1 225 September-19th-2019, 11:50 AM
Last Post: Armin@netPI
  DHCP/DNS issue: Couldn't access NetPI3 out-of-the-box zulliger@software-natives.ch 5 384 March-14th-2018, 06:47 PM
Last Post: adeeljsid

Forum Jump:


Users browsing this thread: 1 Guest(s)