dukesmellington

I can second @MowMdown suggestion, rolling back the driver worked for me.

This may be a dumb question, but If I boot with a new flash drive, will settings and everything carry over? Also, thank you for your response and help. Ive been trying to wrap my head around this.

Hi everyone, I’m running into a strange issue with my Unraid server (IP 192.168.4.55 on VLAN 192.168.4.0/24). Symptoms: Plex starts but shows no libraries. The Plex Web UI logs show repeated failures to connect to plex.direct and plex.tv (timeouts). Community Applications fails to download the appfeed, with the error: “Last JSON error Recorded: Syntax error”. NTP (ntpd) is constantly retrying different pool servers but never syncs. From the Unraid shell: I can ping my router (192.168.4.1) fine. I cannot ping external IPs like 8.8.8.8 or 1.1.1.1 (100% packet loss). ip route shows a proper default route via 192.168.4.1. What I’ve tried so far: Verified that DNS servers are set in Unraid (8.8.8.8, 1.1.1.1). Checked syslog: shows DHCP lease and default gateway being set correctly, but every outbound attempt (NTP, rsyslog, Plex) fails. My other devices on the same VLAN (e.g., Mac at 192.168.4.112) have no issues reaching the Internet. Rebooted the server; issue persists. Environment: Unraid server on VLAN 192.168.4.0/24 Gateway: UDM Pro SE (192.168.4.1) Plex + Community Applications containers on Unraid What I suspect: Since other devices on the VLAN work fine, this seems isolated to the Unraid host. My best guess is that the UDM firewall or a policy-based route is treating 192.168.4.55 differently, essentially blackholing its outbound WAN traffic. What I’m looking for: Has anyone seen Unraid lose outbound WAN despite correct routes and gateway? Is there any Unraid-side config (bridge settings, bonding, docker networking, etc.) that could cause this? Any debugging tips specific to Unraid’s networking stack before I tear apart firewall rules on the UDM? Thanks in advance — I’ve been chasing this because Plex and CA both broke at the same time, and the logs make it clear it’s really an outbound connectivity issue from the Unraid host. syslog 3.txt syslog.txt syslog 2.txt