Staff

Hello, just to frame correctly the issue and fix what you incorrectly wrote, the support team did not consider the issue resolved at all and you were told that the whole content of the ticket would have been transmitted to Eddie developers. Kind regards

We confirm once again, as we always did, that IPv6 support will be added within the end of 2017. Kind regards

Each party has had enough room and time to expose over-eloquently its point of view. Thread locked. Kind regards

@Midori_Salad The log shows that the problem you mention does not exist, at least in the successful connection you showed. You need to post the log taken just after the problem has occurred, or even better a system report ("Logs" > life belt icon > paste into your message). From the log we see anyway that you're not running the latest Eddie release. Please upgrade and test again and if the problem persists send us a system report taken just after the problem has occurred. Kind regards

Hello, we operate servers in five different datacenters in the UK served by different transit providers. It's unlikely (to say the least) that five different datacenters have all the same problem at the same time, and that the 3-4000 persons connecting every week to some UK server do not file a complaint or a warning. On top of that we don't see any relevant problem and our monitoring system does not detect behaviors different that those related to the 8 months ago period you mention. Have you considered different options? Kind regards

Hello, check whether disabling Wayland helps: https://airvpn.org/topic/20750-airvpn-not-working-with-fedora-25-wayland/

This happens with various applications, not only with Eddie. Restart Explorer and the tray icon should re-appear. Double-click on the tray icon to bring up the main window. https://www.howtogeek.com/198815/use-this-secret-trick-to-close-and-restart-explorer.exe-in-windows/ Kind regards

Hello! Unfortunately your messages are useless if you don't post a system report or at least the log showing the issue. Feel free to open a ticket as well. Kind regards

Hello! Anyway Eddie 2.10.3 is more than two years old and is not fully compatible with Wndows 10 and macOS Sierra/High Sierra, not to mention an important amount of bug fixes and improved features since then. An upgrade is recommended. See the changelog here: https://eddie.website/changelog/?software=client&format=html Kind regards

What do you mean by technically impossible? There are other VPN providers out there (I can name a couple that I have previously used) that do it: you have an option in their connection tool that you can turn on or off: when it is on, they block ads, when it is off, you just get everything. I find that very handy. We are not interested in traffic inspection, not even to block ads. Traffic inspection has profound effects and legal consequences: it's contrary to our policy and mission, it weakens remarkably the anonymity layer, it opens the doors dangerously to logging and monitoring and affects in both major and subtle ways the mere conduit status of a service provider in the information society (exemption of liability for users of the service behavior is reduced when the provider selects the content to re-transmit, as past jurisprudence in the EU has widely shown). About traffic discrimination on your end (in your system) you can of course do as you prefer, there are many tools around which meet your needs without overloading our software with options unrelated to our mission or (even worse!) making it become bloatware. Kind regards

Temporary workaround for Ubuntu 17.10 (until the next Eddie version is released) - Install Debian package - edit /usr/bin/airvpn from terminal: xhost +local: && sudo gedit /usr/bin/airvpn- Replace the line mono /usr/lib/AirVPN/AirVPN.exe --path=$HOME/.airvpn "$@"with xhost +local: && pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY mono /usr/lib/AirVPN/AirVPN.exe --path=$HOME/.airvpn "$@"- Launch normally by double-clicking AirVPN icon.

Hello! We remind you that Eddie is currently incompatible with Wayland: momentarily please fall back to X11. Compatibility with Wayland has been planned with Eddie 3. Kind regards

When the IP address of the client changes the OpenVPN connection is lost. Eddie and OpenVPN will try to reconnect as soon as possible. In the meantime the old sockets of the torrent software can't be used to exchange data, but most torrent clients show throughput with a sort of fuzzy logic https://en.wikipedia.org/wiki/Fuzzy_logic (or just an averaged tp on some unit time) so you will not see the throughput going to zero suddenly from the software indicators, not even when you have Network Lock enabled. As soon as OpenVPN reconnects , the torrent software will be able to open new socket(s) (and advertise the new IP address etc.) in a really short time. Kind regards

Hello! Yes, p2p is allowed, as well as any other protocol. Currently p2p is a set of the most efficient protocols to share and access information on the Internet. We do not discriminate against any protocol. In general, we kindly ask you to read the FAQ and their answers before writing in the forum or opening a ticket. Thank you in advance. Please see here: https://airvpn.org/topic/9170-do-you-allow-p2p-how-can-i-optimize-performance-of-emule-and-bittorrent-with-airvpn/ Kind regards

First the address is clearly written, second you have never sent any refund request (not a ticket, not an e-mail), third you don't need to be "techy" unless with "techy" you mean someone capable to download a software from the Internet and using a mouse to click and double-click. Go trolling somewhere else, we have no time to waste. For the readers: we follow a no-questions-asked refund policy in the first three days. Our refunds are normally delivered within 2 working days (the law prescribes 30 days and we will never break this limit). Additionally (and obviously) you are protected by the EU legal framework on consumers protection for the remote purchase of goods or services, according to which you have the right to a refund within 30 days from the service delivery with a simple written request. Regards

Hello, please upgrade to version 2.13.6 (latest stable release at the moment). Your version (2.10.3) is three or so years old and is not fully compatible with macOS Sierra, Windows 8 and Windows 10. Additionally, DNS handling under Windows has been improved dramatically. Kind regards

That's totally correct (except for the fact that the remote servers are four in different countries). Eddie developers are aware of it and the next version of Eddie will address this weakness. The problem is not in updating the information (Eddie can very well use the old ones on the HDD when it can't download new ones) but to log the account in the service the first time, download servers information the first time and so on. EDIT: remember that you can configure Eddie to connect over Tor or some SOCKS or HTTP proxy. This could be useful to download info the first time you run Eddie in those networks where the "bootstrap" Eddie servers are blocked but Tor or some third-party proxy is not. Kind regards

Hello, it looks like your system is querying a poisoned DNS (specifically, a DNS that's been poisoned by order of the AU Federal Court). Please run Eddie (the Air client software) to make sure that your system queries VPN DNS, or anyway open a ticket to receive proper support. Kind regards

Please upgrade to Eddie 2.13.6 (latest stable release). What you describe is a bug affecting Eddie 2.12.4, we're sorry. Kind regards

Hello, what happens if you disable DNS check? Select "AirVPN" > "Preferences" > "DNS", untick "Check Air VPN DNS" and click "Save". Enable Network Lock as well. That's expected, the VPN DNS is not reachable from the Internet, as you might have seen the address is in a private subnet. Kind regards

Please upgrade to Eddie 2.13.6 (latest stable release), reboot both the router and the system and test again. Kind regards

Good or bad this is how things work. If you bind a program to an interface different than the tun/tap interface you can't expect in general that the traffic of this program is tunneled or blocked, unless the previous default gateway is completely removed obviously. This is not an optimal solution for a couple of good reasons and Network Lock should be preferred. That's the basic of how WebRTC works, and that's why with Network Lock you don't only prevent WebRTC leak, but any leak caused by any "wrong" or "unintended" binding. For more clarifications please see https://www.clodo.it/blog/an-alternative-approach-to-so-called-webrtc-leaks/ Therefore, once again and hopefully for the last time: if you experienced a "WebRTC" leak either Network Lock was not on, or the firewall rules were modified after Network Lock had been enabled. When/if you manage to reproduce the issue make sure to print and store all the firewall rules. That's the first step to start troubleshooting. All the other speculations at this time are just time wasting chattering. Kind regards

This is contradictory. If you had a "WebRTC leak" then either Network Lock was NOT on, or the firewall rules had been modified after Network Lock was turned on. When/if you manage to reproduce the issue make sure to print and store all the firewall rules. That's the first step to start troubleshooting. Kind regards

The server is physically in Romania and geo-restricted to Romania services are accessible so it's some database error you can safely ignore in any case. Kind regards

Hello, "Connection refused" (error 111) in several cases means that the packets have been properly delivered to the final destination and actively rejected/dropped. Please check the firewall rules in the machine connecting to the VPN. Furthermore, if the device connecting to the VPN is not the same device running the torrent client, then you need forward packets from the tun interface of the connected device to the proper port of the IP address of the device running the torrent client. For example: https://airvpn.org/topic/9270-how-to-forward-ports-in-dd-wrt-tomato-with-iptables/ Kind regards