Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node-red dashboards are not loading after the upgrade. Lots of failed socket.io calls. #1104

Closed
niirvana-git opened this issue Aug 27, 2021 · 13 comments
Labels
stale There has not been activity on this issue or PR for quite some time.

Comments

@niirvana-git
Copy link

Problem/Motivation

After I upgraded Home assistant to the latest version (2021.8.8) and Node-red add-on to 10.0.0 version, my Node-red dashboards are not loading anymore. There's only an empty page. I have several dashboards in Node-red that I have added to Home assistant Lovelace dashboard as tabs (iFrame). On my Lovelace dashboard, I also have one IFrame card that should be showing one of the Node-red dashboards. I'm using this kind of URLs ,"https://my-external-address.duckdns.org/endpoint/ui/#!/1", in IFrames. Everything has been working great for over a year until the upgrade.

When I review developer tools (F12 in Chrome) I can see that there are lot of calls (socket.io) happening all the time. Some of these calls are failing (status 400), but some are also ok (status 200). One example request: "https://my-external-address.duckdns.org/endpoint/ui/socket.io/?EIO=3&transport=polling&t=Nk7y6OT&sid=co_03HXXdWMUGEymAAAc".

If I try to open dashboards in incognito mode in Chrome, everything works. If I clear cache in Chrome, I can also access the dashboard. However, if I try to access dashboards in home assistant , there's only an empty page, and after that page isn't anymore opening in Chrome either (in incognito it's still ok however).

It seems that this issue has been happening in the past as well, but is now back for some reason Please see this issue. It seems exactly the same.

I'm also using Nginx Proxy Manager where, in addition, to basic stuff, I have defined custom location for node-red "endpoint/ui". Everything has been working for over a year already, so I assume that Nginx configurations are ok.

Expected behavior

I'm expecting dashboards to load without errors as before the upgrade.

Actual behavior

Page is empty and there are lots of socket.io calls happening and failing in the background.

Steps to reproduce

Upgrade to latest versions. Create Node-red dashboard. Add it to Home assistant dashboard as an IFrame. Try to access.

Proposed changes

No idea why this is happening.

@niirvana-git niirvana-git changed the title Node-read dashboards are not loading after the upgrade. Lots of failed socket.io calls. Node-red dashboards are not loading after the upgrade. Lots of failed socket.io calls. Aug 27, 2021
@github-actions
Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Sep 27, 2021
@niirvana-git
Copy link
Author

I upgraded to the latest version, but it didn't change anything. I can only access Node-red dashboards in incognito mode in Chrome. Otherwise it's just a blank page and lot's of failed calls happening in the background (network/dev tools).

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Sep 28, 2021
@Thomaswaldick
Copy link

I upgraded to the latest version, but it didn't change anything. I can only access Node-red dashboards in incognito mode in Chrome. Otherwise it's just a blank page and lot's of failed calls happening in the background (network/dev tools).

Appreciate the Chrome recommendation! I'm also running into a similar issue. Node-Red dashboard is not able to load on firefox either locally or over the internet. I was able to get it to load on Google Chrome. The first part of the error message on Firefox was

"The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range."

@niirvana-git
Copy link
Author

I'm quite surprised that no one else has commented anything to this issue. I'm wondering if this is the right place for this issue? Any other suggestions?

I believe the issue must be in Node-red/this addon or in home assistant itself. I can still access the dashboards in incognito mode in Chrome and also without incognito when clearing the cache. When I try to do it home assistant, it doesn't work. Something is saved to some persistent state/cache that is causing loading dashboards to fail.

@github-actions
Copy link

github-actions bot commented Nov 1, 2021

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Nov 1, 2021
@niirvana-git
Copy link
Author

Still not working.

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Nov 2, 2021
@github-actions
Copy link

github-actions bot commented Dec 3, 2021

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Dec 3, 2021
@niirvana-git
Copy link
Author

niirvana-git commented Dec 5, 2021

Upgraded to the latest version. Still not working.

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Dec 6, 2021
@github-actions
Copy link

github-actions bot commented Jan 5, 2022

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Jan 5, 2022
@niirvana-git
Copy link
Author

Not working

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Jan 8, 2022
@github-actions
Copy link

github-actions bot commented Feb 8, 2022

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Feb 8, 2022
@niirvana-git
Copy link
Author

Still not working

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Feb 14, 2022
@github-actions
Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Mar 16, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Apr 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stale There has not been activity on this issue or PR for quite some time.
Projects
None yet
Development

No branches or pull requests

2 participants