Morning,

 

I embarked on an entirely unnecessary round of fiddling on my server because I decided that I wanted to be able to use unraid.home, cctv.home, films.home, plex.home etc on my local network to access all the docker services.  I've got this all working using Nginx Proxy Manager and Proxy Hosts forwarding these address to http://[Server IP Addredd]:[Port].  Everything resolves correctly and I don't appear to have any issues with any of that configuration.

 

But.  There's always a but with unnecessary fiddling!  Now when I visit the UnRaid GUI using unraid.home the GUI loads up, everything is working as far as I can tell but certain elements of the GUI are simply missing.  For example, on the Main page I can see the Array Devices list, the Pool Devices List, with the correct number of rows for the devices, but the rows are blank. No details for the device, identification, temp, reads, writes etc, can't click on anything, because it's not there.  Unassigned Disk Devices does list all it's items though! 

 

On the Dashboard page I can see details of all the Cache Pools, here the Array details are visible, the only place I can actually see the size and utilization of the array.  But the card for Parity is blank.  The Processor card is showing all the CPUs, but they all say 0% utilization all the time.  System card shows ram size, but everything relating to utilization is missing.  Interface card shows all the Network devices, but no information about them.  GPU card shows all devices and data.

 

Most other aspects of the GUI seem to be there, though I can't easily check.

 

Does anyone know what this is or how I can look at fixing it?

you have to enable websocket support


Edit: In case you have no clue how to do that in nginx, this needs to be in there
 

proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;

 

Edited February 15, 20251 yr by Mainfrezzer

Thanks so much, that was exactly the solution.  Nginx Proxy Manager has a check-box for websocket support, so that was a straightforward fix.