HandyGuy

I was finally able to figure this out incase it helps anyone else. My issue is my unraid is on a subnet different than my laptop/desktop. The Unraid firewall for the vpn connection treats all ips on different subnet as "external" so replies to my desktop was going through the wireguard interface not allowed to go back to my desktop. So what solved it for me was the following that I add to User Scripts. If you don't understand below or it doesn't work straight away then I would just paste it to chat gpt asking how to figure out your docker gateway and the interface for the particular interface "shim-br0" #!/bin/bash ip route replace <my non server subnet>/24 via <docker gateway> dev shim-br0 table 200 || true

Hi, I came across SpaceInvader video https://www.youtube.com/watch?v=yBF9c0u2wCE " Route Containers Through WireGuard – Advanced Docker Networking" which seemed perfect for avoiding some headaches of dockers with vpn support. I happen to use PIA just like him so I followed all his steps and I see the VPN connection is established. However, when I configure my docker to use my new vpn interface from the docker perspective everything works. However, I am no longer able to connect to the docker webui on my desktop. Via Unraid command line, I can run curl to the webui ip and port which is the server's ip and the docker port 8080. But on my non unraid machine I can't access that webui. As soon as I switch the docker back to the bridge connection everything works again. Based on the VPN interface I can see traffic is being sent and received by the docker when its using the VPN interface. I'm curious if anyone seen this issue and have any potential solutions. I spent about an our with ChatGPT and couldn't get the problem fixed. I'm currently running Unraid 7.2.5 and the docker I'm testing this with is a new installation of linuxserver/qbittorrent. As a sanity check I tried this with handbrake to see if I could access the webui and that failed as well.