Hello. After updating to 6.10.3 from 6.9.2 both Main and Dashboard are at least partially broken and look like as visible on the attached screenshots. Has anyone else experienced this problem and knows how to fix it? It's kind of annoying as this is only a visual problem. Array itself works properly.

1 minute ago, Grok said:

After updating

Have you cleared browser cache?

Yes and it doesn't help. It is also happening only when accessing the UI through reverse proxy. When accessing directly, using IP, works fine.

Is your reverse proxy allowing websockets through?  (It's usually an option)

Allowing websockets and updating Nginx Proxy Manager did help with this issue. Thank you.

I have the same problem but enable websocket do not work.

Edited September 7, 20232 yr by Casadream_1

The problem is since 3 versions. 6.12.2, 6.12.3 and 6.12.4 I would like to find the functioning as before, the problem only manifests itself with Unraid. Services that require websocket work well, if I disable websocket the service does not work well, which shows that websocket works well with NPM except for unraid since a few versions.

 

I use NPM jc21

 

Thank you.

Edited September 7, 20232 yr by Casadream_1

I am facing the exact same issue with the new Unraid Version starting from 6.12. I am running 6.12.4 at the moment with NPM in Version 2.9.19 and websocket's enabled. The same issue as the original posted described. When I open unraid with local IP Address without proxy url, it is working perfectly fine. Any recommendations, what to do?

Short Update, also tried the latest NPM Version, with no luck. Any feedback is much appreciated. 

Edited September 8, 20232 yr by ph0b0s101

Please, development community, consider this.

 

I just found something.

If I go to the applications tab and come back to the dasboard.

Everything works as before, I also see the disks.

 

If I don't go to the applications tab, the disks are not visible and the dashboard is frozen.

Edited September 26, 20232 yr by Casadream_1

@Casadream_1 I can confirm, that this "workaround" will work for me as well. Wierd and maybe some kind of a bug. Thanks for sharing your finding!

By going to the applications tab, the freeze does not systematically disappear.

For it to truly disappear you have to scroll in the app tab.

Then at this point there is no longer any freeze.

 

Please, development community, consider this.

Yep, scrolling is mandatory to bring the functionality back.

up

It seems that this only concerns 2 people and therefore it is not interesting.

It's a shame.

I could imagine that this is because of that the topic was already solved and nobody get attention to it. What do you think? Maybe we should open a new bug report topic?

Yes, but I cannot recover the movies screen captures of the old message.

Hi there,  i have the same issue.. Login with local lan ip, no issues however thru reverse proxy NPM, same problem however also tried the "workaround" as explained above but didn't resolve the issue.  This problem accurred when updating to 6.12.3 /.4

same problem here. strange, but enabling websockets in reverse proxy and then visiting the apps tab and scrolling down seems to work.