March 10, 20233 yr So I've had a working Unraid v6.11.5 with wireguard tunnel up (VPN for docker only) until today. Switched from xfinity to fronter, something that should have zero effect as far as Unraid is concerned. Powered down Unraid via GUI first, (needed to power down rack to route some cables), new WAN hooked up to router, powered Unraid server back on. No other changes other than new WAN DHCP IP acquired from router (OPNSense) After waiting for Unraid to fully boot up, my Wireguard Tunnel wg0 would say it was active, but no container set to use wg0 would actually send or receive data. Tried importing a new tunnel to test to see if it was just the wg0 config for some reason, but container also wouldn't work. Unraid itself was exhibiting some odd symptoms as well, Fix Common Problems would report that Unraid couldn't contact github.com (WAN was definitely up during this time). Attempted to just blast wg0 tunnels and start from scratch, I have just a wg0 with a fresh config loaded, and it _looks_ like it's active. The Problem is as soon as I enable docker, network problems start to occur. a basic ping to 1.1.1.1 stops working as soon as docker is enabled (screenshot showing as soon as I activated Docker, and remained unreachable until I disabled Docker), and that's without any containers that use the wg0 Tunnel running. Where should I look to figure out why Unraid networking suddenly went sideways after just switching WAN ips? (everything else on my network works) media-1-diagnostics-20230309-2320.zip
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.