[6.12.10] WireGuard VPN / VPN Manager won't activate after a peer was added

Hi there,

i am currently setting up the WireGuard VPN / VPN Manager.

Setting up the tunnel and activating it works up until i add a peer.

I set up the VPN Manager by mostly following the docs. Due to my ISP, i can only tunnel via IPv6 (at least i think so).

Settings are the following:
 

Name: MYNAME-VPN

Network protocol: IPv6 only

Local tunnel network pool IPv6: default (fc00:253:0:0::/64)

Local tunnel address IPv6: default (fc00:253:0:0::1)

Local endpoint: vpn.mydomain.tld:51820

Local server uses NAT: no

Local tunnel firewall: default (optional)

    Rule: default (Deny)

MTU size: default (automatic)

"Portforwarding" or Portopening is set up in my router for port 51820.

If you are wondering why the NAT setting is set to "no":

i am trying to set it up so i can access docker container with custom IPs. Currently that's only Pihole but i want it to be future proof.

For that i tried to set it up like the docs told me:

Quote

With "Use NAT" = No and "Host access to custom networks" = enabled and static route

- server and dockers on bridge/host - accessible!

- VMs and other systems on LAN - accessible!

- dockers with custom IP - accessible!
(Bingo! This is the recommended setup for complex networks)

My static route in my router looks the following:

IPv6-Network: fc00:0253:0000:0000:0000:0000:0000:0000

Prefix length: 64

Gateway: fc00:0253:0000:0000:0000:0000:0000:0001

I use a dynDNS Docker container (only IPv6) and my DNS provider is Cloudflare while every request goes to my NGINX Proxy Manager which worked flawlessly for HTTP(S) purposes. I don't know if it causes problems because the vpn.mydomain.tld may get blocked by NGINX?

I've read about a bug in 6.3 but that was 2 years ago.

Following questions emerge out of this:

Can you please help me set up the VPN correctly so it works?
Is my static route set right?

Thank you in advance for your help!

EDIT 1: typo

Edited June 22, 20242 yr by Sn4tz