December 13, 2025Dec 13 So I had Unraid running on a small Beelink S12 system and it was running great, but this last week I got my hands on a much more powerful system for dirt cheap with a tower case that can actually fit all my drives directly in the system. So I got a few parts put together and everything install today and hardware wise everything is working perfectly. I moved over the Unraid USB stick and everything picked up great, and I was up and running...except none of my Docker containers were working. So I tinkered a bit, and eventually chocked it up to moving to a completely different type of hardware so I did a fresh install (both with the Unraid USB Creator and with the Factory Reset app) and notice when I install a container, instead of the VPN tunnel being avilable under the "Network Type" in the container (Custom: wg0) it has something else entirely (Custom: br0). I have been tinkering with it off and on for the last few hours and I have no idea how to be able to select the VPN Tunnel in the container.Note I did make sure the VPN tunnel is set up exactly as it was previously on the other system, both before and after the fresh install. The VPN tunnel is configured properly, and it works...I just can't get Docker containers to run through the darn thing.
December 30, 2025Dec 30 I just had the same thing happen to me when I added an additional drive to my server yesterday. What fixed it for me was creating a new Wireguard conf file and importing it in the "VPN Manager" section. It shows up in the "Network Type:" as "Custom: wg1". Now things are working as they did before, but I couldn't tell you what happened with "Custom: wg0"
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.