I added a new 2.5gbps NIC, swapped the eth0/eth1 devices, and rebooted along with swapping the connection to the new NIC.

Now I'm getting some strange network errors.

Fix Common Problems reported that it can't connect to Github, and my docker images can't find updates

There is an error message from Unraid Connect:

"NETWORK: getaddrinfo ENOTFOUND

mothership.unraid.net CLOUD: socket closed"

unsure if related, but my main user for Plex can't see my libraries, while switching to a managed user will let me see my libraries.

How to I fix my network settings?

tower-diagnostics-20260126-0033.zip

Edited January 26Jan 26 by veri745
clarified changing connection to new NIC port

Diags show conenctivy issues, try changing your DNS server to 208.67.222.222 and 208.67.220.220 instead of using your router. Settings - Network Settings

I don't think it's a DNS issue, I can't even ping 8.8.8.8 from the main console

From my docker containers (Sonarr, Radarr) I get both DNS resolution and connectivity:

sh-5.3# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=110 time=30.2 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=110 time=28.5 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=110 time=31.4 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=110 time=29.6 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 28.544/29.922/31.420/1.039 ms
sh-5.3# ping google.com
PING google.com (142.250.190.46) 56(84) bytes of data.
64 bytes from ord37s33-in-f14.1e100.net (142.250.190.46): icmp_seq=1 ttl=110 time=20.1 ms
64 bytes from ord37s33-in-f14.1e100.net (142.250.190.46): icmp_seq=2 ttl=110 time=21.1 ms
64 bytes from ord37s33-in-f14.1e100.net (142.250.190.46): icmp_seq=3 ttl=110 time=22.6 ms
64 bytes from ord37s33-in-f14.1e100.net (142.250.190.46): icmp_seq=4 ttl=110 time=19.2 ms
^C
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms

From main console, I get nothing:

root@Tower:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
42 packets transmitted, 0 received, 100% packet loss, time 41984ms

root@Tower:~# ping 192.168.5.1
PING 192.168.5.1 (192.168.5.1) 56(84) bytes of data.
^C
--- 192.168.5.1 ping statistics ---
135 packets transmitted, 0 received, 100% packet loss, time 137210ms

47 minutes ago, veri745 said:

I don't think it's a DNS issue, I can't even ping 8.8.8.8 from the main console

From my docker containers (Sonarr, Radarr) I get both DNS resolution and connectivity:

That suggests a config problem, try booting with a new flash drive using a stock Unraid install, no key needed, and see if the connectivity returns.

Also post a screenshot from Settings - Network Settings - Routing Table.

Try binding the old nic to vfio. Should make it disappear as far as unRAID is concerned which will make your new nic the default.

Not 100% sure, but I think this could be a problem; try changing that metric to 1, that's the default:

2 hours ago, Veah said:

Try binding the old nic to vfio. Should make it disappear as far as unRAID is concerned which will make your new nic the default.

I tried enabling IoMMU to try this, but for some reason it won't boot from my flash after enabling it.

5 minutes ago, JorgeB said:

Not 100% sure, but I think this could be a problem; try changing that metric to 1, that's the default:

How do I change it?

Settings - Network Settings - eth0

The metric is below the default IPv4 gateway field

45 minutes ago, JorgeB said:

Settings - Network Settings - eth0

The metric is below the default IPv4 gateway field

Tried this, also disabled VPN to simplify the routing table. Still nothing.

I really don't understand how I can access my server via the network, but it can't ping or seem to access my router in any way? How does that even make sense?

Do you by chance have the old Mac address associated with your IP on the router?

20 minutes ago, Veah said:

Do you by chance have the old Mac address associated with your IP on the router?

‼️

OMG, yes updating the MAC on the static DHCP resolved this issue.

I guess I still don't understand why some things were working and others not, but I'll count that a win.

Edited January 26Jan 26 by veri745