Started this morning, I can’t access any service, such as updates, apps catalog, ping, curl, anything that requires network. VMs working fine, Plex running fine too.
If I try to ping google I get “ping: google.com: Temporary failure in name resolution”, trying to check for updates I get “[ETIMEDOUT] Connection timeout while fetching update manifest” If I try to access the app catalog I get “Failed to sync TRUENAS catalog”
Date and time are set (BIOS set to UTC), the gateway is set to my router, DNS servers are set to Cloud Flare DNS (also tried Google, no change)
Can you ping 1.1.1.1 from your desktop command line? If so, that verifies that your IP connection / router / and route to Cloudflare are likely working. Then it becomes a DNS resolution troubleshooting issue.
So this used to work?
Did you do any changes recently, including doing something seemingly innocuous like reboot, install/configure a VM or similar?
What IP are you accessing the server on?
enp133s0f0 having it’s own IP when it at the same time is part of br1 is unexpected. I would start removing the IP from the physical NIC.
Have you tried rebooting since this happened?
Do you have console access using a keyboard and monitor? You should be able to access the network settings using that.
I rebooted this morning, but everything else was the same. Tried several reboots. Nothing seems to work. I have console access, I have tried removing and resetting all network devices too.
I don’t know about removing and resetting, I just recommended that you remove the IP that is currently linked to your physical network interface, since that’s an invalid configuration given that the NIC is a member of br1.
If you haven’t changed anything in your TN network config and you can ping from the CLI and VMs in TN, then it’s likely to be one of the following items:
The DNS resolver IP is not configured properly in TN (‘cat /etc/resolv.conf’ from the CLI to check the TN DNS configuration.)
The configured DNS resolver is down.
Port 53 is being blocked on your network to TN (possibly a routing/firewall issue.)
