Hi. I've been trying to get this to work for some time without success, and through trial and error and scouring the forums here and on reddit, I have identified what the issue is. Many of the posts either haven't got this far, or have been able to do so but haven't posted a solution.

 

I want to be able to send individual container traffic through VPN using the UnraidOS built in VPN Manager. The 'VPN Tunnelled Access for Docker' option can achieve this. I can set up a Mullvad Wireguard connection, and through the console of an added container I can see that 1.1.1.1 can be pinged, and the IP address through ifconfig.io comes back as the exit node for the VPN. So I know the connection itself works.

 

The problem comes when trying to access the WebGUI of any connected container. It basically doesn't resolve, and I can't access the WebUI. I run a Unifi network, and have VLAN's segregating traffic. I have a 'default' VLAN which is the backbone, and my Unraid Server sits on that. I have a VLAN for trusted devices, and my MacBook sits on that. Ordinarily, the Unraid server and my MacBook sitting on different VLAN's doesn't cause any issues at all. I can access container WebUI's without a problem. But in the case of the VPN Manager, it doesn't work. But if I switch my MacBook over to the same VLAN as my Unraid server, I can access the WebUI no problem.

 

I haven't tested this, but I suspect if I were to remote access into my network via Unifi's Teleport, I wouldn't be able to access the container WebUI either, as Unifi puts remote devices onto their own VLAN.

 

I have tried adjusting the IP Tables in Networking, but I just caused myself more problems.

 

So I'm interested to hear from anyone who has solved this problem. Judging by all the posts I have read, there will be many other people interested in a solution too.

 

Thanks for your time.   

Bump. 

Where you able to figure this out as I'm having the exact issue?

Unfortunately not. I gave up on it in the end. I’m instead using GlueTun VPN, but that regularly needs restarting as the VPN drops out, which is annoying. I’m going to go back to my original solution, which is to use a container with VPN built in, and route everything through that instead. Not my preferred option. It could be so much easier and cleaner if the built in Unraid solution would just work.