I've been a happy Unraid user for a couple of years now, however after updating to Version 7, I updated some settings which immediately caused my server's WebUI to become unresponsive.  It started after adjusting some power save settings, however I suspect I did more than that - just don't recall.

 

After the server rebooted, the WebUI, when attempting to navigate internally, looks like it used the UnraidConnect plugin.

 

I then attempted to use the Unraid GUI with a monitor connected, and the UI did not load there either.

 

I was able to access the Unraid Terminal after the server had booted (and interestingly, I could see the server in UnraidConnect, but could not access the Manage function).  While in server mode, I tried restarting the NGINX and the PHP services.

 

I did take a look at the diagnostics that it ran (copy attached), and it appears there might be something wrong with my Dynamix plugin...  I have a backup of the flash drive from before I upgraded to 7.x, and am looking for options before rewriting the flash drive with the previous version of my config.

tower-diagnostics-20250503-0726.zip

Same issue for me - though can't find anything about a Dynamix plugin, just NGINX crashing.

diagnostics.zip

Reboot is safe mode, if the same, post new diags.

6 hours ago, husqnz said:

Same issue for me

Please start a new thread, even if it's a similar issue, it can be a different problem, and it can get confusing to try and help multiple users in the same thread.

Thank you for your help, or for taking a look.  I restarted in Safe Mode, and had the same issue.  New diagnostics are attached.

 

I also recorded a short video of me attempting to login to show the behavior, not sure it'd be of any help.  I cleared the cache, and then attempted to log in via the ip address of the server, and it rerouted me to the error screen seen above.

 

tower-diagnostics-20250506-0700.zip

Edited May 6, 20251 yr by idahounraid

Try disabling SSL by typing in the CLI/SSH

use_ssl no

Then reboot, if still the same, you can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.    

I attempted that, rebooted in safe mode, and while now I get just an HTTP Error 500 "tower.local is currently unable to handle this request."  Of course, it's not doing the forwarding to myunraid.net.

 

I have a backup from mid-April, that I think I will try and restore to, when things were working, and I'll give that a shot.  Is it best to buy a new thumb drive for the restoration, or just backup the current, and overwrite the data on the current drive via the Unraid USB Tool?

Edited May 7, 20251 yr by idahounraid

You can use the same one.

did we clear the cache?

30 minutes ago, Tolete said:

did we clear the cache?

I did clear the cache...I presume you are speaking not of the Unraid server box itself, but of the computer attempting to access the WebUI.  Yes, I did that and tried multiple browsers.  In addition, I restarted in regular operating mode, and am able to see my dockers that are running, but still no WebUI.

5 hours ago, idahounraid said:

I did clear the cache...I presume you are speaking not of the Unraid server box itself, but of the computer attempting to access the WebUI.  Yes, I did that and tried multiple browsers.  In addition, I restarted in regular operating mode, and am able to see my dockers that are running, but still no WebUI.

By any chance are you using pfsense? if so, make sure you add to pfsense (Services > DNS Resolver > General Settings > Custom Options)

private-domain: "myunraid.net"

did you try ssh into the server  and remove the ssl yet?
 

1 ssh root@SERVERIP
2 use_ssl no

 

Edited May 7, 20251 yr by Tolete

I’m not able to SSH into the system, but was able to access via the CLI with a monitor plugged in.  It did seem to have an effect, as now when I go to my IP or to tower.local, it doesn’t redirect and takes me to the login url, but it gives me a 500 error still.

As a report - I was unable to get the errors corrected. I restored the thumb drive from a previous backup and that resolved the access issue. I do not know what a better solution would have been, but that seemed to work the best.