I've posted this in the Wireguard Quickstart topic but am hoping it gets more visibility here.

 

My previous setup of pihole and wireguard with remote tunneled access worked flawlessly, and I was able to access my unraid server, dockers and the internet through the VPN. I have since updated to the latest unraid server version 6.11.3 and my pihole wireguard setup does not connect to the internet anymore. The current setup is with "Use NAT" = No and "Host access to custom networks" = enabled and static route setup as outlined in the Wireguard Quickstart guide. I am sort of stumped because I don't know what settings have changed.

 

I currently have access to my unraid server and its dockers but no access to the internet through the VPN. Pihole fixed IP is 192.168.0.10 and unraid server ip is 192.168.0.201. Below are my wireguard, TP-Link Router and pihole docker settings.

 

Wireguard:

TP-Link Router:

Pihole:

I have the exact same problem but have no previous setup (6.11.4) to know if it would work, so I'm not sure if its a unraid version thing or just doesn't work. The VPN does work if I ignore my static ip docker - I can get to the router, unraid, unraid bridge/host dockers. I have the route setup on my router for the VPN and unraid gateway. But my whole reason for setting this up is to add the pihole layer for blocking ads and tracking on my phone - which requires being able to access the static ip'd docker.

 

Something the quick start or the forum doesn't seem to address is the macvlan vs ipvlan, by default unraid uses ipvlan and there have been cases of people using this scenario successfully before 6.11.x on macvlan but not after.