Staff

Hello! It is normal with most (or all?) listening programs. They need an incoming unsolicited connection to determine that they can receive it, otherwise they obviously can't know (*). Therefore the decision of most designers is showing the port firewalled until evidence of the contrary comes in. Kind regards (*) unless they maintain an external infrastructure, have the client contact this infrastructure, tell it to send an incoming packet to verify... questionable and probably not worth the effort especially with a p2p software.

Hello! We're very glad to inform you a new 10 Gbit/s full duplex servers located in Stockholm, Sweden, is available: Segin. It will replace, with a more powerful hardware, Ain. Ain will be decommissioned on 2025-08-18. The AirVPN client will show automatically the new server; if you use any other OpenVPN or WireGuard client you can generate all the files to access it through our configuration/certificates/key generator (menu "Client Area"->"Config generator"). The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637, 47107 and 51820 UDP for WireGuard. It supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses. You can check the status as usual in our real time servers monitor : https://airvpn.org/servers/Segin Do not hesitate to contact us for any information or issue. Kind regards & datalove AirVPN Staff

Hello! We're very glad to inform you a new 10 Gbit/s full duplex server located in Bucharest, Romania, is available: Nembus. The AirVPN client will show automatically the new server; if you use any other OpenVPN or WireGuard client you can generate all the files to access them through our configuration/certificates/key generator. The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637, 47107 and 51820 UDP for WireGuard. It supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses. You can check the status as usual in our real time servers monitor : https://airvpn.org/servers/Nembus  Do not hesitate to contact us for any information or issue. Kind regards & datalove AirVPN Staff

Hello! We're very glad to inform you a new 10 Gbit/s full duplex server located in Miami, Florida (USA), is available: Dziban. The AirVPN client will show automatically the new server; if you use any other OpenVPN or WireGuard client you can generate all the files to access them through our configuration/certificates/key generator. The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637, 47107 and 51820 UDP for WireGuard. It supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses. You can check the status as usual in our real time servers monitor : https://airvpn.org/servers/Dziban Do not hesitate to contact us for any information or issue. Kind regards & datalove AirVPN Staff

Hello! Please be informed of the following, unavoidable scheduled power maintenance in Tokyo needed by our provider to maintain/replace Automatic Transfer Switch (ATS) systems. Start: Thursday, August 14th, 2025, 02:00 local time (UTC+9) End: Thursday, August 14th, 2025, 03:00 local time (UTC+9) The expected downtime is 30 minutes anywhere in the above mentioned time frame. The downtime will affect every and each server in Tokyo. Kind regards & datalove AirVPN Staff

@jedevnull Hello! Please make sure that the directives airusername and airpassword are correctly set in /etc/airvpn/bluetit.rc. Please check the manual: https://airvpn.org/suite/readme/#bluetit-configuration To have Bluetit start and connect during the system bootstrap, please see here: https://airvpn.org/suite/readme/#automatic-connection-at-boot-or-startup-time The AirVPN Suite User's Manual has been compiled with care and it's your friend. If you have already set all of the above and you still experience problems, please send us the Bluetit log too. Example: sudo journalctl | grep bluetit > bluetit.log Kind regards

@ThisisGabeB Hello! Before anything else, please discern whether the problem is caused by a failed WireGuard connection or not, by connecting WireGuard directly from the host, because similar problems which were initially thought as GlueTun bugs: https://github.com/qdm12/gluetun/issues/2458 turned out to be unrelated to GlueTun. Also check this one, just in case it helps: https://github.com/qdm12/gluetun/issues/2516 Read in particular this answer https://github.com/qdm12/gluetun/issues/2516#issuecomment-2602591109 Kind regards

Hello! In general you don't need IPv6 support by your ISP, but only by the system. Once connected you can use IPv6 (which will be tunneled over the VPN IPv4 connection) if needed. Kind regards

@alfavpn Hello! We see that most disconnections are either caused by an "unexpected status" or an "inactivity timeout". Sometimes you have 3 or more hours of continuous connections, sometimes only 45 minutes, so the matter is puzzling especially since you are connected via Ethernet (and therefore you suffer none of the problems caused by WiFi). What happens if you connect via WireGuard, and via Hummingbird? Do you see any difference? Kind regards

Hello! If Eddie is not running, system DNS addresses are correctly set and the firewall is disabled, then the connection inability must have a completely different cause and Eddie has nothing to do with it. Kind regards

Hello! For a quick discernment test please disable the firewall. You can turn off the firewall from the System Settings -> Network -> Firewall option. If the problem gets resolved then you know that it is related to the current firewall rules. In this case, please see also: https://support.apple.com/guide/mac-help/change-firewall-settings-on-mac-mh11783/mac If the problem doesn't get resolved, DNS settings must be checked as well. Please see here: https://airvpn.org/forums/topic/73821-cant-connect/?do=findComment&comment=253454 Kind regards

Hello! Your listening program does not reply to IPv6 packets, but only to IPv4 ones. Check the program settings and also verify that the program supports IPv6 and that the system firewall does not block unsolicited incoming IPv6 packets. Kind regards

Hello! Please make sure that Eddie is not running, check your system DNS settings and set publicly reachable DNS servers. We usually recommend Quad9: 9.9.9.9 149.112.112.112 2620:fe::fe for their commitment to privacy and neutrality. How to change DNS settings on macOS: https://support.apple.com/guide/mac-help/change-dns-settings-on-mac-mh14127/mac Kind regards

Hello, for the readers, explanation of the cause of the problem and quick solution on systems running firewalld: https://airvpn.org/forums/topic/70164-linux-network-lock-and-firewalld/ Kind regards

@jdelliott Hello! Thank you, we will investigate. It looks like the server sends IPv6 push even when UV_IPV6 environment variable is not sent out by the client. In the meantime can you please check a connection over WireGuard? Since there is no push with a WireGuard connection, but all the addresses must be set earlier on client side, the problem should not occur. Kind regards