Staff

Hello! Confirmed, unfortunately. We're investigating and a fix will be implemented in the next release. Thank you very much for the report. Kind regards

Hello! A first non-fatal problem comes from directives not recognized by the probably old OpenVPN version used by this Tunnelblick version, but the configuration file is sanitized. Should you need to generate configuration files already compatible with OpenVPN 2.4, in the Configuration Generator make sure you select "Advanced Mode" and then in the "OpenVPN version" combo box select ">= 2.4". The Configuration Generator will then generate configuration files compatible with OpenVPN 2.4.x. Then the fatal problem should be this one: Apparently Tunnelblick can't resolve the domain name to get the IP address it should connect to, or the IP address is inaccesible, and exits, in your case gb.vpn.airdns.org. Can you please check the DNS settings of your system? Make sure that publicly accessible DNS addresses are set. See here if necessary: https://serverguy.com/kb/change-dns-server-settings-mac-os/ Furthermore, please make sure that you don't run third party tools (typically Malwarebytes, Bitdefender etc.) which might overblock our VPN servers IP addresses. Kind regards

Hello! Please try this: open the Task Manager and terminate any eddie-ui* process running. Pay attention, you could have two different processes, kill them all delete manually Eddie's configuration file. To find it, please see here: https://eddie.website/support/data-path/ uninstall Eddie completely (this time the process should be successful) reboot the system and re-install Eddie Kind regards

Hi! The final decision to re-open was taken after the request to re-open the thread came from someone who we could call a "counter-part" wishing to exercise the right to reply. This is a perfectly legitimate request. Of course we have no idea whether it comes from the original author of the table or from anyone else, and that's not important. It's only important that anyone is given the right to reply. We're sorry to hear that, and indeed the role of every moderator is invaluable. We indeed wrote "The moderators propose themselves on a voluntary basis and perform their tasks during their free time without any monetary retribution and without any obligation to complete their task in the future. Moderators are not employees of AirVPN and their only motivations are passion and dedication. Their role in maintaining the community forums readable and a relaxed place is invaluable." and we're sorry to hear that it's not enough in your opinion. Therefore, we would like here to re-affirm that without the invaluable moderators activities performed every day and for years and years with passion and dedication, and without any monetary compensation, the community forums could not exist as they currently do. The moderators also wrote valuable guides, created translations into various languages for Eddie Android edition (check the credits in the app), and assist other users relentlessly. For that, we and all the community owe to OpenSourcerer, LZ1, zhang888 gratitude and recognition. Kind regards

Hello! Can you please publish the integral Tunnelblick log? Note: feel free to open a ticket as well to get support directly from the technical support team. Kind regards

Hello! Thank you for having joined the AirVPN community forums with vibrant passion. The community forums have been created by AirVPN for the AirVPN community, and are moderated by moderators from the community itself, appointed by the AirVPN staff. An experiment with un-moderated forums was attempted but unfortunately it was a fiasco. Nowadays, hoping to have a readable forum when it's not moderated at all is probably unrealistic. The moderators propose themselves on a voluntary basis and perform their tasks during their free time without any monetary retribution and without any obligation to complete their task in the future. Moderators are not employees of AirVPN and their only motivations are passion and dedication. Their role in maintaining the community forums readable and a relaxed place is invaluable. While the AirVPN staff forums are moderated by Staff and only Staff members can start new threads, community forums are open to anyone (even non AirVPN customers) and are subjected to non-staff moderation in general. Staff members now and then intervene on the community forum, usually when a post by staff is explicitly required or in those rare cases for which legal problems arise, but in general the staff members don't interfere with the community and with the moderators activity, except to delete blatantly spam bot messages ("buy pharma", "new project porn", and so on) when they pass through captchas. In the case of this particular thread, the support team had an important amount of requests to re-open it (not from you, we know) even from long time community members. Due to the amount of requests, support passed all the matter to a staff member who decided that it was worth to re-open the thread immediately. It is opinion of some staff members that this thread is informative in general, and that it provides various verifiable data which may be useful to protect AirVPN business and promote the good name of AirVPN itself. By keeping the thread open, the community offers to any involved party, including the parties which allegedly publish false data harming AirVPN and/or other services here mentioned, the option to reply even in public and even here should they wish so. We repute that locking the thread would substantially undermine the right to reply, as correctly external entities made us notice via e-mail. With them we publicly apologize, and at the same time we remind that the locking was very short (something like 3 hours max), that a new thread may be opened by anyone (you don't need to be an AirVPN customer) and that the forum moderation is performed by volunteers from the community. Please keep in mind that moderators are persons and human errors in total good faith are possible. There is no reason to make a drama out of it. Whether you are a member of AirVPN community or an external entity which want to exercise the inalienable right to reply, we encourage you and the whole community to open a direct communication channel with moderators when you have doubts, complaints, or just to discuss issues in the forum. You can reach community moderators (LZ1, OpenSourcerer and zhang888) through direct messages of your forum Messenger. Staff messenger is also open now, and as usual for professional support you may open tickets which will be handled by the (not outsourced) support team. Kind regards

Hello! Can you please tell us on which VPN servers, if you can be more specific? Kind regards

@theroarmonster Thank you very much! Hopefully it was just a momentary DNS malfunction. Please feel free to keep us posted if the problem re-occurs and remember the airvpn.info web site in case of "emergency". Kind regards

@OpenSourcerer Re-opening the thread upon various users request... at least for a while. We did not expect we could acquire information we were unaware of thanks to this thread but it happened, plus some community member was happy to be informed about this whole matter so let's see where the thread goes, it doesn't deserve to be locked right now. Let the community members decide by themselves what to do, of course always within the bounds of the netiquette (right, @fsy ?).

Hello! Our New York City server provider M247 informs us of two planned maintenances which will affect our servers during the following time windows: From: Tuesday, 9th of May 2023 07:00 am UTC To: Tuesday, 9th of May 2023 11:00 am UTC From: Wednesday, 10th of May 2023 07:00 am UTC To: Wednesday, 10th of May 2023 11:00 am UTC During the above maintenance windows the servers may experience downtime periods. The downtime periods are not expected to be as long as the entire maintenance window. These works are part of the New York network upgrade process. Kind regards AirVPN Staff

Hello! It really looks like your traffic to airvpn.org is hijacked. Can you access regularly the.info (.info in place of .org) web site? Can you also tell us which IP address airvpn.org resolves into, by using your ISP DNS? You can see it with command: nslookup airvpn.org or alternatively dig airvpn.org Any other Rogers customer here who can test and report, please? Kind regards

Hello! Unfortunately they have an uptime which is too low. You can see now that they have accumulated, only in 2023, something like 15 days of downtime, a colossal amount. They do not operate according to the minimum standards we agreed on with the provider. What's more, the intermittent but frequent line problems they have been suffering in the last 4-5 weeks have caused our customers inconveniences and led to legitimate contentions, complaints and disputes. By offering a new datacenter from a company which proved to be more reliable in the last 7 years we aim at improving the connectivity quality in Brazil and surrounding South America countries dramatically. Kind regards

Hello! We confirm that the linked table includes several errors. We take this opportunity to clarify that: all VPN servers use RAM disks. After a minimal bootstrap which must bring up the TCP/IP stack, the network and essential services to operate on the network, vital files (including secrets, configuration files and scripts) are downloaded on RAM from the network, from selected storage and strong authentication ensuring integrity. What's more, if a server reboots unexpectedly, the AirVPN management must confirm the authorization for the server to be re-admitted in the infrastructure, making it possible to understand the cause of the reboot and to verify (thanks to pristine copies) whether the server has been tampered before it comes back operational WireGuard is available since 2022 (in beta testing since the last quarter of 2021) and it also includes pre-shared keys, just in case they are needed for a quick additional cipher deployment in an unlikely post-quantum world. The API has been improved to offer the option to re-generate keys on the fly, resolving the privacy problems posed by WireGuard ads, trackers etc. blocking lists are available since 2021. In our opinion our system is unrivaled on any VPN service, as you can configure it, add additional blocks or specific exceptions to lift blocks, and link different lists, additions and exceptions to different devices. Last but not least you can operate via API to get the available list information. Note that the ad blocking system is opt-in for a precise choice: by default the network must remain agnostic and neutral. Blocks are enforced only when explicitly wanted by the users. additional connection modes include OpenVPN connecting through HTTP(S) and SOCKS proxies, OpenVPN over Tor (not available on Android), OpenVPN over previously established TLS and SSH tunnels (OpenVPN over stunnel and OpenVPN over SSH), OpenVPN tls-auth for backward compatibility, OpenVPN tls-crypt for enhanced block bypassing Kind regards

Hello! For the readers: the problem affecting @konijntjes has been resolved by disabling Windows "Fast startup" option. We are still investigating to understand more closely the source of the issue. Thanks to @konijntjes precious reports flowed in during the last hours, it might be something related to network interface handling before and after a system suspension or hibernation, but it's premature to say anything more detailed. In the meantime, anybody suffering similar problems may try to disable "Fast startup" to resolve the issue, which is anyway an option infamously known to pose a lot of different problems even on latest Windows versions and even to system commands. Kind regards

Hello! There's a part of an old urban legend here. Eddie's source code is available on GitHub (including the current 2.22.2 which is still considered "beta", according to the unorthodox release cycle of Eddie), anyway the essence of the urban legend is assuming that a license enforces restrictions on future releases of a certain work on the copyright holders themselves. The copyright holders are not restricted on future development or re-arrangement of a work of mind by any previous license since they are the "legal owners" (according to the international treaties which overlap intellectual monopoly with intellectual property and the EU legal framework on intellectual monopolies). On subsequent releases, the license of the current work always defines and/or restricts the rights of third parties, and not the rights of the legal owners. At the same time, the license we agreed to pick grants third parties that no retroactive restrictions are possible. If Eddie's developer decided to distribute an Eddie version without source code he would have the legal right to do so, provided that Eddie does not include third-party code licensed with restrictions against closed source code. It doesn't happen because of AirVPN mission (and Eddie's developer is also an AirVPN co-founder), but legally it would be Eddie's developer right. An identical right is reserved to AirVPN Suite developers, and exercised on both senses. If you notice, when a Suite alpha or beta version is made available to community testers, the OpenVPN3-AirVPN library against which the Suite is linked is always open source, while the proprietary preview code is closed. It is then re-licensed and opened (usually under GPLv3 but we're not ruling out different, more permissive licenses, for the parts we have exclusive rights on) only when the development team considers the software as "stable". Even in this case, releasing a copyrighted software as a preview does not prevent the developers to re-license and open it in the future (so far to make it open source under GPL). You did not miss anything. Eddie 2.22.2 is still the latest "experimental", but the testing work is over. If nothing serious comes out (fingers crossed) you will see a new stable release very soon. Kind regards

@konijntjes Hello! Thank you for having contacted the support team. We have reviewed your ticket and we re-publish the relevant part here just in case some other user has experienced the same Windows malfunction and for general knowledge which might be relevant to this thread. It seems that the problem is related to Windows (and specifically to ipconfig.exe utility) and not to Eddie. If anyone has relevant information about this, please feel free to write here, as we have never seen something like this on any of our Windows testing systems. ---- TICKET REPLY BY CUSTOMER SUPPORT --- The quoted error is a system error. ipconfig.exe is a system application. You have an anomaly of a system application used by Eddie and by OpenVPN, but only at the first boot. This might be a Windows bug related to "fast startup". Can you please check whether fast boot is enabled or disabled? If it's enabled, please disable it and test again. See also here: https://www.windowscentral.com/how-disable-windows-10-fast-startup What's more, if you run third-party antimalware or packet filtering tool, try to disable them as well and test again. It's possible that such tools prevent the system utility (ipconfig) to start under some peculiar situation. We can't reproduce this problem at the moment and we have no other reports related to ipconfig unable to start, but now everything suggests that the problem is related to Windows and networking, or some antimalware tool interfering with network configuration, and not to Eddie itself. We're looking forward to hearing from you. Kind regards AirVPN Support Team --- CUT --- Kind regards

Hello, you didn't open any ticket about this problem, so.... please open a ticket, as the support team is here to assist, just use the customer service! Kind regards

Hello! Like many other well behaving programs, Eddie stores a configuration file in the home directory of the user(s) who launched it. Please see also: https://eddie.website/support/data-path/ Kind regards

Hello! It's a problem affecting intermittently three Dallas servers, apparently, which fail to compute the correct bandwidth due to network interface traffic counters premature reset. So you see the correct amount of connections, but a much lower bandwidth. Chamaeleon, Pegasus and Mensa are currently suffering this issue. A new investigation will be opened. Kind regards

Hello! Thank you for your suggestion. Network Lock remains enabled if the AirVPN app crashes or suffers any abnormal termination. On the contrary, if the AirVPN app is cleanly closed, or the Network Lock is explicitly disabled through the proper option, then the previous system firewall settings are restored. This is by community driven design in the early 2010s and it's still the correct design according to the idea that the AirVPN app, once shut down properly, must not be invasive and must restore all the system settings. It's then administrator's competence, by settings the proper rules, to decide whether the packet filtering tool must block Internet connectivity when the AirVPN app is cleanly shut down or has not been launched, or not. Kind regards

Hello! We're very glad to inform you that a new 1 Gbit/s full duplex server located in Sao Paulo (Brazil) is available: Fulu. 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 and 47107 UDP for WireGuard. Fulu 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 and 4096 bit DH key not shared with any other VPN server. You can check the status as usual in our real time servers monitor: https://airvpn.org/servers/Fulu Please note that Fulu will replace Peony and Lalande, which unfortunately in the last 6 months performed very poorly. Peony and Lalande are currently down (again). Unfortunately the uptime of Peony and Lalande has become unacceptably low, so we are forced to decommission them. Fulu can replace both servers as our tests confirm that its superior hardware and connectivity outperform Peony and Lalande together. Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team 

Hello and special thanks! Please see here for an explanation and a quick solution: https://airvpn.org/forums/topic/53004-openssl-error-restart-every-3-seconds/ Kind regards

Hello! For the readers, an update from the support team. The problem of the OP was caused by the fact that he/she disabled Eddie's Network Lock inadvertently by setting "Allow outgoing" and "Allow incoming" connections outside the VPN tunnel in the network lock fine tuning settings. This event pushes us to recommend the following: do not change advanced settings if you don't understand what they do. Read the documentation first and if you still have doubts contact the customer service. Kind regards

Hello! It is possible that you're still running OpenVPN 2.4. That message is slightly misleading: in reality, it usually means that some directive in the ovpn file has not been recognized. Our Configuration Generator, now, by default creates ovpn files compatible with OpenVPN 2.5, 2.6 and 3. If you still run OpenVPN 2.4, you must generate a configuration file with the following options in the CG: - check "Advanced Mode" - in the "OpenVPN version" combo box select ">= 2.4". The above settings will force the CG to generate an ovpn file fully compatible with OpenVPN 2.4.x. Let us know whether the above solves the problem. Kind regards

Hello! Please follow the thread here: https://airvpn.org/forums/topic/56119-new-10-gbits-server-available-bg/ The message by Antonio Quartulli on the end of March implies that our tests had to re-start almost from scratch with the new DCO and the new OpenVPN 2.6.2. Remember that DCO, as reported in the GitHub repository https://github.com/OpenVPN/ovpn-dco ovpn-dco is currently under heavy development, therefore neither its userspace API nor the code itself is considered stable and may change radically over time. Remember also that every time the code changes radically our tests must re-start almost from scratch. About the stability, with 2.6.2 and latest current experimental DCO 0.2 module we have not had anymore kernel panics. Given the above you can easily understand that DCO is not ready for production on the server side of course, so we're planning to put a highly experimental server to let the community test with no stability or backward compatibility commitments. For latest issues and updates about them, please follow GitHub as well: https://github.com/OpenVPN/ovpn-dco/issues Kind regards