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

Do you get the same accessing the server by IP or name?

4 hours ago, JorgeB said:

Do you get the same accessing the server by IP or name?

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?

Yes, but if the IP doesn't work name is likely going to be the same, try with a new flash drive with a stock install, no key needed, just to see if it's a config problem. 

6 hours ago, JorgeB said:

Yes, but if the IP doesn't work name is likely going to be the same, try with a new flash drive with a stock install, no key needed, just to see if it's a config problem. 

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

No, just don't assign any disks.

6 hours ago, JorgeB said:

No, just don't assign any disks.

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.

Edited January 9, 20233 yr by alexfsr

10 hours ago, alexfsr said:

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.

This doesn't make much sense and sounds like an internal network problem to me.

 

 

On Settings -> Management Access, your "Use SSL/TLS" setting is set to "no".

 

With that setting, I would expect this to work:

  http://192.168.104.11

but not this:

  https://192.168.104.11

(note that one is http, the other is https)

4 hours ago, ljm42 said:

On Settings -> Management Access, your "Use SSL/TLS" setting is set to "no".

 

With that setting, I would expect this to work:

  http://192.168.104.11

but not this:

  https://192.168.104.11

(note that one is http, the other is https)

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!

Yeah browsers are complicating things by assuming https. If you are happy with http for the webgui that is fine, if you want to use https Unraid offers two options:

* a self-signed cert (which browsers also complain about)

* a Let's Encrypt certificate on a custom myunraid.net url (no complaints from browsers)

 

Instructions are here:

https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29 

 

...

 

FYI, now that you are on Unraid 6.11.5 you can go to Settings -> Management Access and get a list of the Local Access urls valid for your system.  With current settings you should see:

* http://ipaddress

* http://HomeNAS

As you change settings to enable SSL, this list of urls will change.

 

I highly recommend that you go to the Apps tab and install the "Fix Common Problems" plugin, it will let you know if there are any common configuration problems you should fix. It will have a suggestion for your "Local TLD" setting.

 

Hi there, I am experiencing a similar but different problem. My plex server (Binhex - plex) stopped working early this morning. When I checked unraid the docker had disappeared. The files were still in the AppData folder, so I went to the apps and reinstalled the container from the recent apps. All the setting looked good and the docker was running. When I tried to access the web UI, I got an error message, "This site can’t be reached" and "Connect refused." when I reexamined the docker container settings I noticed that under the docker allocations, the plex docker had three question marks "???", while all the other containers each have unique ports. Please refer to screen capture;

 

  

 

Additionally, I noticed that under the dockers tab is no "port mapping"being displayed prior to this issue, please refer to screen capture ;

I have attached the general diagnostic log, the plex server log, and a sample of the superord.log that references the crash. I hope that it helps with identifying the issue.

 

If you have any suggestions on how I can fix this issue, I would greatly appreciate them.

 

Thank you.

 

 

 

 

 

 

tower-diagnostics-20240923-1144.zip Plex Crash Uploader.log

20240923 supevisord.log sample.txt

Edited September 23, 20241 yr by brownsugar
Needed to add additional information and an attachment that may clarify things for the reader.

The worst system I've ever had. At random times it denies access, both to the management page and the services running on it, docker, vm, ssh.
It responds to ping. I've already spent two days investigating what the problem is and I haven't found any connection to anything.
In the meantime, qnap in the same network is working without a problem.
I don't expect any response, I just wanted to share that this was the worst money I've ever spent.
Thank you for your attention and best regards.

1 hour ago, Radiska said:

Thank you for your attention

Attach Diagnostics to your NEXT post in this thread.