I did some upgrades/sidegrades on my server, booted it back and everything was working fine for a bit. Only issue was that I had to use the network interface on the motherboard because the NIC I installed wasn't working (it kept coming up UPv4 not set...). I've switched eth0 and eth1 back and forth, active/backup, made one inactive and rebooted with both plugged in....the issue now however is that whatever I have done in my 'troubleshooting' (changing settings, rebooting rinse repeat, hoping something good happens) is that now I apparently can't get the server on the internet at all. LAN access is fine on one of the interfaces (the motherboard one), the other still comes in as IPv4 not set, but I can't get the server to see the internet at all. I'm really at a a loss. I feel I've probably done something dumb in my fumbling, but I would really appreciate anyone who could take a look at my diagnostics and tell me if they see anything wrong, or how to fix whatever it is I've done. 

 

The NIC was working fine before I made the hardware changes, for what it's worth. The hardware change in question is a new motherboard. New to me anyway.

 

tower-diagnostics-20250323-0123.zip

Try changing your DNS server to 208.67.222.222 and 208.67.220.220 instead of using your router.  Settings - Network Settings 

1 hour ago, JorgeB said:

Try changing your DNS server to 208.67.222.222 and 208.67.220.220 instead of using your router.  Settings - Network Settings 

 

I tried that on both interfaces and there isn't a difference. New diagnostics attached here just in case?

 

Another thing that may be potentially relevant, on the network settings page is keeps displaying "Interface Ethernet Port 1 is down. Check cable!". This is clearly not the case because I'm looking at the page over a LAN connection. I did try replacing the cable just in case, but that didn't change anything either.

 

Additional information: I found this thread and tried deleting the wireguard folder with no effect. I also have tried booting in safe mode, and that doesn't help either.

tower-diagnostics-20250323-0823.zip

Edited March 23, 20251 yr by aldumil
include diagnostics

28 minutes ago, aldumil said:

This is clearly not the case because I'm looking at the page over a LAN connection.

It could be true as the Unraid GUI is set up to work over eth0.

1 minute ago, itimpi said:

It could be true as the Unraid GUI is set up to work over eth0.

I've found in my searching that unraid will show that message if one of the interfaces doesn't have a cable attached, even if the other one does. I guess that isn't really a clue to my problem.

I feel like I'm taking crazy pills...I just keep changing the same few things and rebooting and nothing changes. It has somehow gotten worse though, now I can't even access the web GUI over LAN. It says it has an ipv4 address, but I can't connect to it from any computer.

 

Fresh diagnostics attached....I'm really losing my mind here. syslog

tower-diagnostics-20250323-0651.zip

Just to see if it helped, I just took the PCI card out. I just want to get the darn thing running normally, then maybe I can circle back to try and get an additional NIC working. One of the motherboard ethernet ports might not be working? When one of them is plugged in I still get the "no cable connected" warning message, but the other port makes that message go away. However I still can't access the GUI over LAN, or internet obviously.

Try renaming the two files that begin with 'network' by adding a new extension on them of   .bak

 

Then reboot your server with a keyboard and monitor attached.  When the Unraid boot menu comes select 'safe mode'.

? are you using tailscale ? this sounds like tailscale magicdns breaking the resolv config...

17 minutes ago, bmartino1 said:

? are you using tailscale ? this sounds like tailscale magicdns breaking the resolv config...

I was, but I've removed it to see if it helped. It did not. Is there something I can/should do to make sure any issues it was causing get removed as well?

25 minutes ago, aldumil said:

I was, but I've removed it to see if it helped. It did not. Is there something I can/should do to make sure any issues it was causing get removed as well?

not really. I've documented the issue and its issues and repair in this thread:

*At time of testing and infomring, live patches and chages were made... thorugh out unraid. including the use of resolv tail and head... and semi issue fixed with the rc network config that limetech /dev ship with... slackware and how unraid has things implemented are weird and the code has mutated to the point its legacy code...

If the tailscale plugin is uninstalled. (you may need to check and remove the tailscale binary...) and a system REBOOT! Then yes, your testing is fine. as tailscale with some options via the plugin that I have tested would break dns and internet access at the hos as it affect the resolve.conf as it replaces it. then it cascade into other dns internet related things with dockers eventually crippling the host ability to dns resolve.

this only if you atempted to use subnets and magicdns via tailscale...

what is the output of
cat /etc/resolv.conf

? if tailscale is mentioed at all then tailscale is still over writing the host config...

I recomend restarting the network config for unriad.

Disable dockers, disable VMs in settings.
Go to /boot/config and delete any file and config that says network 

then reboot unraid. this at boot recreate the default unriad network config. Unraid should network boot via DHCP and then reset and set your network settings.

other test are with curl to google.com and ping ona device that can to grab the ip and curl the ip... as it seems your having dns name resoltion issues not internet off lan traffic issues.

I recommend using your gateway as the 1st dns serve, a in home dns server like adguard/pihole and the tailscale magic dns 100.100.100.100
for testing...

so example
my home network is 192.168.2.x
gateway is 192.168.2.1

I would tell unraid to use 3 dns sdervers:

192.168.2.1 > the router/gateway
192.168.2.x > A dns server i run for my home network

100.100.100.100 or 8.8.8.8 or 1.1.1.1 or etc Public DNS 100 if planing to still use tailscale for dns