Staff

@Air4141841 Hello! By muting the entries you would hide the problem but wouldn't solve it. Try with mssfix 1280 directive. It will tell OpenVPN to split TCP packets inside the UDP tunnel larger than 1280 bytes; if the problem is related to MTU this directive alone can greatly mitigate or solve it altogether. Kind regards

Hello! We're glad to know that you managed to solve the problem. Yes, for some reason their customer care could explain, Radmin interface blocks UDP connections. Eddie should not pick this interface for OpenVPN. For the readers: you can also tell Eddie to ignore any other interface by entering a valid name in Preferences > Networking > VPN interface name field (for example eddie) but, when Radmin runs, this solution could be insufficient. Kind regards

Hello! We consider redundancy in definite areas. Toronto is just 500 Km away from Montreal and offers ~37 Gbit/s as well as 10 Gbit/s availability. New York City is about 500 Km away and offers 10 Gbit/s lines as well. If you need redundancy in one single specific town you will not find it in all the towns (note that we mentioned "redundancy in most countries"), such as in Montreal, we're sorry, but please note that connectivity in Montreal remained available even if you had some less throughput. Unfortunately, in many cases this is impossible because it depends on factors that are out of our control. Common examples: a routing problem that needs to be detected, diagnosed and resolved by a datacenter's transit provider; an unknown hardware problem which needs to be determined first in order to decide which pieces to replace. EDIT: Ross is back online. Kind regards

Hello! We apologize for any inconvenience. We can't provide you with a definite time but we are confident that Ross will be back online in the very near future. Please do not rely on a single server, you will have a single point of failure. We offer a decent redundancy in most countries exactly to avoid your situation. Kind regards

Hello! No, they can't: OpenVPN and WireGuard are invulnerable to replay attacks in real life. Nevertheless a massive replay attack can dramatically slow down the VPN tunnel throughput because of the massive amount of packets that need to be dropped and re-sent. Kind regards

@hedgehog Hello! Some of the features you mention are essentially managed by Mono, can you please make sure you have an up to date package? If any problem persists, please test Eddie 2.24 beta version and report any persisting problem in this thread: https://airvpn.org/forums/topic/57401-eddie-desktop-224-beta-released/ Start from a default configuration please: before you install the beta version please delete the 2.21.8 configuration file whose location is ~/.config/eddie directory (you can delete anything inside that directory while Eddie is NOT running in order to wipe out any previous setting). If the scroll problem persists, please try to change font. When you report persisting problems please do not forget to mention your Desktop Environment name and version. Kind regards

@Ackei Hello! Insufficient information, we're sorry. What is the program you run to connect to the VPN? Can you post the log of such program taken after a connection attempt has failed? Kind regards

@drsergei Hello! WireGuard extracts the configuration file name to name the virtual network interface. The Configuration Generator generates names which are way too long for interface names. You will need to rename configuration files with very short names, with ASCII characters, before using them with WireGuard. Kind regards

Hello! Yes, definitely. More in general, the remote inbound port forwarding feature depends on forwarding and pre-routing set on the VPN server for all subnets and specific for each client, and therefore nothing changes if you switch connection protocol/port/type and/or connection program. Your setup is correct, we verified that your service is reachable through the VPN server while your system is connected to some VPN server. Keep Network Lock enabled to ensure no exposure of your inbound port on your physical network interface (i.e. your "real" IP address). Anyway, now you're connected through WireGuard and your port on the real IP address is not reachable, so it's fine. Kind regards

Hello! In many cases it depends on how many queries Google receives from the same IP address. It is plausible that some VPN user queries Google heavily with bots and such. When you want faster search via Google you can rely on https://startpage.com which will act as a proxy (it will give you back exactly Google answers) and save you from the captchas. As a nice side note you will have additional protection against Google profiling. You can also consider different search engines, a good one is https://search.brave.com Kind regards

Hello! The client-side problems could be caused by Plex service. In order to reach a Plex server, you may optionally use Plex services for registration, authentication etc., instead of pointing directly to the Plex server. In this case, if Plex service blocks any AirVPN server, you will not be able to access your own Plex server. Try to bypass completely any Plex service and you should be able to reach your Plex server from the Internet or from the VPN. Just in case you decide to connect to an AirVPN server even the machine running the Plex server, please check the documentation on inbound remote port forwarding and keep in mind that no matter how you configure it, Plex will always listen to port 32400 of your physical and virtual interfaces. Kind regards

@Radosk We're very glad to know that we meet all of your requirements, and we thank you for the appreciation and your compliments! Kind regards

Hello! Captchas could be mobile-specific in some rare cases. Do you get captchas if you use Chrome on the computer to browse the same web sites from the same VPN server? If the Android device connects to the same VPN server your computer connects to, do you still get captchas when you browse the same web sites? Also, what if you change browser in your Android device? If you can, also mention the web sites. Kind regards

Hello! We have identified the problem caused by a rare bug in the collision/duplicate check, therefore more than one user may potentially operate one name, and your case is one of the very rare ones. We are working on it to solve the issue. Now collisions are no more possible and we will have to take action for the current duplicates. In the meantime, for a quick resolution so that you can re-start operating immediately, please change your *.airdns.org names with some more unique strings. We still experience another problem with our first authoritative nameserver, so feel free to report any further anomaly. Kind regards

Hello! It's not so simple with more and more networks in public places trying to block VPN and Tor activities. Please test connection modes capable to bypass blocks, such as OpenVPN over SSH and OpenVPN over SSL: on Eddie's main window select "Preferences" > "Protocols" uncheck "Automatic" select a proper connection mode line (example some OpenVPN over SSH mode). The line will be highlighted click "Save" and test again connections in case of failure, repeat the procedure with a different port and/or connection mode (example SSL to port 443) Kind regards

@AirVPNUser2023 Hello! The problem for your own *.airdns.org domain name is now resolved. However, we're still experiencing problems on our primary authoritative nameserver. We are investigating. Please feel free to report any anomaly related to DDNS. Kind regards

Hello! We are going to investigate the problem. Kind regards

Hello! Don't worry, it's impossible that AirVPN will follow "this development", and after 14 years such doubts, or worse insinuations, are frankly inexcusable. The comparisons you make with some poor service with little value and lack of knowledge about Linux are a bit insulting. "Linux" in general is the main development platform for AirVPN and the backbone of the infrastructure, especially with robust distributions built on top. What's more, customers connecting via Linux are an irreplaceable part that totals, according to rough estimates, more than 30% of AirVPN customers (not counting Android here, which is anyway Linux based). Some major points showing how much we support "Linux" customers, regardless of the distribution they picked: AirVPN free and open source software is compatible with at least 200 Linux distributions and probably more. AirVPN software not only supports systemd based distributions, but also SysV Style-init and chkconfig based distributions (let's remember that more than 50 distributions are not based on systemd) . For leaks prevention, both iptables and nftables Netfilter components are supported Packages for most package managers as well as classical tarballs are ready for customer comfort, and Eddie is also available as an AppImage There is no feature for other systems which is not ported on Linux too, and not infrequently a feature is implemented on Linux first or simultaneously on all systems Linux is the only system for which multiple software by AirVPN is available: you can choose between Eddie (offering a rich GUI running swiftly on all major Desktop Environments) and the AirVPN Suite, which in turn offers a stand alone binary as well as a client-daemon architecture The AirVPN software is built not only for Linux x86-64 systems, but also for Linux systems based on ARM 64 bit, ARM 32 bit CPUs. Builds are also available for x86-64 legacy systems, ARM 32 bit legacy systems, and ARM 64 bit legacy systems OpenVPN3-AirVPN library development is led on Linux systems, only then the library is ported to macOS too AirVPN Configuration Generator is very friendly for any third-party Linux software, if you don't want to run AirVPN software in your Linux system Talking about bloatware, you will not find any on AirVPN. Additional features like DDNS or DNS opt-in filters never caused a price increase, and if you think about it DDNS is really comfortable for inbound remote port forwarding, it surely isn't bloat feature offered as marketing fluff. DNS filters have received a stellar feedback so we will maintain them (as usual, opt-in and at no price). Note how AirVPN pricing is the same since 2011 in spite of the useful features added since then. Kind regards

Hello! This is an error: in AirVPN the authentication takes place via certificates and keys. Please disable the username/password authentication. Kind regards

Hello! Thank you for your tests! We reproduce the problem and a fix is coming, you should see it on beta 2. Kind regards

Hello! The Express VPN network interface is causing a critical error, please see here for a quick solution: https://airvpn.org/forums/topic/56643-stuck-in-a-broken-route-never-connects/?tab=comments#comment-225323 Kind regards

Thank you! Eddie during system bootstrap may consult "Default" servers (according to the boot connection settings) to decide which server to connect to, while a "quick connection" (i.e. a connection initiated by tapping the big "on/off" button, or the button in the tile) does not consult this set but it considers "favorite" and "forbidden" server and country lists. We'll change "Default" label into something more descriptive and unambiguous. Kind regards

Hello and thank you for your tests! "Tile failure" when the app has not been launched since the device has bootstrapped is confirmed and it is now under investigation. We have been failing to reproduce the other issue. Can you send us a report through the paper plane icon in the "Log" view? Please generate it after the problem has occurred. The report will also tell us your exact Android version, device etc., as well the exact settings of the app, each tile and app's activity, so it is instrumental to understand the issue. Thanks! Side note: "default" servers are quite a different set from "favorite" servers. Connection during bootstrap may consult "Default" servers (according to the boot connection settings), while quick connection does not consult this set (but it must respect "favorite" and "forbidden" server lists). We'll consider to change "Default" label into something more descriptive and unambiguous. Kind regards

@Typhoon365 Hello! An "Earth" configuration is very generic, good to randomize around the world but not suitable at all for performance. Try to fine tune your choice to specific countries or servers. Each configuration file can point to a single server, a country or a continent, or you can customize for a specific set of servers. You can keep multiple configuration files, the generation phase is an almost "once and for all" operation which needs to be re-performed when you add new countries or servers or when you modify your client key(s). Kind regards

@OpenSourcerer is right, operating a server in Russia is detrimental and risky for the users. Since 2023 (and for specific cases since June 2024), datacenters / hosting providers are forced to connect their servers and routers to SORM-2 software and hardware equipment, so you have 100% certainty that any server in Russia is closely monitored and wiretapped through advanced Deep Packet Inspection, that all data and metadata are stored and correlated by the surveillance system in Russia, and such data and metadata can be accessed by many entities in Russia without a court order (a court order can be obtained pro-forma ex-post...). We do not agree with Proton decision (and we do not even understand it), even with SecureCore (a multi hop system) option. Moreover, SecureCore is opt-in, so a naive customer could connect to Russian servers directly. We firmly believe that not running servers in Russia is a correct decision preserving our customers' privacy and personal safety. Kind regards