Node red dashboard not loading after a couple of days

Dashboard
1

Hi, Every couple of days Node Red becomes unloadable and displays the screen below.

IMG_0147
IMG_0147953×1255 79.8 KB

The page is really poor design as it tells me zero information about what the problem is!
Clicking the reload button does nothing. If however i copy the url to another browser the node red dashboard does load. So why does it stop loading in the first browser? The browsers are safari and chrome running on IOS. I get the issue with both browsers. If I go to the node red flows page. The browser does then reload the dashboard. But that is not a very good workaround for end users.

2

I have the same Problem an Safari on my IPhone. On PC it works.

3

Can you check the browser's JavaScript console for any error messages?

Also, do you have any security/login setup for the dashboard?

4

I don't know how on an IPhone...

No login used.

I use Node-Red 3.1.10 on an Victron Cerbo GX. The problem came since i update the dashboard to 1.22.1 (@flowfuse/node-red-dashboard)

5

Sorry, have no access to the javascript console on IOS. There is a webinspector where you can attach the device to a mac, but unfortunately my only other device is a laptop pc.

There are no login/security credentials in play.
Are there any logs in node red/linux that will have logged anything? I could not find anything.

I now have a node red page that displays the error message, where even a node red reload of the flows does not fix the issue (which did previously)
I have also deleted the browser cache for both safari and chrome with no luck.
Added a catch node to node red. Nothing logged.
I`m going to gradualy remove flows one by ond and see if anything changes.
Its very odd.
Works for a couple of days in both Safari and Chrome and also when saved as a web app (I presume this is just Safari without the address bar)
Then suddenly one browser or the web app will display the error screen, while it still works in the other browser/app. This leads me to believe the issue is client side.

6

Interesting, my node-red flows are running on a Victron CerboGX too.

7

When I accessed Node-Red via venus.local:1881 after the error appeared, I got a message saying the page was insecure, which I can confirm. Afterward, I was able to access the dashboard again. Perhaps it's related to that? The browser remembers the selection for a certain amount of time, and the prompt might then not work on the dashboard?

8

I have a web component that mirrors console logs to a web page. It should work fine with Dashboard.

Test/Demo pages and documentation here:

I wrote the visible-console component for just this kind of thing.

9

Thanks, that’s very useful.

10

Update. I ran the simplest flow with a single text node outputting the time stamp from an inject node. Same issue!

I also installed node red on another server (not the cerbo gx) no issues after a couple of days. Though it was using http not https…that’s my next test.

I’m going to post in the Victron forums and see what they say.