URL "http://192.168.1.131:1880/ui/#/0" no longer works since upgrade to node-red-dashboard 2.3.3
623 views
Skip to first unread message
Jan Van den Audenaerde
Feb 26, 2017, 4:20:05 AM2/26/17
to Node-RED
Hi,
I have recently upgraded node-red-dashboard to version 2.3.3
Since the upgrade the URL http://192.168.1.131:1880/ui/#/0 no longer works in chrome. (FYI 192.168.1.131 is the IP address of my raspberry pi running node-red).
I get a blank screen in chrome with following page source code:
| <!--</Deject>--> <!DOCTYPE html> <!-- | |
| Copyright 2016 JS Foundation and other contributors, https://js.foundation/ | |
| Copyright 2016 IBM Corp. | |
| Copyright 2015 Andrei Tatar | |
| Licensed under the Apache License, Version 2.0 (the "License"); | |
| you may not use this file except in compliance with the License. | |
| You may obtain a copy of the License at | |
| http://www.apache.org/licenses/LICENSE-2.0 | |
| Unless required by applicable law or agreed to in writing, software | |
| distributed under the License is distributed on an "AS IS" BASIS, | |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | |
| See the License for the specific language governing permissions and | |
| limitations under the License. | |
| --> <html lang="en" manifest="dashboard.appcache"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width,initial-scale=1"> <meta name="apple-mobile-web-app-capable" content="yes"> <meta name="mobile-web-app-capable" content="yes"> <link rel="icon" sizes="192x192" href="icon.jpg"> <link rel="shortcut icon" type="image/png" href="icon.png"> <link rel="stylesheet" href="css/app.min.css"> <title>Node-RED Dashboard</title> <link rel="stylesheet/less" href="css/app.min.less"> </head> <body ng-app="ui" ng-controller="MainController as main" ng-cloak layout="column" style="background: {{main.backgroundColor}}" class="nr-dashboard-theme"> <md-content ng-if="main.loaded" ng-include="'partials/main.html'" layout="column" flex></md-content> <script src="socket.io/socket.io.js"></script> <script src="js/app.min.js"></script> <script src="js/tinycolor-min.js"></script> </body> </html> <!--</Deject>--> |
The same URL works in internet explorer.
I can still get the same page in chrome by using following URLs:
kr
Jan
Dave C-J
Feb 26, 2017, 4:25:11 AM2/26/17
to node...@googlegroups.com
Can you edit /move something and redeploy?
sent from phone
Jan Van den Audenaerde
Feb 26, 2017, 4:26:57 AM2/26/17
to Node-RED
Note that I see that currently the latest node-red-dashboard version is 2.3.2 while the version I have installed a couple of days a ago is 2.3.3 !
If this problem is due to the fact that I have installed an incorrect version how can I install the correct version ?
many thanks for any help.
Jan
Jan Van den Audenaerde
Feb 26, 2017, 4:37:00 AM2/26/17
to Node-RED
Hi Dave,
Editing and redeploying it doesn't fix it.
Restarting node-red also doesn't fix it.
I have 2 chart nodes that are also not displaying any graphs since the upgrade to version 2.3.3
kr
Jan.
Jan Van den Audenaerde
Feb 26, 2017, 5:09:43 AM2/26/17
to Node-RED
I have reverted back to version 2.3.2 using the following command but this also didn't fix the issue (I admit I forget to redeploy the flow).
but when I reverted back to version 2.2.1 and redeployed the flow - it worked again as before (including the chart node).
pi@pi3one:~/.node-red $ sudo npm uninstall node-red-dashboard
unbuild node-red-...@2.3.3
pi@pi3one:~/.node-red $ sudo npm install node-red-...@2.3.2
node-red-...@2.3.2 node_modules/node-red-dashboard
├── serve-...@1.12.0 (escap...@1.0.3, enco...@1.0.1, pars...@1.3.1, se...@0.15.0)
└── sock...@1.7.3 (object...@4.1.0, socket.i...@0.5.0, has-b...@0.1.7, de...@2.3.3, socket.i...@2.3.1, engi...@1.8.3, socket.i...@1.7.3)
pi@pi3one:~/.node-red $ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://192.168.1.131:1880
On Pi Node-RED works better with the Firefox 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
26 Feb 10:57:20 - [info] Stopping flows
Stopped Node-RED graphical event wiring tool..
Starting Node-RED graphical event wiring tool....
Started Node-RED graphical event wiring tool..
26 Feb 10:59:18 - [info]
Welcome to Node-RED
===================
26 Feb 10:59:18 - [info] Node-RED version: v0.16.1
26 Feb 10:59:18 - [info] Node.js version: v4.7.2
26 Feb 10:59:18 - [info] Linux 4.4.26-v7+ arm LE
26 Feb 10:59:19 - [info] Loading palette nodes
pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/python -u /usr/lib/node_modules/node-red/nodes/core/hardware/nrgpio.py info
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
26 Feb 10:59:23 - [info] Dashboard version 2.3.2 started at /ui
26 Feb 10:59:29 - [info] Settings file : /home/pi/.node-red/settings.js
26 Feb 10:59:29 - [info] User directory : /home/pi/.node-red
pi@pi3one:~/.node-red $ node-red-stop
Stop Node-RED
Use node-red-start to start Node-RED again
pi@pi3one:~/.node-red $ sudo npm install node-red-...@2.2.1
node-red-...@2.2.1 node_modules/node-red-dashboard
├── serve-...@1.12.0 (escap...@1.0.3, enco...@1.0.1, pars...@1.3.1, se...@0.15.0)
└── sock...@1.7.3 (object...@4.1.0, socket.i...@0.5.0, has-b...@0.1.7, de...@2.3.3, socket.i...@2.3.1, engi...@1.8.3, socke t.io-...@1.7.3)
pi@pi3one:~/.node-red $ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://192.168.1.131:1880
On Pi Node-RED works better with the Firefox 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
Started Node-RED graphical event wiring tool..
26 Feb 11:05:22 - [info]
Welcome to Node-RED
===================
26 Feb 11:05:22 - [info] Node-RED version: v0.16.1
26 Feb 11:05:22 - [info] Node.js version: v4.7.2
26 Feb 11:05:22 - [info] Linux 4.4.26-v7+ arm LE
26 Feb 11:05:23 - [info] Loading palette nodes
pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/python -u /usr/lib/node_modules/node-red/nodes/core/hardware/nrgpio.py info
pam_unix(sudo:session): session opened for user root by (uid=0)
pam_unix(sudo:session): session closed for user root
26 Feb 11:05:28 - [info] Dashboard version 2.2.1 started at /ui
26 Feb 11:05:34 - [warn] Missing node modules:
26 Feb 11:05:34 - [warn] - node-red-dashboard: ui_date_picker
26 Feb 11:05:34 - [info] Removing modules from config
26 Feb 11:05:34 - [info] Settings file : /home/pi/.node-red/settings.js
26 Feb 11:05:34 - [info] User directory : /home/pi/.node-red
26 Feb 11:05:34 - [info] Flows file : /home/pi/.node-red/flows_pi3one.json
26 Feb 11:05:34 - [info] Server now running at http://127.0.0.1:1880/
26 Feb 11:05:34 - [info] Starting flows
26 Feb 11:05:35 - [info] Started flows
26 Feb 11:05:35 - [info] [mqtt-broker:9c9ae2bc.63652] Connected to broker: mqtt://192.168.1.131:1883
26 Feb 11:06:04 - [info] Stopping flows
26 Feb 11:06:05 - [info] [mqtt-broker:9c9ae2bc.63652] Disconnected from broker: mqtt://192.168.1.131:1883
26 Feb 11:06:05 - [info] Stopped flows
26 Feb 11:06:05 - [info] Starting flows
26 Feb 11:06:05 - [info] Started flows
26 Feb 11:06:05 - [info] [mqtt-broker:9c9ae2bc.63652] Connected to broker: mqtt://192.168.1.131:1883
Dave C-J
Feb 26, 2017, 5:15:05 AM2/26/17
to node...@googlegroups.com
Hi
any chance you can email me the flow if it's not too sensitive, so I can try to work out what's not upgrading ? dceejay gmail
thanks
Jan Van den Audenaerde
Feb 26, 2017, 5:26:31 AM2/26/17
to Node-RED
Just sent it to your gmail address.
Jan Van den Audenaerde
Feb 27, 2017, 5:48:45 AM2/27/17
to Node-RED
I have executed below commands as suggested and it is working again - thanks a lot.
reload latest 2.3.3stop and restart Node-RED serverreload the web page at least twice to flush the cache ctrl-r or whatever your browser requires.Clean up the flow - remove un-needed config nodes - goto menu - Configuration nodes should get this tab
click unused to show the unused ones... double click them to expand them and then hit the delete top left of each...then re-deploy and go to the dashboard... reload the page twice again... ctrl-r.
Reply all
Reply to author
Forward
0 new messages