4 hours ago, HDodd said:

So I completed the above and br0 is now back, but my VPN connection no longer shows up when adding/updating docker containers... It still shows up in the VPN manager, and is able to handshake/ping, but I can't connect any of my containers to the VPN now

When you head into the vpn manager, do a dummy change on the wireguard interface for it (put a 1 in the local name and remove it again) so that the apply button for that interface gets enabled, hit it and it will create the wg1 docker interface again

So I deleted my VPN and re-added it via a new imported wireguard config, and the network has returned. But now none of those containers can access anything else (Not the internet or other docker containers)

I'm going to get some rest before working on this in the morning, I'm planning on adding another tunnel with a different config in the morning to see if that does anything, but I'm not sure what's causing this separation from other containers...

 

Is there anything else I should try, or anything obvious I might be missing?

Edited March 1, 20251 yr by HDodd

7 minutes ago, HDodd said:

So I deleted my VPN and re-added it via a new imported wireguard config, and the network has returned. But now none of those containers can access anything else (Not the internet or other docker containers)

then the tunnel isnt running

The tunnel says that it's active and shows a very tiny amount of data being received and sent.

So I added a brand new tunnel (wg1) and tried using that with my containers, but I'm not able to access the webui of these containers at all.

Both wg0 and wg1 are active, but only wg0 gives webui access... any idea what could be causing this?

Okay after another restart the new tunnel seems to be running. I'm going to test a few other things before marking this as solved, but I think we're there

Thank you all for your help! I really appreciate it. It seems like everything is up and running now