HDodd

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

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

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?

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?

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)

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

And even more strange is this: "Error response from daemon: network b3c2cf3baf6e not found" Even though the log specifically calls out that network above, it also claims it is not found... What do I need to do to recreate my docker image? Just delete the docker.img file and reinstall previous apps from CA?

Interestingly enough the network id is unchanged after restarting docker "Feb 28 17:32:39 mHDPC root: Error response from daemon: network di-b3c2cf3baf6e is already using parent interface br0"

Not sure if this is helpful, but here:

Would giving br0 a new subnet help? (192.168.3.0/24 instead of 192.168.1.0/24) I'd like to avoid that if I can, but I'm open to any options and really appreciate the help you all have given so far

I've checked all of the netowrks shown in the list and none of them show a parent of br0... here is the text from my console. I searched for br0 after inspecting every network and found nothing dockerNetworkInspectLog.txt

Okay, what do I need to do to identify which custom network is causing the issue? I've used 'docker network ls' to list them, but none of the IDs match with the above id you found. Are these re-generated every launch?

When I enter that into the console I get : "Error response from daemon: network br0 not found"

I just tried that and unfortunately nothing changed... Would checking the DHCP Pool checkbox help at all?