theseus

I know you posted this a while ago but I wanted to provide the fix just in cases someone experiences the same issue in future. Yes, there's an obvious fix. In the reactive resume template, click on 'Show more settings' at the bottom and you'll see both DISABLE_SIGNUPS and DISABLE_EMAIL_AUTH are set to 'true'. Set them both to 'false' and you're good to go.

I found the solution to my problem:

For extra context, everything else in the unRAID web UI is working. My array is up, all docker containers are running and I can browse throughout the entire unRAID web UI. When I enter the VPN Manager panel, I assume there should be more presented to me than just a non-clickable grey bar.

I downloaded my Mullvad VPN settings from my account and attempted to setup a new tunnel to run some containers into. I clicked 'Import Settings', selected the config file and now the VPN Manager page appears to be completely broken. See the screenshot below: https://imgur.com/mNwb3Om There are no buttons or any UI within that window for me to click. I can't remove, edit or do anything on this page. I assume that there should be some settings for me to add/edit/remove configurations but nothing appears here. I've rebooted the server, cleared my browser's cookies and cache and tried a different browser with no luck. ares-diagnostics-20241217-1108.zip

Update time. I managed to resolve this issue (I think) by just biting the bullet and recreating a new bootable USB with the UNRAID USB creator tool. I was running 6.12.8 which is strangely not available as an option so I visited https://www.unraid.gutt.it/ to download a copy and created a new USB. Fortunately I believe I managed to mount my drives as they were previously (my parity is the single largest drive and the other 7 drives are assigned from biggest to smallest) and it appears I'm up and running without issue.

OK, so after a short wait, I tried booting again and I managed to get the to command line. During the unRAID boot, it got a ton of errors stating the following: A quick Google search pretty much states that this means the USB is faulty (which we already know). I managed to get a copy of the diagnostics file on the USB (despite the numerous errors stating it's READ only) however as stated in my earlier post, none of my computers can read the contents of the USB so I'm at a loss on what to do.

Things are going from bad to worse. I spun down the server to attempt to boot into safe mode (not sure if that would have done anything). Upon restarting the server, I just get a black screen and it doesn't seem to be doing anything at all now. Unfortunately I read your post after spinning down the server and now I can't seem to get the system online at all. Not sure if this would have worked since the USB already appeared to be on its way out as the unRAID UI was throwing up errors stating that it was "Read only". As stated in my original post, both my macOS and Windows machines could not read the contents of the drive anyway. macOS's Disk Utility somehow managed to run OK on the drive and Windows Explorer hangs and eventually crashes when I attempt to view the contents of the USB. Looks like I may need to create a new bootable USB. Reading the unRAID documentation, it states this for those in my situation: As stated in the last sentence of the above snippet of the documentation, I unfortunately do not have any backups or photos of my drive configuration.

I was getting errors in my unRAID web UI informing me that the boot USB was read only. I figured the USB drive was going faulty so I powered down the server, removed the USB drive to attempt to clone it onto new hardware. I inserted the USB into both a macOS and Windows machine and both devices could not read the contents of the USB drive. I then tried to spin up my server again to backup the USB's contents via the unRAID UI and then I was prompted with an error saying something to the words of "Read only". I could not log into the web UI of unRAID. I spun down the server, removed the USB again and this time attempted to do a Disk Repair via macOS's Disk Utility. It completed successfully. I inserted the USB back into the server, booted it and it seems to boot OK as the command prompt shows the server's local IP address and says "Ares login:" as it normally does. The "Read only" error from earlier was not present. No computers or phones in my house can connect to the server. I can ping the server's internal IP address, but I cannot connect to it. How do I navigate around this issue?