Staff

19 hours ago, sarahc said:

It's been down since yesterday and it's really impacting me

-Also, this is my first post since I purchased service more than 5 years ago, and your forum software is telling me that I've already reached posting limit 😕

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
 

On 4/22/2024 at 8:17 PM, acute-playpen-downy-qatar said:

I'm able to connect fine using OpenVPN. When I try to connect with WireGuard (any profile), Eddie fails at "Checking DNS." What could be going on?

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
 

11 hours ago, sidsec said:

I am trialling the WireGuard client with AirVPN generated server configs on macOS. It's very fast - almost too fast. Am I missing something?

There is no obvious Network Lock comfort blanket. Is the WireGuard client / AirVPN server config as secure as using Eddie with Network lock?

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
 

18 hours ago, flat4 said:

boy there's a few servers down for maintenance for a few days.

Are they being upgraded?

Hello!

Yes, there are many upgrades ongoing on the whole 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
 

13 hours ago, MHq said:

Hello, I have the installer, and have uninstalled it form the Windows control panel, but after reinstalling Eddie, the Activate Ntework lock is still checked, thus Eddie should store the settings somewhere (registry? %LOCALAPPDATA% ?)

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.
 

14 hours ago, MHq said:

Actually, it doesn't crash the machine:

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
 

25 minutes ago, MHq said:

Thanks for reply.  It seems Netwrok Lock option is enabled and set to Automatic by default, is that correct?

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
 

3 hours ago, MHq said:

Hello everyone, say I'm torrenting and eMuleing passing thru Eddie on a Windows Server machine. 
I noticed that I may change the VPN server I'm connected to without closing any applications, but is this advisable?
Or would it be better to close qBittorrent and eMule, switch to a different VPN server and then restart the p2p apps?

Thanks in advance 

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
 

1 hour ago, Air4141841 said:

guess I still do not follow.   when the troubleshooting forum posts list Eddie logs 
so Eddie is bundled with the same version of openvpn as the current servers are running 2.5.5? 
we would need to manually tell the program to use an updated version?    is there an article written with these instructions I can review so I can better understand? 

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
 

39 minutes ago, Air4141841 said:

When will the Eddie client receive the newer openssl 3* ?


https://www.openssl.org/source/

states 1.1.1 should not be used 

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
 

1 hour ago, Crewman6639 said:

having trouble getting Eddie on Windows 11 to use IPv6 instead of IPv4. In the networking tab if I set any of the preferences to either prefer IPV6 and/or block IPv4, regardless of protocol, I cannot connect to a server. I am assuming I am probably doing something wrong and was hoping others might have a solution. 

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
 

1 hour ago, b0sszkr1 said:

Closed Eddie, deleted default.profile, re-started Eddie, no dice.

Really sorry, I know it's gotta be something I'm doing wrong. Is there something else it might be? 

Here's an updated log if it helps: https://eddie.website/report/1413566f/ 

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
 

13 hours ago, cucuruz said:

Hi folks,
newcomer here, Linux Ubuntu 23, running Eddie on WireGuard. from my area I have plenty of servers available, and getting like 500 Mbps every day. Refreshing and a lot quicker than my previous vpn! but on the top user speed I see lots of people getting higher speed, is there any way I can fine tune my Eddie to squeeze more bw? Kudos for port forwarding and ad block, terrific system... any chance we can get more than 5 ports? Or I missed some option to have more ports (for a price)?

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
 

@b0sszkr1

Hello!

We see that you renewed your OpenVPN key and certificate very recently. Eddie updates them only when an account logs in (this behavior will change in future versions). Please try the following procedure:

• run Eddie
• log your account out
• log your account in
• try again a connection

Kind regards
 

@AirGuy24

Hello!

The route check failure claimed by Eddie seems correct, because it is confirmed by WireGuard:
 

52 minutes ago, AirGuy24 said:

. 2024.04.17 10:42:50 - WireGuard > Retrying handshake with peer 1 (199.189.27.125:1637) because we stopped hearing back after 15 seconds
. 2024.04.17 10:42:50 - WireGuard > Handshake for peer 1 (199.189.27.125:1637) did not complete after 5 seconds, retrying (try 2)

Therefore, this problem could be peculiar to the WireGuard code implemented in Eddie 2.21 (or Eddie is blocked by some other blocking tool, can you please check?) and the new WireGuard resolves the problem. Can you please test whether or not the same problem occurs with Eddie 2.24.x? Please see here to download it: https://airvpn.org/forums/topic/57401-eddie-desktop-224-beta-released/

Kind regards
 

Hello!

Please try the following procedure to quickly resolve the problem:

• 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

Kind regards
 

@overmorrow

Hello!

Do you have the package mono-runtime-common available for your system? If so, try to install it and test whether the problem gets solved. Of course a portable program should not require external installations, but at the moment that's a workaround for a "quick and dirty" patch.

Kind regards
 

14 minutes ago, jowlo said:

Hi!

Thanks for the quick answer. I know, but this is a device managed by another account. I do not have access to that account to regenerate the configuration for this device. 

My question was whether there is another way of extending the lifetime of the certificate and getting the new CA without the use of the Configuration Generator. But it appears not, thank you anyways...

Hello!

Well, very strange case. BTW, ca.crt is just a public certificate and is always the same, so no, the Configuration Generator is not strictly needed, once any account has the ca.crt, it can be sent to any other account. The client certificate and key, on the contrary, are secret and non-sharable files.

Kind regards