March 2, 20251 yr (Unraid 7.0.0) I am new to unraid, so please forgive my ignorance on this one. I noticed the time was off by a few hours in unraid, so i enabled NTP from unraid settings and hit Apply (did not submit a var for an NTP server; i believe this was my mistake). Unraid showed the loading/apply squigglies, but they continued ~5 minutes. this seemed like too long to wait for a clock update, so i hard reset the system (probably another mistake here) . after waiting for boot, navigating to the web UI for login shows a blank white screen (not failed to load/404/504/500/etc., but loads a white screen). watching the scrolling logs during boot for unraid looks like it is booting successfully, and shows the normal info in the cli after successful boot, including unraid version, ipv4 address, login prompt, etc. - i am able to access the server cli, login, and have root access from here. Because NTP was the thing i changed immediately before having this issue, I think this is the issue, but hopefully it is not a red herring. Is there documentation on disabling NTP (or accessing settings config) via the CLI? I have been having a very hard timing finding cli help for unraid. I am also open to any other suggestions for things to try to get this up and running; however, i would like to keep the data on the drives... some of it is irreplaceable (i haven't setup an offsite copy yet )
March 3, 20251 yr Community Expert Not sure that would be enough to crash the GUI, but edit /boot/config/ident.cfg and change USE_NTP="yes" to "no", then reboot.
March 4, 20251 yr Author thank you for that info. sadly, changing the ntp setting (thank you for showing me where that was) did not change the white screen issue; it was a red herring.
March 4, 20251 yr Community Expert 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.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.