Greetings,

I like to ask the pros about an issue I ran in: I can´t access my server via webgui or ssh.

History
My system ran stable for several months and it was time to upgrade Unraid. Started upgrade, rebooted and parity became disabled. Shutdown, checked the disk on bios level, everything fine so far on an extended SMART-Test. Reboot, still disabled. OK, ordering a new disk, crap happens
Two days later Disk 2 started to fail with read-errors. Ok, another shutdown, another SMART-Test. But disk 2 appears to be fine, too. Hmm.
Digging through Internet and posts with the result that it could be anything from faulty power supply to misfortune. System was AMD Ryzen and pre-pandemic, power supply even far older, why not building up from scratch I thougth

New hardware specs:
Intel Core i3-12100
MSI B760 Gaming Plus WiFi DDR 4
NZXT C850 Gold
GTX 1070 (used from Ebay)
LSI 9300-8i IT mode (used from Ebay)

kept the RAM Kingsten Fury 4x 32GB

Assembled everything and booted. Looked good, server booting, couldn´t see any issues. Ready with the same ip as before, 192.168.0.110. That was the first strange thing because there was no ip reservation at all, should have gotten a new one from DHCP
Powerdown, reboot without network cable, 169.254..., seems correct. Reboot again with network cable, 192.168.0.110
Checked router (Fritzbox) TOWER appears twice with old and new connection, both  but different MAC. Powerdown, deleted both, restarted server. One connection named TOWER with 192.168.0.110 active

Seemed good so far, right?

But I can´t access the Webgui. I can´t SSH, not even ping it. Old board had two network cards so theoretically there could be a 192.168.0.111 but alas, same result. 

Created diagnostics.zip, checked it line for line but at least for me nothing seems to be out of the ordinary. And now I´m flabbergasted.

I´m a Windows tech for 25 years but on Linux I´m merely a slightly experienced noob. So I politly like to ask you for help and recommendations. Especially if I´m missing something dead obvious the whole time.

tower-diagnostics-20241123-1952.zip

Server has a static I set, delete/rename /boot/config/network.cfg and reboot to go back to default DHCP, then post new diags.

OK, it took a little bit. Renamed to network.old, rebooted, same IP. Checked the route again, deleted existing connection, rebooted router, rebooted server, still the same story. Here the diagnostics

tower-diagnostics-20241123-1553.zip

To sort things out I assigned in DHCP 192.168.0.110 to an non-existing device. Rebooted server, it now got 192.168.0.111 but still no webgui

You can try booting with a new flash drive using a stock Unraid install, no key needed, that will confirm if it's a config issue or an external problem.

Good idea. Will take a few days because I only own 1 USB stick atm

Sorry for the delay.

Created a new USB Stick with a trial install, Webgui reachable first try, same IP. Booted original stick again,  no webgui.

So there is something on the original stick that prevents the webgui access. Or the webgui itself. What could it be?

As said, gui worked fine on the old system.

tower-diagnostics-20241124-1217.zip

That suggests a config issue, 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, 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.   

I found the issue. The ident.cfg contained manual set ports. And it seems that the fritz.box is binding port-forwarding strictly to the MAC Adress and not to the IP. So with the new networkcard it tried to reach the webgui on the standard and therefore wrong port.

 

Thanks for your help and pointing me into the right direction.