Help with Ports

[Pilly 0]

Any port that is choose when connected to VPN via Wireguard says cant connect Connection timed out (110)

Any way of making this work?

[Staff 10346]

@Pilly

Hello!

Please start from here:
https://airvpn.org/faq/port_forwarding/

Follow this checklist if you experience any problem:
https://airvpn.org/forums/topic/66388-port-forwarding/?do=findComment&comment=243305

Kind regards
 

[Pilly 0]

Hi again 👋

 

After some more testing I think I’ve figured out what’s going on, but I’d like confirmation from the AirVPN team.

 

Here’s my setup:

 

• UniFi Gateway (UCG) running a WireGuard VPN client

• Endpoint: gb3.vpn.airdns.org (AirVPN)

• Traffic Policy: all traffic from my NixOS server is routed through the AirVPN tunnel

• Application: qBittorrent on that NixOS VM

• Port Forwarding: I generated a port in my AirVPN client area (for example 38649) and set qBittorrent to listen on the same port with UPnP/NAT-PMP disabled

 

 

The VPN works fine — my IP shows as AirVPN’s (e.g. 37.120.x.x), and speeds are good —

but no matter which port I assign, qBittorrent and every external port-checking site still report the port as closed.

 

From what I can tell, UniFi’s built-in WireGuard client connects using only the raw keypair and doesn’t provide AirVPN with any device certificate or account identifier, so the AirVPN server can’t associate my active connection with the port forwards in my account.

That would explain why inbound packets never reach my NixOS VM even though the tunnel itself works for outbound traffic.

 

Can anyone confirm whether AirVPN’s remote port forwarding currently works with third-party WireGuard clients on routers (like UniFi)?

And if not, is there any way to manually link my UniFi WireGuard public key to a “device” in my AirVPN account so the forwarded ports (e.g. 38649) can be tied to that tunnel?

[Staff 10346]

1 hour ago, Pilly said:

UniFi’s built-in WireGuard client connects using only the raw keypair and doesn’t provide AirVPN with any device certificate or account identifier

Hello!

The keys are key here.  AirVPN infrastructure knows who you are from your key and knows your VPN IP address according to that key (as WireGuard doesn't support DHCP). Your account remotely forwarded ports are linked to "All devices" or to "Default" device, which is the only key you have, so the problem must lie elsewhere. If your NixOS VM is attached to the host via NAT, please make sure that the incoming packets are properly forwarded by the host to the final VM running qBittorrent.

Kind regards