Leaderboard

I'm actively using port-forwarding and without issues. Except today The Bt client doesn't show as many incoming connections as it would if the port-forwarding worked. I've used this port for weeks and it has worked fine yesterday on this same server. Other than this anomaly, (I just checked, it was just a fluke. The website tester was unreliable) I've been using port forwarding without any issues ever since I got AirVPN. Adding a new port in the client area immediately enabled it for the current VPN connection (no noticable delay, no reconnect was required). On the topic of port exhaustion: splitting up forwarded ports per server/country would confuse A LOT of people. On the other hand those who know to configure port forwarding probably will manage through that hoop too. The only other way is to have an additional exit IP for each VPN to 'double' the amount of available ports (max. 2 allocations per port but then it would need to be static, so each user must be statically assigned into either group for routing)

@Obvious Hello! Incoming packet forwarding is a server side matter. It makes no difference whether the VPN connection is handled by OpenVPN 2,. OpenVPN 3 or Wireguard. In Linux and macOS, Eddie can run both OpenVPN and Hummingbird, which is an AirVPN software based on OpenVPN3-AirVPN library. You can tell Eddie to run Hummingbird and not OpenVPN by ticking "Use Hummingbird" item in Eddie's "Preferences" > "Advanced" window. On a client settings equal footing, packet forwarding behavior discrepancy between VPN servers should be investigated server side too. From your description it is possible that you're just wasting time as it appears that you're investigating incorrectly: please open a ticket. The support team can, first and foremost, ascertain whether packets are actually pre-routed and forwarded to your node or not. Kind regards

Hello! We inform you that all of our VPN servers in Maidenhead will cease operations on 03 September 2021. They will be replaced by servers in London featuring more modern hardware. Unfortunately, both technical and non-technical reasons force us to leave the current dc in Maidenhead. Servers in London are anyway located just 40 Km from Maidenhead and they will be announced and available in the next days. The new machines will keep the same names in order to support the old FQDN used by OpenVPN client profiles. Since the datacenter seems to have put offline already a server before the natural expiration date, we could put the new servers online before the mentioned 03 September date. When new servers are turned on, older ones with the same name will be disconnected from the infrastructure. This thread will be updated, if necessary, accordingly. The replacement servers are five, while the replaced ones are six. That's because we might be adding in the future another datacenter in UK in a different location. Kind regards AirVPN Staff