[Solved] Web GUI not accessible after computer upgrade

[Ancalagon]

I just built a new computer, moving all the hard drives from my previous Unraid computer, all except the SSD cache drive, which I replaced with two new M.2 drives. I booted to my Unraid flash drive and all appears to have booted normally, ending on the login prompt as expected. But the Unraid web GUI is not accessible. The .local hostname resolves correctly to my unraid.net TLS domain. Going to the IP address directly also resolves to the unraid.net TLS domain. But the page fails to load:

 

This site can’t be reached

https://XXXXX.unraid.net/ is unreachable.

ERR_ADDRESS_UNREACHABLE

 

I can login at the terminal login prompt successfully. Pressing the power button signals the OS to shutdown gracefully. I tried rebooting and selecting Unraid OS GUI Mode. But when it finishes booting it goes to a black screen.

Edited May 8, 2021 by Ancalagon

[JorgeB]

Boot in normal mode, grab the diags by typing "diagnostics" in the console and attach them here.

[itimpi]

What version of Unraid are you using?   Recent motherboards are likely to need the 6.9.x release to have the needed NIC drivers.

[Ancalagon]

3 hours ago, itimpi said:

What version of Unraid are you using?   Recent motherboards are likely to need the 6.9.x release to have the needed NIC drivers.

 

I'm running the latest 6.9.2 version.

[Ancalagon]

It's a x570 motherboard, ASUS ROG Crosshair VIII Dark Hero, plugged into the Intel 1 Gbps NIC. I only have a 1 Gbps network switch, so reserving the Realtek 2.5 Gbps for now, but I could try plugging into that NIC as well.

 

5 hours ago, JorgeB said:

Boot in normal mode, grab the diags by typing "diagnostics" in the console and attach them here.

 

I'll grab the diagnostics.

[Ancalagon]

2 hours ago, Ancalagon said:

It's a x570 motherboard, ASUS ROG Crosshair VIII Dark Hero, plugged into the Intel 1 Gbps NIC. I only have a 1 Gbps network switch, so reserving the Realtek 2.5 Gbps for now, but I could try plugging into that NIC as well.

 

Same result using the other NIC.

[Ancalagon]

Here are the system logs. The end looks like this:

 

May  7 09:34:04 Hobbes root: Starting Nginx server daemon...
May  7 09:34:04 Hobbes avahi-daemon[4904]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
May  7 09:34:04 Hobbes avahi-daemon[4904]: New relevant interface virbr0.IPv4 for mDNS.
May  7 09:34:04 Hobbes avahi-daemon[4904]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
May  7 09:34:04 Hobbes kernel: virbr0: port 1(virbr0-nic) entered blocking state
May  7 09:34:04 Hobbes kernel: virbr0: port 1(virbr0-nic) entered listening state
May  7 09:34:04 Hobbes dnsmasq[6099]: started, version 2.84rc2 cachesize 150
May  7 09:34:04 Hobbes dnsmasq[6099]: compile time options: IPv6 GNU-getopt no-DBus no-UBus i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-cryptohash no-DNSSEC loop-detect inotify dumpfile
May  7 09:34:04 Hobbes dnsmasq-dhcp[6099]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
May  7 09:34:04 Hobbes dnsmasq-dhcp[6099]: DHCP, sockets bound exclusively to interface virbr0
May  7 09:34:04 Hobbes dnsmasq[6099]: reading /etc/resolv.conf
May  7 09:34:04 Hobbes dnsmasq[6099]: using nameserver 208.67.222.123#53
May  7 09:34:04 Hobbes dnsmasq[6099]: using nameserver 208.67.220.123#53
May  7 09:34:04 Hobbes dnsmasq[6099]: read /etc/hosts - 2 addresses
May  7 09:34:04 Hobbes dnsmasq[6099]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
May  7 09:34:04 Hobbes dnsmasq-dhcp[6099]: read /var/lib/libvirt/dnsmasq/default.hostsfile
May  7 09:34:04 Hobbes kernel: virbr0: port 1(virbr0-nic) entered disabled state

 

The last line doesn't look right, "entered disabled state". Nothing else stood out from the logs higher up. Both NICs seemed to initialize and bind together successfully.

syslog.txt

Edited May 7, 2021 by Ancalagon

[Ancalagon]

I just tested each NIC separately, disabling the other one in the BIOS. Same thing, neither worked still on its own.

[Ancalagon]

Here are the rest of the diagnostics, if that's helpful.

hobbes-diagnostics-20210507-0934.zip

[Ancalagon]

I can access the SMB shares and the files on them. I can also ssh into the server. So this really seems to be specific to the nginx web server for the admin GUI.

[Squid]

Try accessing via https://192.168.1.84 Then once in, update the DNS (or reprovision etc)  within Settings Management settings.

[Ancalagon]

2 minutes ago, Squid said:

Try accessing via https://192.168.1.84 Then once in, update the DNS (or reprovision etc)  within Settings Management settings.

 

Ah, yes, this did the trick! I was thinking along these lines, needing to reprovision the certificate possibly, but it just needed the updated DNS was all. Thanks for the help.