ANSWERED Can't access server from laptop when both are connected to AirVPN

[hifiboombox 0]

I have AirVPN (with wireguard) set up and working great on my server. A torrent client running on the server is routing its traffic through the wireguard interface, and I can access all the services running on the server through my DDNS (MYSUBDOMAIN.duckdns.org).

I also have AirVPN (with wireguard) set up and working great on my laptop.

Now the problem is: I cannot access my server (through MYSUBDOMAIN.duckdns.org) on my laptop while my laptop and server are both connected to AirVPN. I can only access my server If I disconnect my laptop, or my server (or both of course) from the VPN.

I was wondering if it has something to do with the MYSUBDOMAIN.duckdns.org URL itself. When I run the route check tool on "MYSUBDOMAIN.duckdns.org", every single server fails to connect to MYSUBDOMAIN.duckdns.org

I guess I should also mention, my laptop and server are both on the same LAN. If my laptop and server are both connected to AirVPN, I can still access my server from my laptop if I use the server's local (192.168.1.X) IP address. But I really would prefer to use the MYSUBDOMAIN.duckdns.org address instead.

How can I fix this?

Attached is a screenshot of the route checking tool saying every server failed to connect to MYSUBDOMAIN.duckdns.org.

[Staff 10171]

7 hours ago, hifiboombox said:

screenshot of the route checking tool saying every server failed to connect to MYSUBDOMAIN.duckdns.org.

Hello!

The route checker tries ports 80 and 443 so the failure is due and expected. Please make sure that your domain name resolves into the correct IP address and that you point to the correct port(s). Please note that we can reach your listening program on the proper port (the only port you have remotely forwarded on your AirVPN account port panel) but only over IPv6, and not over IPv4. Maybe the torrent client "listens" only to v6.

Kind regards
 

[hifiboombox 0]

The route checker should have worked then, I have a website running on port 80. I managed to completely fix my problem with these settings in /etc/wireguard/wg0.conf:

    PostUp = ip rule add from 192.168.1.0/24 table main
    PreDown = ip rule del from 192.168.1.0/24 table main

This comment has a fuller explanation: https://www.reddit.com/r/WireGuard/s/YRZnEVRmua

Edited ... by hifiboombox

[Staff 10171]

46 minutes ago, hifiboombox said:

The route checker should have worked then, I have a website running on port 80.

Hello!

You said that the services had to be reached while the system is behind the VPN through an FQDN, and port 80 can not be forwarded. In such a scenario the failure is expected and due.
 

48 minutes ago, hifiboombox said:

I managed to completely fix my problem with these settings in /etc/wireguard/wg0.conf:

So you needed to bypass the VPN. We assumed the contrary, i.e. that you wanted your services (torrent etc.) "protected" by the VPN, hence the misunderstanding. All good then!

Kind regards