Search the Community

I'd been using Mullvad for years, but since they disabled their port forwarding feature I started looking for other solutions. Then I subscribed to AirVPN and although it's been so far a positive experience in general (I must say for example that I'm getting better speeds in AirVPN than Mullvad) there are a couple of issues that I'd like some guidance with, if possible. First I must say that I use OPNsense as my router/firewall. I downloaded and configured a Wireguard connection with the data I got from the generated file. It works ok. Very acceptable speeds, port forwarding also works as expected. But I've been having troubles accessing a number of sites that I really didn't expect. As for example I have a docker stack whose containers I simply can't download (ghcr.io) because of timeout errors (it gets downloaded as soon as I turn the vpn off). I noticed that I also can't access github.com due to timeout errors. Among a couple of other very known sites. Another issue is related to specific apps. Two examples: I use Nicotine+ (a Soulseek client) and it needs one forwarded port. When using Wireguard I noticed that although the port was correctly forwarded, people can't upload from me. In fact they see my available files and queue them, but upload speed is 10 Kib/s to 0. I tried to add a second vpn connection (OpenVPN this time) using the same preconfigured ports and it works perfectly with it, with good upload speeds. The second app is Eppi Cinema (a streaming Android app). It doesn't require any forwarded ports. When using Wireguard it either doesn't work at all or when works, speeds are so low that it's impossible to stream. If I use OpenVPN it works perfectly. Thing is I prefer to use Wireguard instead of OpenVPN. I noticed it is more stable and speeds are significantly higher. Any help or suggestion would be greatly appreciated.

I'm having some trouble with my current configuration, and I'm not sure what's going wrong. Here's my setup: Firewall: I'm using PFsense with the necessary ports open and NAT configured properly. (For now, it's open to the world for simplicity, but I'll restrict it later.) VPN: Deluge is running and shows the AirVPN IP as expected. Environment: OS: Debian Layered Stack: CasaOS -> Deluge (Docker) Despite this setup, something seems to be off. Deluge is running, and the AirVPN IP appears correctly, but connections don't seem to function as intended. Any idea of what am I doing wrong? Without the VPN was working fine the port forwarding locally

Hello! I'm trying to expose Jellyfin to internet through AirVPN port forwarding, but I can't for the life of me make it to work. You can see the gluetun stack I'm using bellow 45554 is the port I'm trying to use for Jellyfin. 42148 is the one I'm using for Qbittorrent. You can ignore this, it's working perfectly. I have no idea what I could be doing wrong, tried everything that came to my mind. In the AirVPN => Client Area => Forwarded Port, I tried to bind 45554 to "local port" 8096, without success. I'd really appreciate any help, Thanks for your time! services: gluetun: image: qmcgaw/gluetun container_name: gluetun cap_add: - NET_ADMIN devices: - /dev/net/tun:/dev/net/tun environment: - VPN_SERVICE_PROVIDER=airvpn - VPN_TYPE=wireguard - WIREGUARD_PRIVATE_KEY=xxx - WIREGUARD_PRESHARED_KEY=xxx - WIREGUARD_ADDRESSES=xxx - SERVER_REGIONS=Europe - FIREWALL_VPN_INPUT_PORTS=45554,42148 ports: - 8080:8080 # Qbittorrent1 - 42148:42148 # Qbittorrent1 port forwarding - 42148:42148/udp # Qbittorrent1 port forwarding - 8181:8181 # Qbittorrent2 - 6881:6881 # Qbittorrent2 port - 6881:6881/udp # Qbittorrent2 port - 8096:8096 # Jellyfin - 45554:45554 qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent1 environment: - PUID=1000 - PGID=1000 - TZ=Etc/UTC - WEBUI_PORT=8080 - TORRENTING_PORT=42148 volumes: - /home/charly/container/qbittorrent1/appdata/:/config - /home/charly/Téléchargements/:/downloads network_mode: 'service:gluetun' depends_on: - gluetun restart: unless-stopped qbittorrent2: image: qbittorrentofficial/qbittorrent-nox:latest container_name: qbittorrent2 environment: - PUID=1000 - PGID=1000 - TZ=Etc/UTC - TORRENTING_PORT=6881 - QBT_LEGAL_NOTICE=confirm - QBT_VERSION=latest - QBT_WEBUI_PORT=8181 volumes: - /home/charly/container/qbittorrent2/appdata/:/config - /home/charly/Téléchargements/:/downloads network_mode: 'service:gluetun' depends_on: - gluetun restart: unless-stopped jellyfin: image: jellyfin/jellyfin container_name: jellyfin network_mode: 'service:gluetun' volumes: - /home/charly/container/jellyfin/config:/config - /home/charly/container/jellyfin/cache:/cache - /home/charly/container/jellyfin/movies:/movies - /home/charly/container/jellyfin/tvshows:/tvshows restart: 'unless-stopped' environment: - TZ=Etc/UTC - PUID=1000 - PGID=1000

Hi, I have just finished setting-up a Flint2 router as a wireguard client. The Flint2 seats behind my primary router which provides it access to the WAN. I have downloaded a Wireguard config from the Config generator, loaded it and I can establish a connection with no problem. I have temporarily connected a PC to one of the LAN port and I can see that it's got the VPN IP when browsing. However when I test my forwarded port I get the following error: "Connection refused 111". Is there a specific FW rule in the Flint2 to set-up in order to accept incoming connections? Thanks for the help. T

Hello everyone, I'm a new user to AirVPN, and just installed Eddie, requested a port (random one) and connected to a VPN server (I've picked over 10 all over the world). Whenever I try to test out if port forward is working when I click "Test open" I always end up with Connection Timed out (110). I even tried Canyouseeme.org, same issue there. Does anyone knows why and what I'm doing wrong? I didn't have these kind of issues when I used Mullvad (before they removed Port forwarding)

Hello all, Anyone managed to set up amule with a HighID through wireguard? I run debian bookworm, I opened 3 consecutive ports and configured them in amule but I'm still a low ID. To make sure amule binds to the right interface (my wg interface is not the default one), I use https://github.com/JsBergbau/BindToInterface I am not sure what I did wrong. For qbittorrent I chose the wg interface and opened the port and it just works. Is this a limitation of BindToInterface, amule, airvpn? A bad setting somewhere? Thanks for reading me

Trying to use AirVPN port forwarding to do the following. I've got a wireless T-Mobile router which will not do port forwarding or NATing. I've gotten a ASUS RT-AC68U and configured it to work with AirVPN double-natted behind the T-Mobile router. I think I have the AirVPN set up right (I get access to the internet and it shows my IP to be a Canadian AirVPN server).What I can't figure out how to do is how/whether to configure port forwarding in AirVPN. I understand that I get the port and decide whether I want UDP or TCP or both and whether I want the same destination port or another - but there is no place to put the local LAN address of the box I want the port to have access to. Do I configure that in my Asus router? The WAN-NAT passthrough appears to be set up but I don't want to engage the virtual server or port forwarding module on the ASUS, do I?You can see I'm a little confused and would appreciate a hand here by someone who has done it before.

Hi I am looking to forward one of my ports through TCP on IPv4. I have connected to the vpn (tried both udp and tvp ports . Then setup Port Forwarding on the ports section. (BEWARE: My ISP has CGNAT so there's double a NAT that I have to punch through) Before connecting NetStat output is: Active Connections Proto Local Address Foreign Address State TCP 127.0.0.1:2657 view-localhost:2658 ESTABLISHED TCP 127.0.0.1:2658 view-localhost:2657 ESTABLISHED TCP 127.0.0.1:2659 view-localhost:2660 ESTABLISHED TCP 127.0.0.1:2660 view-localhost:2659 ESTABLISHED TCP 127.0.0.1:9349 view-localhost:11080 ESTABLISHED TCP 127.0.0.1:11080 view-localhost:9349 ESTABLISHED TCP 127.0.0.1:49736 view-localhost:65001 ESTABLISHED TCP 127.0.0.1:49740 view-localhost:49753 ESTABLISHED TCP 127.0.0.1:49753 view-localhost:49740 ESTABLISHED TCP 127.0.0.1:65001 view-localhost:49736 ESTABLISHED TCP 192.168.29.205:1029 eu-de01:50519 ESTABLISHED TCP 192.168.29.205:1294 20.197.71.89:https ESTABLISHED TCP 192.168.29.205:11333 20.54.37.64:https ESTABLISHED TCP 192.168.29.205:11343 172.67.202.182:https ESTABLISHED TCP 192.168.29.205:11368 ec2-15-207-57-185:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:10941 [2600:9000:2075:2000:a:15d0:77c0:93a1]:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11346 upload-lb:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11347 airvpn:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11353 [2606:4700::6812:126e]:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11354 [2a00:c6c0:0:154:4:d8aa:b4e6:c89f]:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11355 del12s08-in-x04:https ESTABLISHED After connecting to vpn output of netstat is: Active Connections Proto Local Address Foreign Address State TCP 10.16.55.31:11421 upload-lb:https ESTABLISHED TCP 10.16.55.31:11451 37.218.245.111:https ESTABLISHED TCP 10.16.55.31:11593 104.18.11.207:https ESTABLISHED TCP 10.16.55.31:11595 104.18.11.207:https TIME_WAIT TCP 10.16.55.31:11600 172.67.214.69:https TIME_WAIT TCP 10.16.55.31:11603 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11604 104.16.87.20:https ESTABLISHED TCP 10.16.55.31:11606 104.16.87.20:https TIME_WAIT TCP 10.16.55.31:11608 104.16.19.94:https TIME_WAIT TCP 10.16.55.31:11609 ams15s40-in-f3:https ESTABLISHED TCP 10.16.55.31:11610 ams15s41-in-f14:https TIME_WAIT TCP 10.16.55.31:11614 204.79.197.219:https ESTABLISHED TCP 10.16.55.31:11623 ec2-52-202-215-126:http TIME_WAIT TCP 10.16.55.31:11627 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11628 104.16.126.175:https TIME_WAIT TCP 10.16.55.31:11629 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11630 104.16.126.175:https ESTABLISHED TCP 10.16.55.31:11631 1:https ESTABLISHED TCP 10.16.55.31:11632 1:https ESTABLISHED TCP 10.16.55.31:11637 ec2-15-207-57-185:https ESTABLISHED TCP 10.16.55.31:11638 ec2-15-207-57-185:https ESTABLISHED TCP 127.0.0.1:2657 view-localhost:2658 ESTABLISHED TCP 127.0.0.1:2658 view-localhost:2657 ESTABLISHED TCP 127.0.0.1:2659 view-localhost:2660 ESTABLISHED TCP 127.0.0.1:2660 view-localhost:2659 ESTABLISHED TCP 127.0.0.1:9349 view-localhost:11080 ESTABLISHED TCP 127.0.0.1:11080 view-localhost:9349 ESTABLISHED TCP 127.0.0.1:49736 view-localhost:65001 ESTABLISHED TCP 127.0.0.1:49740 view-localhost:49753 ESTABLISHED TCP 127.0.0.1:49753 view-localhost:49740 ESTABLISHED TCP 127.0.0.1:65001 view-localhost:49736 ESTABLISHED TCP 192.168.29.205:1029 eu-de01:50519 ESTABLISHED TCP 192.168.29.205:1294 20.197.71.89:https ESTABLISHED TCP 192.168.29.205:11393 213.152.186.42:https ESTABLISHED TCP 192.168.29.205:11633 20.199.120.182:https ESTABLISHED TCP [2405:201:5003:40a7:3124:eb36:19c:e412]:11396 airvpn:https ESTABLISHED However Port Forwarding over tcp does not work ?

Hello, I have a couple of questions regarding AirVPN's port forwarding/DDNS service and the "new" multiple Device keys per user feature: From your "What is Dynamic DNS" section I can read: When a Premium member connects to an Air VPN server, the .airdns.org DNS record is updated to the exit-IP address of that server. Therefore, be aware that this service may be unusable when you establish multiple connections to different servers from different devices with the same account (in such cases, you need to point directly to the exit-IP address of the server, or use some third-party DDNS which you manually set). I understand how this worked before the multiple Device keys feature came into play but now we can have multiple devices connected to the same server, in which case my guess is that not even trying to point directly to the exit-IP address would make the port forwarding work. My suggestion is to relate de DDNS service to a Device key. For example, adding a "Device key" selector to the port forwarding menu. This way we would have 2 benefits. First, DDNS service would work as long as there were only one device using the related Device key, letting the user have some other connections at the same time. Second, even if a user ended up with a second connection to the very same server, the port forwarding feature would still work for the device with the proper Device key. Thanks in advance for your comments.

Hi I went to test out the port forwarding feature to open my NAT type for call of duty modern warfare 2, but my NAT type is still strict. I want to host some games but use a vpn so people will not ddos my home IP. The ports are: TCP - 3074,27014-27050 and UDP 3478,4379-4380,27000-27031,27036. Maybe I entered them incorrectly?

If I forward a port for my BitTorrent client, are my torrent downloads protected by the VPN?