node-red-dashboard won't show anything

[iotsw...@gmail.com]

I used node-red-contrib-ui which worked fine and now I wanted to change to the newer node-red-dashboard but despite updating my nodes, when I open http://localhost:1880/ui I can only see the top blue page whitout any graphs. Also on the bottom of the page it shows "The url cannot be loaded into an iframe."
What is wrong? Any ideas?
Thanks

[sebasti...@gmail.com]

I had a same issue when installing the dashboard not globally

sudo npm install -g node-red-dashboard solved it for me ... maybe this is related to your issue.

[iotsw...@gmail.com]

I have done that too but it still doesn't show anything on the dashboard...

[sebasti...@gmail.com]

Did you clear your caches?

Just try it in another browser 

[iotsw...@gmail.com]

I did, same result I can't see anything

[Nicholas O'Leary]

Hi,

you mentioned on the issue in github that 'even new nodes don't appear'.

Do you mean the dashboard nodes do not appear in the palette? Are there any error messages on startup?

Nick

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
For more options, visit https://groups.google.com/d/optout.

[iotsw...@gmail.com]

Hi,

The dashboard nodes appear well in the palette and there is no error message. The wepage /ui appears but blank with blue on the top (unlike green in contrib-ui) but no graph appears. By new nodes I mean if in nodered I put a button and deploy it, it also doesn't appear on the webpage.

Le mercredi 7 septembre 2016 15:55:48 UTC+2, Nick O'Leary a écrit :

Hi,

you mentioned on the issue in github that 'even new nodes don't appear'.

Do you mean the dashboard nodes do not appear in the palette? Are there any error messages on startup?

Nick

On 7 September 2016 at 14:48, <iotsw...@gmail.com> wrote:

I did, same result I can't see anything

Le mercredi 7 septembre 2016 15:15:54 UTC+2, sebasti...@gmail.com a écrit :

Did you clear your caches?

Just try it in another browser 

Am Mittwoch, 7. September 2016 15:07:57 UTC+2 schrieb iotsw...@gmail.com:

I have done that too but it still doesn't show anything on the dashboard...

Le mercredi 7 septembre 2016 14:46:01 UTC+2, sebasti...@gmail.com a écrit :

I had a same issue when installing the dashboard not globally

sudo npm install -g node-red-dashboard solved it for me ... maybe this is related to your issue.

Am Mittwoch, 7. September 2016 14:34:58 UTC+2 schrieb iotsw...@gmail.com:

I used node-red-contrib-ui which worked fine and now I wanted to change to the newer node-red-dashboard but despite updating my nodes, when I open http://localhost:1880/ui I can only see the top blue page whitout any graphs. Also on the bottom of the page it shows "The url cannot be loaded into an iframe."
What is wrong? Any ideas?
Thanks

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

[Nicholas O'Leary]

In the dashboard, rather than contrib-ui, you have to add your widgets to a group. If you have simply imported a contrib-ui flow they may not have a group associated with them.

In the dashboard sidebar there is a tree view of your tabs/groups/widgets. If you have any widgets not properly in a group, you'll get the warning you can see at the bottom of this screenshot. Clicking that link will add your widgets to a default group. You can then start to drag them around that tree to get them back where you want them.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

[Peter Scargill]

I am having this issue "the URL cannot be loaded into an IFRAME" on my new installations. I'm using DIET-PI.... So Node-Red is fine, everything else works like SQLITE, MQTT etc,  all the dashboard items are there - I've nothing - no flows - i.e. a clean installation - on Windows with Chrome - and I am getting this message at the bottom of the screen (normally just out of view - you have to scroll down). Node 4.6.0 - npn 2.15.9  and node-red 0.15.1 and dashboard 2.1.0 

No obvious error messages when starting node-red.

If I then stick a text box onto the flow - even before I put a value in -the problem goes away...  and that's fine - but I'm sure that message should not be there on an empty system?

Ideas chaps?

Pete.

[Dave C-J]

It's there because the dashboard is empty. And is indeed off the bottom of the screen. Not exactly informative, more for debug, has already been removed on master.

[Peter Scargill]

Magic

On 19 Oct 2016 08:53, "Dave C-J" <dce...@gmail.com> wrote:

It's there because the dashboard is empty. And is indeed off the bottom of the screen. Not exactly informative, more for debug, has already been removed on master.

--

http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---

You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/j015cz2jtNU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CACXWFwKjAxJJ52cpmFzkj7KOUgv5MdhMEZcGyDZvym0nmgpk0g%40mail.gmail.com.

[Cleyton Barroso]

Oi, não vi que respondeu com a solução. Conseguiu resolver o seu problema? Eu também estou com o mesmo problema.

[Stephen Mann]

I was having the same problem, but solved it by selecting all nodes on my flow then exporting the nodes to my clipboard.  Next I created a new flow, deleted the original flow, then import the nodes from the clipboard.  Everything works now.

Hope this helps someone else.