I'm having an issue and I have no idea what to do. I rebooted my Unraid server because I was moving up in the rack. Now when I boot up the server, I have no GUI. When I go to http://x.x.x.x in my browser I just get This site can’t be reached. x.x.x.x refused to connect. I tried rebooting and select to boot it to GUI using a local keyboard and I just get a _ at the top left of the screen. I reboot it into Safe Mode with GUI and I get that localhost cannot be reached. localhost refused to connect. One thing I do notice is in safe mode it is defaulting to HTTPS instead of HTTP and even if I turn of HTTPS-On-Always on the FF browser, it still goes to HTTPS. From what I can tell, my dockers, VMs and array all start up, but for some reason I can't get into the GUI anymore. I really don't know what to do or how a reboot did this. I'm so-so when it comes to linux CLI, but I can get into the server via CLI.

Attach Diagnostics ZIP to your NEXT post in this thread.

DIag zip

unraid-diagnostics-20260717-1423.zip

Can't see what's causing the issue, the GUI appears to start correctly after boot, but then it stops working. 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.

12 hours ago, JorgeB said:

Can't see what's causing the issue, the GUI appears to start correctly after boot, but then it stops working. 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.

The USB backup I have is from about a week ago when I changed from booting via USB to booting from an internal hard drive.

But I must of got lucky somehow, I powered down my server for about 5 minutes, reseated the USB and the connection to the internal boot hard drive and powered back up and luckily got the GUI back. I have no idea if the reseat of them had anything to do with it or not but after powering back up the GUI is up and running. Nothing I did make sense of why it would interfere with the GUI or help it get up and running.

I am running 7.3.2 servers and both have GUI go down after some random time. Rebooting fixes the issue, but only temporarily. I tried to troubleshoot with ChatGPT to no avail. Here is the latest syslog and the chatbots recommendations:

I reviewed the syslog. It confirms an extreme nginx reload storm—not a network failure.

From approximately 4:40 AM until the reboot:

• rc.nginx repeatedly launched overlapping reloads, sometimes 2–6 simultaneously.

• There are about 68,976 nginx entries and 5,240 rc.nginx entries.

• Concurrent reloads corrupted the generated servers.conf, producing duplicated server blocks.

• The storm consumed nearly the entire syslog, obscuring the original triggering process.

• This also likely explains why diagnostics stalled.

Now that Tower2 has rebooted, please check whether the storm has resumed:

date
tail -n 50 /var/log/syslog
grep -c 'rc.nginx' /var/log/syslog
grep 'rc.nginx' /var/log/syslog | tail -n 20

Also check for a scheduled script invoking nginx:

crontab -l
grep -RniE 'rc\.nginx|nginx.*reload|nginx.*restart' /etc/cron* /boot/config/plugins 2>/dev/null

If the count stays low and no new reloads appear, the reboot cleared the condition. I would then upgrade Unraid before touching Unraid Connect. If reloads are already accumulating again, we need to disable the responsible plugin or scheduled task before the GUI fails a second time.tower2-syslog-20260718.txt

So, looks like uninstalling Unraid Connect fixed the GUI crashing issue on both servers.

16 hours ago, levster said:

date
tail -n 50 /var/log/syslog
grep -c 'rc.nginx' /var/log/syslog
grep 'rc.nginx' /var/log/syslog | tail -n 20

I'm not seeing any evidence of a storm in the last 18 hours. And using those outputs there isn't anything that is filling up the logs. So it seems for me, the storm isn't happening at least now. How long after reboot did you lose GUI?

Both servers would lose their GUI after a few hours. I actually did not time them. But now, having removed the unraid connect, everything is fine.

After installing the latest version of the API no further issues have been noticed.