Power was out an extended time and the server essentially had the power pulled from it as on 6/4/2024.
(This will be mitigated moving forward)

 

Status:
Docker is online and working
Webgui is unreachable
SMB shares are unreachable 
No VMS are in use (not an issue. I just don't use them)

SSH is accessible

 

Attempted Remediation and Results:
*Restored the USB backup from 6/3/2024 (after backing up the current USB) - same behavior
*Deleted the network.cfg and network-rules.cfg files - After reboot, I could reach the server on the new IP via SSH but not via the WebGUI. An authentication prompt came up when trying to access the file shares but no users which previously had access could log in to see the files.  (After this test, I restored the USB backup from 6/3/2024 again).
*Rebooted with local access in GUI safemode - unable to connect to localhost

*via SSH:  /etc/rc.d/rc.nginx restart Response: Nginx is not running

 

Last time I had a similar problem, I ended up building it back by pulling out the relevant config files for my disks and just rebuilding the config files for my docker containers. I'd like to avoid that if there is an easier fix. I also set up a consistent USB back up when I had a similar problem before as I thought that would allow me to quickly restore and be back online if I had similar problem moving forward. 

 

Edited June 5, 20242 yr by tinymegalodon

The array is not started, so no shares is normal, but the GUI should be wotrking as far as I can see, try booting with a new flash drive using a stock install, if the GUI works, you can try redoing the flash drive, backup the current one first and then redo it 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, 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 just realized when you said the array wasn't started that I had the Unraid server booted in safe mode.

 

When I boot it up normally, the array does start. I have rebooted and attached the diagnostics for a normal running state. Anything stand out to you here?

 

Edited June 5, 20242 yr by tinymegalodon

I've now tried the following:

• restored the USB backup 6/3/2024 to a separate flash drive. No web GUI. No joy.
• restored a previous USB backup 5/27/2024 to the licensed flash drive. No web GUI. No joy.
• restored a previous USB backup 5/20/2024 to the license flash drive. No web GUI. No joy.
• I reinstalled the base image and copied over the ENTIRE config folder (hoping for damage outside this folder). No web GUI. No joy.
• I reinstalled the base image and copied over ONLY Plus.key, super.dat, pools folder, and shares folder. WebGUI booted right up.
• I then through a few reboots copied over disk.cfg, docker.cfg, domain.cfg, ident.cfg, network.cfg, network-rules.cfg, random-see, secrets.tdb, and smbpasswd. The WebGUI still booted right up.
• I reinstalled the base image and copied over all loose files from the config folder along with the pools and shares folders. The webGUI still came up. The array started successfully automatically.
• I shut down and copied over the full plugins folder. Everything now seems to be working normally after rejoining the server to the active directory environment.

 

Unfortunately, I haven't pinpointed the problem to easily correct it if there is a next time. If anyone has any ideas, I'm game to do some troubleshooting.

Edited June 5, 20242 yr by tinymegalodon

So apparently, this is a lingering issue from the last time I rebuilt the server. It was an malformed SSL cert that was keeping the the WebGUI from booting. I did not have SSL on but there was something screwy with a malformed cert that was preventing nginx from starting.

 

In the end, I restored the 6/3/2024 backup one last time.

I renamed /boot/config/cert to /boot/config/cert.old

I reviewed /boot/config/ident.cfg to ensure that SSL="no" (it was already)

Then I was able to restart my server with the backup from 6/3/2024 and access the WebGUI.

 

I was hoping to help myself and the community with this one but it looks like this was a very niche problem that most people wouldn't have. Anyhow, that's how it all turned out.

 

If you want to check and see if this is your problem, you can run the command:

 

nginx -s reload

 

If this gives you a warning, no problem. If it gives you an error, it will not allow access to the WebGUI.

Edited June 5, 20242 yr by tinymegalodon