Staff

Hello! Goldcrest looks for a configuration file named "off" and does not find it. This is due to Goldcrest's parser, as this particular usage is not permitted. Goldcrest, in the current command line example you gave us, needs a configuration file as a mandatory option (for example air-connect) is missing. So it finds off and considers it the name of the configuration file and not the argument of the network-lock option. We will consider to address the issue both on the program and the manual to provide more informative notes and proper error message. Back to your problem, if you have persistent Network Lock enabled in Bluetit you can't disable it through Goldcrest: by design, some Bluetit settings can not be overridden by Goldcrest commands for security reasons (more info on the user's manual). If a system administrator needs to disable persistent network lock, root must terminate Bluetit. Just before exiting, Bluetit "disables Network Lock", i.e. it restores previous system settings and firewall rules. DNS settings are a different, potential reason of the issue: please check your system DNS after you have terminated Bluetit and make sure that publicly reachable nameservers are set. Kind regards

Hello! WireGuard can't assign addresses dynamically so each address is linked to a single key. With multiple keys you will have multiple addresses. Please generate different keys in your AirVPN account "Client Area" > "Devices" pane and use each key for a unique connection. Instructions are available here: https://airvpn.org/forums/topic/26209-how-to-manage-client-certificatekey-pairs/ Kind regards

Hello! The correct FQDN for the various servers is <server name>.airservers.org. However it resolves into IP address 1 only. Each VPN server has 4 entry-IP addresses for various connection modes, but we do not offer domain names for each IP address. For example entry-IP address 1 accepts OpenVPN in TLS Auth mode (for backward compatibility with old OpenVPN versions) and WireGuard, entry-IP address 3 accepts OpenVPN in TLS Crypt mode and WireGuard, and so on. For every detail you can check the "Specs" page "Protocols and entry-IP addresses of each VPN server" section: https://airvpn.org/specs You can use the API to get all the entry IP addresses of all the servers. API instructions and an API navigator are available in your AirVPN account "Client Area" > "API" panel. To make an example based on your request, let's say that you need to know all the info about Teegarden. A first raw search can be performed through the API and filtered accordingly, please see below. The first example shows everything the API can say about Teegarden, the second example prints the THIRD entry IPv4 and IPv6 addresses. Kind regards $ curl -s "https://airvpn.org/api/status/" | grep -A17 -i teegarden "public_name": "Teegarden", "country_name": "United States", "country_code": "us", "location": "Los Angeles", "continent": "America", "bw": 637, "bw_max": 2000, "users": 102, "currentload": 31, "ip_v4_in1": "37.120.132.90", "ip_v4_in2": "37.120.132.92", "ip_v4_in3": "37.120.132.93", "ip_v4_in4": "37.120.132.94", "ip_v6_in1": "2a0d:5600:8:3e:b389:fbfa:508a:1eca", "ip_v6_in2": "2a0d:5600:8:3e:604e:24d0:570c:230f", "ip_v6_in3": "2a0d:5600:8:3e:eceb:3b20:e697:db07", "ip_v6_in4": "2a0d:5600:8:3e:878b:13a8:3b47:98ed", "health": "ok" $ curl -s "https://airvpn.org/api/status/" | grep -A18 -i teegarden | grep in3 | awk -F '"' '{print $4}' 37.120.132.93 2a0d:5600:8:3e:eceb:3b20:e697:db07

Hello! Please try the following procedure: run Eddie on Eddie's main window uncheck "Remember me" log your account out log your account in (you'll need to re-enter your AirVPN credentials) try again a connection See also https://airvpn.org/forums/topic/58289-openvpn-certificate-has-expired/?do=findComment&comment=231319 Kind regards

Hello! We are investigating the problem. Kind regards

Hello! We're glad to inform you that it is back online now. Kind regards

@valkyrie89 Hello! Inbound remote port forwarding is a feature divorced from the VPN p-t-p communication protocol, it all relies on NAT configuration through packet mangling, so you can use it both with OpenVPN and WireGuard. Kind regards

Hello! Can you please test Eddie 2.24.2 beta and check whether the problem persists or gets resolved? Please see here to download the latest beta version: https://airvpn.org/forums/topic/57401-eddie-desktop-224-beta-released/ Kind regards

@8zXUsOoeym Hello! The problem has been solved, at least according to our tests. Can you please check now? Kind regards

Hello! WireGuard on macOS still lacks a kernel module, so in an agnostic network you should not see a lot of gain from OpenVPN. However, it's also possible that your ISP shapes OpenVPN and not WireGuard, or shapes low ports but not high ports (if you connect WireGuard to port 51820 and OpenVPN to port 443, for example). Please make sure that the tunnel works properly by browsing to https://ipleak.net - when you open that page while the Mac is connected to the VPN, you must not see your "real", ISP-assigned public IP address anywhere. Do you also see performance boost compared to Eddie connecting over WireGuard? If so, MTU could come into play. The CG generates files with MTU set to 1320 bytes (*), Eddie 2.21.8 lets WireGuard pick the default value (1420 bytes, typically), while Eddie 2.24.x defaults to 1320 bytes but lets you configure various, different MTU size in bytes (1280, 1320, 1360, 1400, wg default). (*) You can change it by editing the configuration file with any text editor and changing the line "MTU = 1320". Kind regards

Hello! Yes, there are many upgrades underway throughout the infrastructure. On top of the usual, periodical system updates, we are adding an important new feature we will announce in the future (maybe as early as June, but don't take it for granted). Kind regards

@blank90 Hello! As @SurprisedItWorks wrote you may rely on https://ipleak.net, or you can also use the AirVPN API. Check your "Client Area" > "API" panel for instructions and commands through the API navigator. With a single fetch you can get all the data of all the servers, for example. Kind regards

@8zXUsOoeym Hello! We confirm some problem on the datacenter, the bandwidth is "choked". It happens now and then in UA. We're contacting datacenter technicians if the problem does not disappear within a couple of hours, thank you for the head up. Kind regards

Hello! Yes, exactly. The location of the configuration file is described in the following page: https://eddie.website/support/data-path/ When you uninstall you don't destroy the configuration file. In other systems, uninstalling a program implies preserving the settings in case of future re-installing or upgrading, while purging implies deletion of settings on top of any other program related file deletion. OK, that's better. Network Lock, as you correctly found out, did its job. Kind regards

@MHq Hello! If you have the portable package just delete the directory which you have decompressed the package into. If you have the installing version you can start the Windows uninstall procedure available in the control panel. Do you have the option to obtain the crash dump (or any message related to the crash) and send it to us? Eddie does not have the power to bring down an entire Windows system. System drivers could, however, and Eddie features the usual and well tested in years wintun driver (Windows is the only system which does not come pre-packaged with a driver for a virtual network adapter, so it's strictly necessary to install it). Kind regards

Hello! That depends on the Eddie version. Up to Eddie 2.22 Network Lock is disabled by default. Starting from Eddie 2.23 Network Lock is active during a connection, by default, and de-activates when the user explicitly orders the end of a connection. This working mode is not suitable for your goal. In all versions, enabling Network Lock manually or at startup enforces Network Lock during the whole program session lifetime, no matter what (therefore Network Lock is permanently set and protects you from any server switch or any other event). This is the working mode you want, which is disabled only when you order explicitly to de-activate Network Lock or you shut down Eddie cleanly. You can also configure Eddie to always activate Network Lock (as soon as the program is launched) on the "Preferences" > "General" window, by checking "Activate Network Lock at startup". For your purpose this is highly recommended for peace of mind. Kind regards

Hello! Only if Network Lock option is enabled you can safely switch servers "on the fly", because Network Lock will prevent any possible traffic leak outside the VPN tunnel. Kind regards

Hello! You can either use the OpenVPN version packaged with Eddie, Hummingbird, or another version, as you prefer. To change OpenVPN version selected by Eddie, please install in your system the OpenVPN version you prefer; then, run Eddie and from its main window select "Preferences" > "Advanced". Beside the "OpenVPN custom path" field please click the file requester symbol to navigate through your file system and choose the proper OpenVPN binary file. Finally click "Save". Alternatively just type in the field the binary name with the complete, absolute path, and click "Save". Kind regards

Hello! Eddie is not linked against any OpenSSL library. It's OpenVPN the program linked against some TSL library, which is in most cases OpenSSL, and that depends on your system. Eddie Windows and Mac edition include a ready to use OpenVPN binary linked against OpenSSL and this binary is updated on each new version, but you can update it by yourself. You can also tell Eddie to start a specific OpenVPN binary in your system. WireGuard does not use any external TLS library, so if you have Eddie connection mode set to WireGuard you can ignore OpenSSL. Kind regards

Hello! An essential requisite is that your ISP supports pure IPv6 (not IPv6 over IPv4), can you please verify? If your ISP does not support IPv6 you must connect over IPv4. Then, provided that IPv6 is supported by your system, you can use IPv6 over IPv4 through our servers. Kind regards

@darksent21 Hello! Your idea is totally correct but unfortunately Android forbids (for unfathomably alleged security reasons or waffling technical oversight) the phone to work as a hot spot in tethering mode when in a VPN. So you can't share the VPN traffic with an un-rooted Android device working as a hot spot. Technically, it's because Android VPN tethering system app fails to set the proper packet pre-routing and forward rules for a virtual network interface. However, if you have a rooted device you can fix the problem by adding the missing mangling rules with iptables. Please see here: https://android.stackexchange.com/questions/60819/can-i-share-my-androids-vpn-connection-over-a-hotspot Kind regards

Hello! Please try the following procedure: https://airvpn.org/forums/topic/58289-openvpn-certificate-has-expired/?do=findComment&comment=231319 Kind regards

Hello! Nothing wrong on your side, you performed the procedure correctly. The error changed, now it is very different: . 2024.04.18 01:49:20 - OpenVPN > TCP: connect to [AF_INET]192.30.89.29:443 failed: Unknown error Knowing that the error is "unknown" does not help so much, but at least the previous problem is solved. Do you run any antimalware tool which could be blocking OpenVPN and cause this unknown error? What happens if you switch to WireGuard? To do so: from Eddie's main window please select "Preferences" > "Protocols" uncheck "Automatic" select the line with WireGuard port 51820. The line will be highlighted click "Save" and test again connections to various servers Kind regards

Hello! You can test different MTU values. Please install Eddie 2.24.x (if you haven't already done so) and change MTU on "Preferences" > "WireGuard" window. Please try all the possible values to determine which one can provide you with the best performance. Each time you change value you need to re-start the VPN connection, in order to apply the change on WireGuard. Please make sure to perform a variety of "speed" tests on a level playing field. Also, please make sure to test servers in a variety of locations around your node. The limit of 5 ports can't be increased at the moment, we are very sorry. We are working to power up remote inbound port forwarding system in order to avert port depletion and also be able to offer a larger quantity if needed. Stay tuned and welcome aboard! Kind regards

@b0sszkr1 Hello! Do you still get this error? . 2024.04.17 13:43:12 - OpenVPN > AUTH: Received control message: AUTH_FAILED If so, try to delete the following file while Eddie is NOT running: C:\Users\ag\AppData\Local\Eddie\default.profile Then re-start Eddie (you will need to re-enter your AirVPN credentials and the custom options you wish) and test again. Kind regards