alexfsr

Indeed i have figured out what's going on. You are correct, http://IPAddr works. The reason it wasn't working before was because i never write the http part, just the IP address in the browser field. Coincidentally, i remembered that Chromium based browsers started defaulting awhile back to https unless specified (and my server indeed doesn't have SSL because i could never figure out how to set it up properly. It never worked and caused the server to become completely inaccessible when i last tried to enable it with self-signed/generated SSL). Thank you!

Ok I tried to boot a fresh image of UNRAID configured from the disk imager with the same network settings (static IP, same IP as the original one). The fresh install was again refusing the connection when accessing via the IP address but it worked with "http://tower.local". After i setup a password and got to the main screen, i tried accessing the server with the IP address and it worked. I then went back and booted my orignal flash drive and that one also allowed the connection to the WebGUI via the .local domain. But it still refuses connections when using the IP address. What's going on? Seems to be something with the networking configuration but i don't see anything wrong with it and it hasn't changed since the last time i worked on the server and using the IP to access the WebGUI worked fine. I'll update everything now to see if it fixes but i really don't understand what's going wrong. EDIT: Running lastest stable verion of UNRAID now, all plugins updated. Docker and VM manager disabled. Still no access via IP.

Ok. That's not gonna mess up the HDD array, right?

I have never used the local domain nome to access the server, only IP (static). I don't believe my router is configured for it to work either but i can try it now. It's serverName.local , right?

Hi, I've been using UnRAID for a few years now for my family's NAS and Plex Server (docker). A while back, I also hosted a Windows 10 VM for my mom to use when she does her arts and craft (the server lives in the same room and it has more than enough power to handle light browsing and zoom calls). It has been working fine for a while but the Windows VM started having issues with the GPU recently (driver time out) so i decided to investigate during Christmas break. However, when i went to login to the server, i was faced with a "Connection Refused" error message. The server continues to work just fine as a NAS, all shares are accessible on the network. SSH works as well. But the webGUI is dead for no appearant reason. So far i have tried: Safe mode - No change. Renamed the virtual disk file for the VM to stop it from auto-starting on boot (i couldn't figure out how to stop it with virsh) - VM doesnt start anymore but GUI still missing. Changed the USB port of the boot flash drive. Checked the flash drive on another PC. It reads fine and seems to have all the server files on it as normal. Checked via local terminal with df command - the flash drive seems to properly mount at /boot. Generated a diagnostic zip with the command from local terminal - successfully saved to the flash drive and attached to this post. I don't know what else to do. This server hold a sh*t load of family data and I need to restore it ASAP but i have no idea what's wrong with it. Everything seems to be fine and works fine except for the web GUI. Any ideas? homenas-diagnostics-20230107-1825.zip