This does not happen in Firefox.
Windows 11 Pro, Edge both fully updated. Unsure how long this has been happening.
If I log into the GUI of my cluster, it does not matter which node, and navigate away from the tab for a few minutes, when I return to it the canvas will be white.
Sometimes I can wait and the GUI will render without further incident. If I do not wish to wait the indeterminant amount of time and refresh the page, I will get often get a "This page isn't responding" dialog.
Choosing [ Wait ] does not affect the outcome. Perhaps the dialog appears again or I am forced to refresh the page again.
Choosing [ Exit page ] brings me to a "This page is having a problem" message.
Clicking the [ Refresh ] button always successfully renders the page.
I have:
I do not expect to get this resolved, but perhaps someone knows something else I should check. It might be a policy I set and have forgotten about. Maybe someone else is having a similar issue that developed recently and finds this. I hope it helps them.
Windows 11 Pro, Edge both fully updated. Unsure how long this has been happening.
If I log into the GUI of my cluster, it does not matter which node, and navigate away from the tab for a few minutes, when I return to it the canvas will be white.
Sometimes I can wait and the GUI will render without further incident. If I do not wish to wait the indeterminant amount of time and refresh the page, I will get often get a "This page isn't responding" dialog.
Choosing [ Wait ] does not affect the outcome. Perhaps the dialog appears again or I am forced to refresh the page again.
Choosing [ Exit page ] brings me to a "This page is having a problem" message.
Clicking the [ Refresh ] button always successfully renders the page.
I have:
- updated and restarted all nodes
- cleared cache and cookies from all time in Edge
- excluded the nodes from tracking prevention in Edge
- disabled power and performance settings in Edge
- switched between vertical and horizontal tabs
I do not expect to get this resolved, but perhaps someone knows something else I should check. It might be a policy I set and have forgotten about. Maybe someone else is having a similar issue that developed recently and finds this. I hope it helps them.
Last edited: