Cannot access WAN IP from Wireguard full tunnel

[Gio]

Hi guys!

I've been trying to setup Wireguard today and I'm running into a problem.
I have followed the complex setup steps from this topic: 

 

Mostly it is working except for 1 thing.
I've got the static route setup and I can access the static docker IP's (in my case 192.168.1.13) just fine and I can access the internet with NAT turned off for Wireguard.
But what doesn't work is connecting to my WAN IP.

I have Nginx Proxy Manager setup that listens to port 80 and 443, I use it for services such as Plex, Sonarr, Radarr and more.
This works just fine using the split-tunnel (Remote Access to LAN) and it also works fine when on my home network.
But when I connect using the full tunnel (Remote Tunneled Access) it keeps loading and loading.
Going manually to the ports (192.168.1.10:80/443) works just fine, but going to my WAN IP it stops working.

What works:

192.168.1.10:80

 

What does not work:

45.45.45.45:80 (WAN IP)

proxy.domain.com (points to WAN IP too)

 

I have tried setting up a static route for 45.45.45.45/32 in Unraid and point it to 192.168.1.1 (router) but it does not work.
Pointing it to Unraid or the br0 network doesn't work either. 

The proxy is setup in a custom bridge network (178.18.0.0).

Anyone have any idea?

 

Edit: when using NAT and no static route it works fine, I just can't connect to 192.168.1.13 (custom docker bridged network) anymore.

Edited September 4, 2023 by Gio