Hi all. Looking for guidance for my Unraid GUI error.

Running 7.0.1 and ran into this problem last night. No dashboard web access, no login prompt. It just displays a white error page, "500 Internal Server Error" and "nginx" below that. I usually access my Unraid via this link, http://homer/Dashboard Using the IP instead of homer results in same.

Docker containers are still functioning and accessible. VM service disabled.

I do have SSH access via PuTTY. I have not yetrebooted, and copied the syslog (attached). Also attached is the nginx error log from /var/log/nginx

I reviewed https://docs.unraid.net/unraid-os/troubleshooting/diagnostics-information/ . But running "diagnostics" errors for me like this, "-bash: diagnostics: command not found". And which does not find diagnostics for me showing this, "which: no diagnostics in (/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin)".

I first found the condition last night before bed, in the 2200 hour. There was a User Script that was set to run at 22:03 that I wanted to check on. That script moves files between drives. Coincidence likely, but that's when I first saw the 500 error.

This morning I attempted "/etc/rc.d/rc.php-fpm restart" and "/etc/rc.d/rc.nginx restart". Those appeared to run successfully, and the 500 error persists.

syslog.log nginx_error.log

Edited August 12, 2025Aug 12 by Bait Fish
modified post title to include Unraid version, 2nd edit - Marked title solved

System stats plugin is causing errors; remove it or look for an update, but to get the GUI back you will likely need to reboot.

JorgeB, thanks for leading me to a solution. It seems so far not to have been the plugin.

I rebooted and removed the plugin as advised. The system ran fine until I again ran the (new, untested) user script I mentioned earlier. I was able to cause the 500 error immediately each time the script was run subsequently. And it caused the 500 error immediately each time. It seems it was causing i/o overload too quickly. Got rid of the offending operation and the script is again running and Unraid remains accessible.