Eddie 2.14beta released

[madrat 19]

Well, after using it for the last three days on my Mac (El Capitan 10.11.6) I can say that when it's up and running it works fine - no connection problems so far.

 

However, as I mentioned in a post above, if I try to quit Eddie my whole system freezes and I have to switch off the power to my Mac in order to restart. I tried to get round that by leaving the app running in the background after disconnecting from a server at the end of the night, which was my routine with previous versions of Eddie, but when I switched on my Mac the following morning, I found that Eddie was completely greyed out, including the quit command in the drop down menu.  

 

As no one else seems to have similar problems I can only assume it has something to do with the set-up of my Mac, although I've never had this problem with previous versions of Eddie. At this stage there seems no point in continuing to use it if I have these problems every time I stop using it for any length of time. I had hoped this new version would solve the problems that I had with 2.12 and 2.13, but although it solved those issues the new version has just brought more problems. I can't even submit any logs as the problems only seem to arise after I disconnect from a server.

 

I did notice that there seem to have been some changes in the preferences with this version, and I'm just wondering if perhaps something in there might be causing the problem.

 

As always, any suggestions would be appreciated.

Maybe reset your settings to default and try connecting. If that works, start slowly adding your old settings and reconnect each change. I'm just grasping at straws here, but worth a try. I, like you, am running El Capitan, and have had no "freezing" problems at all.

[blaHbluBB 6]

this new version, is not working at all for me on windows 8.1 64bit 

 

1: Settings > General options are a bit "all over the place", if it should look that way then .... ok :/

2: Settings > Protocols entries are duplicated again bug/error:

 

3: also getting a Windows WFP, Add rule failed: error?!

I 2018.02.04 17:00:44 - Session starting.
I 2018.02.04 17:00:44 - Checking authorization ...
. 2018.02.04 17:00:45 - IPv6 disabled with packet filtering.
! 2018.02.04 17:00:45 - Connecting to Errai (Germany, Frankfurt)
. 2018.02.04 17:00:45 - Routes, added a new route, 185.189.112.12 for gateway 192.168.2.1
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG5[ui]: stunnel 5.40 on x86-pc-mingw32-gnu platform
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG5[ui]: Compiled/running with OpenSSL 1.0.2k  26 Jan 2017
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG5[ui]: Threading:WIN32 Sockets:SELECT,IPv6 TLS:ENGINE,OCSP,PSK,SNI
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG5[ui]: Reading configuration from file C:\Program Files\AirVPN\d51600e82efb6dc53ffb94c3c3d3ef86bf1d9a1b9a79fb982885eb952faad495.tmp.ssl
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG5[ui]: UTF-8 byte order mark not detected
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG6[ui]: Initializing service [openvpn]
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG4[ui]: Service [openvpn] needs authentication to prevent MITM attacks
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG5[ui]: Configuration successful
. 2018.02.04 17:00:45 - OpenVPN > OpenVPN 2.4.4 x86_64-w64-mingw32 [sSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Nov  3 2017
. 2018.02.04 17:00:45 - OpenVPN > Windows version 6.2 (Windows 8 or greater) 64bit
. 2018.02.04 17:00:45 - OpenVPN > library versions: OpenSSL 1.0.2l  25 May 2017, LZO 2.10
. 2018.02.04 17:00:45 - Connection to OpenVPN Management Interface
. 2018.02.04 17:00:45 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100
. 2018.02.04 17:00:45 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2018.02.04 17:00:45 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2018.02.04 17:00:45 - OpenVPN > TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:63694
. 2018.02.04 17:00:45 - OpenVPN > Socket Buffers: R=[65536->262144] S=[65536->131072]
. 2018.02.04 17:00:45 - OpenVPN > Attempting to establish TCP connection with [AF_INET]127.0.0.1:63694 [nonblock]
. 2018.02.04 17:00:45 - OpenVPN > TCP connection established with [AF_INET]127.0.0.1:63694
. 2018.02.04 17:00:45 - OpenVPN > TCP_CLIENT link local: (not bound)
. 2018.02.04 17:00:45 - OpenVPN > TCP_CLIENT link remote: [AF_INET]127.0.0.1:63694
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG5[0]: Service [openvpn] accepted connection from 127.0.0.1:1898
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG6[0]: s_connect: connecting 185.189.112.12:443
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG5[0]: s_connect: connected 185.189.112.12:443
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG5[0]: Service [openvpn] connected remote server from 192.168.2.2:1899
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG6[0]: SNI: sending servername: 185.189.112.12
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG6[0]: Peer certificate not required
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG6[0]: Certificate verification disabled
. 2018.02.04 17:00:45 - OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3100
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG6[0]: Client certificate not requested
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG6[0]: TLS connected: new session negotiated
. 2018.02.04 17:00:45 - SSL > 2018.02.04 17:00:45 LOG6[0]: Negotiated TLSv1.2 ciphersuite ECDHE-RSA-AES256-GCM-SHA384 (256-bit encryption)
. 2018.02.04 17:00:45 - OpenVPN > TLS: Initial packet from [AF_INET]127.0.0.1:63694, sid=4b7794ca f13122fb
. 2018.02.04 17:00:45 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2018.02.04 17:00:45 - OpenVPN > VERIFY KU OK
. 2018.02.04 17:00:45 - OpenVPN > Validating certificate extended key usage
. 2018.02.04 17:00:45 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2018.02.04 17:00:45 - OpenVPN > VERIFY EKU OK
. 2018.02.04 17:00:45 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Errai, emailAddress=info@airvpn.org
. 2018.02.04 17:00:45 - OpenVPN > Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
. 2018.02.04 17:00:45 - OpenVPN > [Errai] Peer Connection Initiated with [AF_INET]127.0.0.1:63694
. 2018.02.04 17:00:46 - OpenVPN > SENT CONTROL [Errai]: 'PUSH_REQUEST' (status=1)
. 2018.02.04 17:00:46 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 10.50.0.1,comp-lzo no,route-gateway 10.50.0.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.50.1.129 255.255.0.0,peer-id 0,cipher AES-256-GCM'
. 2018.02.04 17:00:46 - OpenVPN > Pushed option removed by filter: 'redirect-gateway def1 bypass-dhcp'
. 2018.02.04 17:00:46 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2018.02.04 17:00:46 - OpenVPN > OPTIONS IMPORT: compression parms modified
. 2018.02.04 17:00:46 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified
. 2018.02.04 17:00:46 - OpenVPN > OPTIONS IMPORT: route-related options modified
. 2018.02.04 17:00:47 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
. 2018.02.04 17:00:47 - OpenVPN > OPTIONS IMPORT: peer-id set
. 2018.02.04 17:00:47 - OpenVPN > OPTIONS IMPORT: adjusting link_mtu to 1627
. 2018.02.04 17:00:47 - OpenVPN > OPTIONS IMPORT: data channel crypto options modified
. 2018.02.04 17:00:47 - OpenVPN > Data Channel: using negotiated cipher 'AES-256-GCM'
. 2018.02.04 17:00:47 - OpenVPN > Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
. 2018.02.04 17:00:47 - OpenVPN > Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
. 2018.02.04 17:00:47 - OpenVPN > interactive service msg_channel=0
. 2018.02.04 17:00:47 - OpenVPN > ROUTE_GATEWAY 192.168.2.1/255.255.255.0 I=4 HWADDR=00:e0:4c:51:25:c8
. 2018.02.04 17:00:47 - OpenVPN > open_tun
W 2018.02.04 17:00:47 - Windows WFP, Add rule failed: Interface ID '{FB4F1D23-4739-45F2-8249-3381886D8E63}' unknown or disabled for the layer.:<rule name="NetLock - Interface - Allow {FB4F1D23-4739-45F2-8249-3381886D8E63} - IPv6" layer="ale_auth_recv_accept_v6" action="permit" weight="1000"><if field="ip_local_interface" match="equal" interface="{FB4F1D23-4739-45F2-8249-3381886D8E63}" /></rule>
. 2018.02.04 17:00:47 - OpenVPN > TAP-Windows Driver Version 9.21
. 2018.02.04 17:00:47 - OpenVPN > Set TAP-Windows TUN subnet mode network/local/netmask = 10.50.0.0/10.50.1.129/255.255.0.0 [sUCCEEDED]
. 2018.02.04 17:00:47 - OpenVPN > Notified TAP-Windows driver to set a DHCP IP/netmask of 10.50.1.129/255.255.0.0 on interface {FB4F1D23-4739-45F2-8249-3381886D8E63} [DHCP-serv: 10.50.255.254, lease-time: 31536000]
. 2018.02.04 17:00:47 - OpenVPN > Successful ARP Flush on interface [7] {FB4F1D23-4739-45F2-8249-3381886D8E63}
. 2018.02.04 17:00:47 - OpenVPN > do_ifconfig, tt->did_ifconfig_ipv6_setup=0
! 2018.02.04 17:00:47 - Disconnecting
. 2018.02.04 17:00:47 - Routes, removed a route previously added, 185.189.112.12 for gateway 192.168.2.1
. 2018.02.04 17:00:47 - Sending management termination signal
. 2018.02.04 17:00:47 - Management - Send 'signal SIGTERM'
. 2018.02.04 17:00:47 - OpenVPN > MANAGEMENT: CMD 'signal SIGTERM'
. 2018.02.04 17:00:47 - OpenVPN > Closing TUN/TAP interface
. 2018.02.04 17:00:47 - SSL > 2018.02.04 17:00:47 LOG3[0]: readsocket: Connection reset by peer (WSAECONNRESET) (10054)
. 2018.02.04 17:00:47 - SSL > 2018.02.04 17:00:47 LOG5[0]: Connection reset: 3657 byte(s) sent to TLS, 3659 byte(s) sent to socket
. 2018.02.04 17:00:47 - OpenVPN > TAP: DHCP address released
. 2018.02.04 17:00:47 - OpenVPN > SIGTERM[hard,] received, process exiting
. 2018.02.04 17:00:56 - Sending soft termination signal
. 2018.02.04 17:00:56 - Connection terminated.
. 2018.02.04 17:00:56 - IPv6 restored with packet filtering.
I 2018.02.04 17:00:57 - Cancel requested.
I 2018.02.04 17:00:57 - Session terminated.

 

4: on exit i still get this error/appcrash since Eddie 2.13.6:

Eddie 2.13.6:

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: AirVPN.exe
Problem Signature 02: 2.13.0.0
Problem Signature 03: 59c55e32
Problem Signature 04: mscorlib
Problem Signature 05: 4.7.2117.0
Problem Signature 06: 59cf513d
Problem Signature 07: 165d
Problem Signature 08: 198
Problem Signature 09: System.IO.IOException
OS Version: 6.3.9600.2.0.0.256.4
Locale ID: 1031
Additional Information 1: 0c22
Additional Information 2: 0c221678be4c7f105750b6658e71aeca
Additional Information 3: 0897
Additional Information 4: 089739075a8f8aba004048ed8e46b132

 

Eddie 2.14.0:

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: AirVPN.exe
Problem Signature 02: 2.14.0.0
Problem Signature 03: 5a7069c2
Problem Signature 04: mscorlib
Problem Signature 05: 4.7.2117.0
Problem Signature 06: 59cf513d
Problem Signature 07: 165d
Problem Signature 08: 198
Problem Signature 09: System.IO.IOException
OS Version: 6.3.9600.2.0.0.256.4
Locale ID: 1031
Additional Information 1: 0c22
Additional Information 2: 0c221678be4c7f105750b6658e71aeca
Additional Information 3: 0897
Additional Information 4: 089739075a8f8aba004048ed8e46b132

[Clodo 173]

this new version, is not working at all for me on windows 8.1 64bit 

 

1: Settings > General options are a bit "all over the place", if it should look that way then .... ok :/

all-over-the-place.jpg

 

I don't see the issue. The preferences window is resizable.

 

2: Settings > Protocols entries are duplicated again bug/error:

duplicated-again.jpg

 

 

It's correct, the new second set of port/protocol is specific to tls-crypt.

 

3: also getting a Windows WFP, Add rule failed: error?!

 

This is a known bug. This occurs because you have IPv6 disabled at OS or network-adapter level. Please re-enable, or wait for the next release that manages this situation better.

[Clodo 173]

4: on exit i still get this error/appcrash since Eddie 2.13.6:

Eddie 2.13.6:

Problem signature:

Problem Event Name: CLR20r3

Problem Signature 01: AirVPN.exe

Problem Signature 02: 2.13.0.0

Problem Signature 03: 59c55e32

Problem Signature 04: mscorlib

Problem Signature 05: 4.7.2117.0

Problem Signature 06: 59cf513d

Problem Signature 07: 165d

Problem Signature 08: 198

Problem Signature 09: System.IO.IOException

OS Version: 6.3.9600.2.0.0.256.4

Locale ID: 1031

Additional Information 1: 0c22

Additional Information 2: 0c221678be4c7f105750b6658e71aeca

Additional Information 3: 0897

Additional Information 4: 089739075a8f8aba004048ed8e46b132

 

Eddie 2.14.0:

Problem signature:

Problem Event Name: CLR20r3

Problem Signature 01: AirVPN.exe

Problem Signature 02: 2.14.0.0

Problem Signature 03: 5a7069c2

Problem Signature 04: mscorlib

Problem Signature 05: 4.7.2117.0

Problem Signature 06: 59cf513d

Problem Signature 07: 165d

Problem Signature 08: 198

Problem Signature 09: System.IO.IOException

OS Version: 6.3.9600.2.0.0.256.4

Locale ID: 1031

Additional Information 1: 0c22

Additional Information 2: 0c221678be4c7f105750b6658e71aeca

Additional Information 3: 0897

Additional Information 4: 089739075a8f8aba004048ed8e46b132

 

We cannot reproduce this issue.

Please answer:

1- Does it occur EVERY time you close Eddie? Even if you simply launch and close without connection to the VPN?

2- Do you see a dialog error, or is it reported only in Event Viewer?

3- Do you use .exe installer or .zip portable edition?

4- If you download the .zip portable edition, extract to a temporary directory, launch, quit: still crash?

 

Thx.

[blaHbluBB 6]

 

4: on exit i still get this error/appcrash since Eddie 2.13.6:

Eddie 2.13.6:

Problem signature:

Problem Event Name: CLR20r3

Problem Signature 01: AirVPN.exe

Problem Signature 02: 2.13.0.0

Problem Signature 03: 59c55e32

Problem Signature 04: mscorlib

Problem Signature 05: 4.7.2117.0

Problem Signature 06: 59cf513d

Problem Signature 07: 165d

Problem Signature 08: 198

Problem Signature 09: System.IO.IOException

OS Version: 6.3.9600.2.0.0.256.4

Locale ID: 1031

Additional Information 1: 0c22

Additional Information 2: 0c221678be4c7f105750b6658e71aeca

Additional Information 3: 0897

Additional Information 4: 089739075a8f8aba004048ed8e46b132

 

Eddie 2.14.0:

Problem signature:

Problem Event Name: CLR20r3

Problem Signature 01: AirVPN.exe

Problem Signature 02: 2.14.0.0

Problem Signature 03: 5a7069c2

Problem Signature 04: mscorlib

Problem Signature 05: 4.7.2117.0

Problem Signature 06: 59cf513d

Problem Signature 07: 165d

Problem Signature 08: 198

Problem Signature 09: System.IO.IOException

OS Version: 6.3.9600.2.0.0.256.4

Locale ID: 1031

Additional Information 1: 0c22

Additional Information 2: 0c221678be4c7f105750b6658e71aeca

Additional Information 3: 0897

Additional Information 4: 089739075a8f8aba004048ed8e46b132

 

We cannot reproduce this issue.

Please answer:

1- Does it occur EVERY time you close Eddie? Even if you simply launch and close without connection to the VPN?

2- Do you see a dialog error, or is it reported only in Event Viewer?

3- Do you use .exe installer or .zip portable edition?

4- If you download the .zip portable edition, extract to a temporary directory, launch, quit: still crash?

 

Thx.

 

1- Yes and no

2- (sorry my bad, should have posted some pics) these are from 2.13.6

3- .exe installer

 

the other thing i forgot to mention(i don't know if that'll make a difference), my windows is a fresh install (2 days ago) and i tried installing the new beta over the old.

so i uninstalled the beta version and installed it again, and still had the problems i described.

[blaHbluBB 6]

 

this new version, is not working at all for me on windows 8.1 64bit 

 

1: Settings > General options are a bit "all over the place", if it should look that way then .... ok :/

all-over-the-place.jpg

 

I don't see the issue. The preferences window is resizable.

 

>2: Settings > Protocols entries are duplicated again bug/error:

duplicated-again.jpg

 

 

It's correct, the new second set of port/protocol is specific to tls-crypt.

 

3: also getting a Windows WFP, Add rule failed: error?!

 

This is a known bug. This occurs because you have IPv6 disabled at OS or network-adapter level. Please re-enable, or wait for the next release that manages this situation better.

 

 

ok, thanks for answering

 

edit: i've got the 2.14.0 version running now, thanks for the OS level thing.

        the only problem i still have, is the eddie/program exit thing :/

[stookie 4]

 

Well, after using it for the last three days on my Mac (El Capitan 10.11.6) I can say that when it's up and running it works fine - no connection problems so far.

 

However, as I mentioned in a post above, if I try to quit Eddie my whole system freezes and I have to switch off the power to my Mac in order to restart. I tried to get round that by leaving the app running in the background after disconnecting from a server at the end of the night, which was my routine with previous versions of Eddie, but when I switched on my Mac the following morning, I found that Eddie was completely greyed out, including the quit command in the drop down menu.  

 

As no one else seems to have similar problems I can only assume it has something to do with the set-up of my Mac, although I've never had this problem with previous versions of Eddie. At this stage there seems no point in continuing to use it if I have these problems every time I stop using it for any length of time. I had hoped this new version would solve the problems that I had with 2.12 and 2.13, but although it solved those issues the new version has just brought more problems. I can't even submit any logs as the problems only seem to arise after I disconnect from a server.

 

I did notice that there seem to have been some changes in the preferences with this version, and I'm just wondering if perhaps something in there might be causing the problem.

 

As always, any suggestions would be appreciated. 

 

Honestly, the more data you can provide, the easier it will be to debug. If you can't do a screen recording due to the crashing, recording your screen with a cell phone (in decent quality) and uploading it to youtube clearly demonstrating the problem is likely to give the developers more of a clue. It's hard to work with just words alone

 

I have contacted support about my quit/freezing problem, but unfortunately when it happens at the end of a session I am unable to access the Eddie app in any way to obtain any log information due to the fact that it is frozen. The only indication that something is wrong is the little dot still visible next to the Eddie icon in the dock, which indicates that it hasn't fully quit, even though my system thinks it has (see Screen Shot in post #17). I have tried force quitting by every method I can think of, including through the Activity Monitor and the Terminal, but nothing works because they think that Eddie has quit. Even trying to restart my Mac is impossible, unless I resort to switching off the power to it. Naturally, it's not a good idea to keep switching it off in this way.

 

I followed madrat's suggestion and worked my way through the new preferences to see if something there might be the problem, but in order to check if that helped I have to keep trying to quit, and when the changes fail to make a difference I have to switch off the power again and again.

 

The reason I'm continuing to try with Eddie 2.14 is because when I went back to Eddie 2.13 I found that it too now has the same quit/freeze problem, and I now find that 2.12 also has it.

I have tried removing all Eddie versions (and related items) from my Mac and reinstalling them, but without any success. As it only seems to be me having this problem on a Mac, then I can only assume that something occurred when I first installed Eddie 2.14 four or five days ago to upset my system. I have searched on the internet for a solution, but while other people have reported similar problems with other apps, none of them have come up with a way to fix my problem. I have tested all my other apps and all of them are working fine. I have tested for viruses, but everything looks fine there, too.

 

Is it possible that the Eddie program exit problem on Windows that blaHbluBB mentioned above is similar to my problem on a Mac? 

[madrat 19]

 

 

Well, after using it for the last three days on my Mac (El Capitan 10.11.6) I can say that when it's up and running it works fine - no connection problems so far.

 

However, as I mentioned in a post above, if I try to quit Eddie my whole system freezes and I have to switch off the power to my Mac in order to restart. I tried to get round that by leaving the app running in the background after disconnecting from a server at the end of the night, which was my routine with previous versions of Eddie, but when I switched on my Mac the following morning, I found that Eddie was completely greyed out, including the quit command in the drop down menu.  

 

As no one else seems to have similar problems I can only assume it has something to do with the set-up of my Mac, although I've never had this problem with previous versions of Eddie. At this stage there seems no point in continuing to use it if I have these problems every time I stop using it for any length of time. I had hoped this new version would solve the problems that I had with 2.12 and 2.13, but although it solved those issues the new version has just brought more problems. I can't even submit any logs as the problems only seem to arise after I disconnect from a server.

 

I did notice that there seem to have been some changes in the preferences with this version, and I'm just wondering if perhaps something in there might be causing the problem.

 

As always, any suggestions would be appreciated. 

 

Honestly, the more data you can provide, the easier it will be to debug. If you can't do a screen recording due to the crashing, recording your screen with a cell phone (in decent quality) and uploading it to youtube clearly demonstrating the problem is likely to give the developers more of a clue. It's hard to work with just words alone

 

I have contacted support about my quit/freezing problem, but unfortunately when it happens at the end of a session I am unable to access the Eddie app in any way to obtain any log information due to the fact that it is frozen. The only indication that something is wrong is the little dot still visible next to the Eddie icon in the dock, which indicates that it hasn't fully quit, even though my system thinks it has (see Screen Shot in post #17). I have tried force quitting by every method I can think of, including through the Activity Monitor and the Terminal, but nothing works because they think that Eddie has quit. Even trying to restart my Mac is impossible, unless I resort to switching off the power to it. Naturally, it's not a good idea to keep switching it off in this way.

 

I followed madrat's suggestion and worked my way through the new preferences to see if something there might be the problem, but in order to check if that helped I have to keep trying to quit, and when the changes fail to make a difference I have to switch off the power again and again.

 

The reason I'm continuing to try with Eddie 2.14 is because when I went back to Eddie 2.13 I found that it too now has the same quit/freeze problem, and I now find that 2.12 also has it.

I have tried removing all Eddie versions (and related items) from my Mac and reinstalling them, but without any success. As it only seems to be me having this problem on a Mac, then I can only assume that something occurred when I first installed Eddie 2.14 four or five days ago to upset my system. I have searched on the internet for a solution, but while other people have reported similar problems with other apps, none of them have come up with a way to fix my problem. I have tested all my other apps and all of them are working fine. I have tested for viruses, but everything looks fine there, too.

 

Is it possible that the Eddie program exit problem on Windows that blaHbluBB mentioned above is similar to my problem on a Mac? 

 

Very frustrating stookie. Have you tried removing Eddie with a program such as "AppDelete" and then reinstalling? It seems very strange that we are both running El Capitan and I have had no "freezing" problem. My problem when updating to 2.14 was very strange. When trying to connect the first time, it kept getting stuck at "Checking Route IPV4". After several reboots and several tries reconnecting, I still had the same problem. I decided to reinstall 2.13.6 over 2.14 and presto, after another reboot, it connected no problem. However, after checking the version, it was in fact still 2.14 and not 2.13.6. Figure. But since that, everything has worked fine, so I'm leaving as is! I had no similar problems updating to 2.14 on my MacBook Pro running Sierra.

[stookie 4]

 

 

 

Well, after using it for the last three days on my Mac (El Capitan 10.11.6) I can say that when it's up and running it works fine - no connection problems so far.

 

However, as I mentioned in a post above, if I try to quit Eddie my whole system freezes and I have to switch off the power to my Mac in order to restart. I tried to get round that by leaving the app running in the background after disconnecting from a server at the end of the night, which was my routine with previous versions of Eddie, but when I switched on my Mac the following morning, I found that Eddie was completely greyed out, including the quit command in the drop down menu.  

 

As no one else seems to have similar problems I can only assume it has something to do with the set-up of my Mac, although I've never had this problem with previous versions of Eddie. At this stage there seems no point in continuing to use it if I have these problems every time I stop using it for any length of time. I had hoped this new version would solve the problems that I had with 2.12 and 2.13, but although it solved those issues the new version has just brought more problems. I can't even submit any logs as the problems only seem to arise after I disconnect from a server.

 

I did notice that there seem to have been some changes in the preferences with this version, and I'm just wondering if perhaps something in there might be causing the problem.

 

As always, any suggestions would be appreciated. 

 

Honestly, the more data you can provide, the easier it will be to debug. If you can't do a screen recording due to the crashing, recording your screen with a cell phone (in decent quality) and uploading it to youtube clearly demonstrating the problem is likely to give the developers more of a clue. It's hard to work with just words alone

 

I have contacted support about my quit/freezing problem, but unfortunately when it happens at the end of a session I am unable to access the Eddie app in any way to obtain any log information due to the fact that it is frozen. The only indication that something is wrong is the little dot still visible next to the Eddie icon in the dock, which indicates that it hasn't fully quit, even though my system thinks it has (see Screen Shot in post #17). I have tried force quitting by every method I can think of, including through the Activity Monitor and the Terminal, but nothing works because they think that Eddie has quit. Even trying to restart my Mac is impossible, unless I resort to switching off the power to it. Naturally, it's not a good idea to keep switching it off in this way.

 

I followed madrat's suggestion and worked my way through the new preferences to see if something there might be the problem, but in order to check if that helped I have to keep trying to quit, and when the changes fail to make a difference I have to switch off the power again and again.

 

The reason I'm continuing to try with Eddie 2.14 is because when I went back to Eddie 2.13 I found that it too now has the same quit/freeze problem, and I now find that 2.12 also has it.

I have tried removing all Eddie versions (and related items) from my Mac and reinstalling them, but without any success. As it only seems to be me having this problem on a Mac, then I can only assume that something occurred when I first installed Eddie 2.14 four or five days ago to upset my system. I have searched on the internet for a solution, but while other people have reported similar problems with other apps, none of them have come up with a way to fix my problem. I have tested all my other apps and all of them are working fine. I have tested for viruses, but everything looks fine there, too.

 

Is it possible that the Eddie program exit problem on Windows that blaHbluBB mentioned above is similar to my problem on a Mac? 

Very frustrating stookie. Have you tried removing Eddie with a program such as "AppDelete" and then reinstalling? It seems very strange that we are both running El Capitan and I have had no "freezing" problem. My problem when updating to 2.14 was very strange. When trying to connect the first time, it kept getting stuck at "Checking Route IPV4". After several reboots and several tries reconnecting, I still had the same problem. I decided to reinstall 2.13.6 over 2.14 and presto, after another reboot, it connected no problem. However, after checking the version, it was in fact still 2.14 and not 2.13.6. Figure. But since that, everything has worked fine, so I'm leaving as is! I had no similar problems updating to 2.14 on my MacBook Pro running Sierra.

 

Yes, I've been using AppCleaner to remove the various versions of Eddie, but so far it doesn't seem to help. As you are also running El Capitan, I'm wondering what your set-up is regarding IPv6 on your Mac - currently IPv6 is disabled on my Mac, so maybe that is interfering with things, although I can't work out what it would be. There seems to be a new tab in Eddie preferences dealing with IPv4 and IPv6 connections, as well.

 

I notice also that your solution to the PF Firewall problem - that is, to uncheck allow ping in preferences - seems to have been adopted in the preferences for 2.14. So, was that the solution to that problem all along - I always thought that allow ping had to be rechecked after connection on 2.13.

 

Hopefully, support will be able to suggest a solution for me, although I'm not holding my breath after all the problems I've had over the past few months.

[madrat 19]

 

 

 

 

Well, after using it for the last three days on my Mac (El Capitan 10.11.6) I can say that when it's up and running it works fine - no connection problems so far.

 

However, as I mentioned in a post above, if I try to quit Eddie my whole system freezes and I have to switch off the power to my Mac in order to restart. I tried to get round that by leaving the app running in the background after disconnecting from a server at the end of the night, which was my routine with previous versions of Eddie, but when I switched on my Mac the following morning, I found that Eddie was completely greyed out, including the quit command in the drop down menu.  

 

As no one else seems to have similar problems I can only assume it has something to do with the set-up of my Mac, although I've never had this problem with previous versions of Eddie. At this stage there seems no point in continuing to use it if I have these problems every time I stop using it for any length of time. I had hoped this new version would solve the problems that I had with 2.12 and 2.13, but although it solved those issues the new version has just brought more problems. I can't even submit any logs as the problems only seem to arise after I disconnect from a server.

 

I did notice that there seem to have been some changes in the preferences with this version, and I'm just wondering if perhaps something in there might be causing the problem.

 

As always, any suggestions would be appreciated. 

 

Honestly, the more data you can provide, the easier it will be to debug. If you can't do a screen recording due to the crashing, recording your screen with a cell phone (in decent quality) and uploading it to youtube clearly demonstrating the problem is likely to give the developers more of a clue. It's hard to work with just words alone

 

I have contacted support about my quit/freezing problem, but unfortunately when it happens at the end of a session I am unable to access the Eddie app in any way to obtain any log information due to the fact that it is frozen. The only indication that something is wrong is the little dot still visible next to the Eddie icon in the dock, which indicates that it hasn't fully quit, even though my system thinks it has (see Screen Shot in post #17). I have tried force quitting by every method I can think of, including through the Activity Monitor and the Terminal, but nothing works because they think that Eddie has quit. Even trying to restart my Mac is impossible, unless I resort to switching off the power to it. Naturally, it's not a good idea to keep switching it off in this way.

 

I followed madrat's suggestion and worked my way through the new preferences to see if something there might be the problem, but in order to check if that helped I have to keep trying to quit, and when the changes fail to make a difference I have to switch off the power again and again.

 

The reason I'm continuing to try with Eddie 2.14 is because when I went back to Eddie 2.13 I found that it too now has the same quit/freeze problem, and I now find that 2.12 also has it.

I have tried removing all Eddie versions (and related items) from my Mac and reinstalling them, but without any success. As it only seems to be me having this problem on a Mac, then I can only assume that something occurred when I first installed Eddie 2.14 four or five days ago to upset my system. I have searched on the internet for a solution, but while other people have reported similar problems with other apps, none of them have come up with a way to fix my problem. I have tested all my other apps and all of them are working fine. I have tested for viruses, but everything looks fine there, too.

 

Is it possible that the Eddie program exit problem on Windows that blaHbluBB mentioned above is similar to my problem on a Mac? 

Very frustrating stookie. Have you tried removing Eddie with a program such as "AppDelete" and then reinstalling? It seems very strange that we are both running El Capitan and I have had no "freezing" problem. My problem when updating to 2.14 was very strange. When trying to connect the first time, it kept getting stuck at "Checking Route IPV4". After several reboots and several tries reconnecting, I still had the same problem. I decided to reinstall 2.13.6 over 2.14 and presto, after another reboot, it connected no problem. However, after checking the version, it was in fact still 2.14 and not 2.13.6. Figure. But since that, everything has worked fine, so I'm leaving as is! I had no similar problems updating to 2.14 on my MacBook Pro running Sierra.

Yes, I've been using AppCleaner to remove the various versions of Eddie, but so far it doesn't seem to help. As you are also running El Capitan, I'm wondering what your set-up is regarding IPv6 on your Mac - currently IPv6 is disabled on my Mac, so maybe that is interfering with things, although I can't work out what it would be. There seems to be a new tab in Eddie preferences dealing with IPv4 and IPv6 connections, as well.

 

I notice also that your solution to the PF Firewall problem - that is, to uncheck allow ping in preferences - seems to have been adopted in the preferences for 2.14. So, was that the solution to that problem all along - I always thought that allow ping had to be rechecked after connection on 2.13.

 

Hopefully, support will be able to suggest a solution for me, although I'm not holding my breath after all the problems I've had over the past few months.

 

I read that IPv6 should be enabled and I saw in one of the forums how to enable it using Terminal, so I did so, although I also read somewhere that it was automatically enabled on a mac anyway. See if this may help: http://osxdaily.com/2014/04/18/disable-ipv6-mac-os-x/

[Guest]

Memory leak on Linux seem to persist.

 

see https://airvpn.org/topic/23911-eddie-client-memory-leak-on-linux/page-2?do=findComment&comment=69197

[H8SOCIETY 7]

WIN 8.1 x64:

 

No connection possible if "remove the gateway route" is checked.

After uncheck connection to servers possible.

 

In tap adapter there is no specific dns entry for ipv6. is that correct ?

 

 

EDIT: Back to 2.13.6, because network lock (Windows Firewall) was not working every time.

[stookie 4]

Have you tried removing Eddie with a program such as "AppDelete" and then reinstalling? It seems very strange that we are both running El Capitan and I have had no "freezing" problem.  ... I decided to reinstall 2.13.6 over 2.14 and presto, after another reboot, it connected no problem. However, after checking the version, it was in fact still 2.14 and not 2.13.6. Figure. But since that, everything has worked fine, so I'm leaving as is!

 

If I might ask one last question about this quit/freezing problem that I'm now having with all versions of Eddie, whether 2.14 or earlier versions:

 

Last night I removed all trace of Eddie from my system using AppCleaner, and then re-downloaded and re-installed Eddie 2.13 in the hope that it would quit as normal, but as is the case with all versions of Eddie that I use now, it froze completely and required a complete shutdown of my Mac.

 

It was my belief that by re-installing it in this way the preferences would have reverted to the default setting, as if it was being installed for the first time, and given me a clean start; however, when I checked I noticed that my customised preference settings from the previous installation were still in place.

 

So, I'm wondering if this indicates that there are still some traces of Eddie 2.14 hidden on my system somewhere that AppCleaner can't detect. Is anyone aware of a Terminal command that will reveal them to me so that I can finally remove them and then go back to a clean start with Eddie 2.13? Needless to say, I'll be asking support for their help, too.

 

Thanks

[madrat 19]

 

Have you tried removing Eddie with a program such as "AppDelete" and then reinstalling? It seems very strange that we are both running El Capitan and I have had no "freezing" problem.  ... I decided to reinstall 2.13.6 over 2.14 and presto, after another reboot, it connected no problem. However, after checking the version, it was in fact still 2.14 and not 2.13.6. Figure. But since that, everything has worked fine, so I'm leaving as is!

 

If I might ask one last question about this quit/freezing problem that I'm now having with all versions of Eddie, whether 2.14 or earlier versions:

 

Last night I removed all trace of Eddie from my system using AppCleaner, and then re-downloaded and re-installed Eddie 2.13 in the hope that it would quit as normal, but as is the case with all versions of Eddie that I use now, it froze completely and required a complete shutdown of my Mac.

 

It was my belief that by re-installing it in this way the preferences would have reverted to the default setting, as if it was being installed for the first time, and given me a clean start; however, when I checked I noticed that my customised preference settings from the previous installation were still in place.

 

So, I'm wondering if this indicates that there are still some traces of Eddie 2.14 hidden on my system somewhere that AppCleaner can't detect. Is anyone aware of a Terminal command that will reveal them to me so that I can finally remove them and then go back to a clean start with Eddie 2.13? Needless to say, I'll be asking support for their help, too.

 

Thanks

 

"Reset to default settings" in preferences would not do this?

[stookie 4]

 

 

Have you tried removing Eddie with a program such as "AppDelete" and then reinstalling? It seems very strange that we are both running El Capitan and I have had no "freezing" problem.  ... I decided to reinstall 2.13.6 over 2.14 and presto, after another reboot, it connected no problem. However, after checking the version, it was in fact still 2.14 and not 2.13.6. Figure. But since that, everything has worked fine, so I'm leaving as is!

 

If I might ask one last question about this quit/freezing problem that I'm now having with all versions of Eddie, whether 2.14 or earlier versions:

 

Last night I removed all trace of Eddie from my system using AppCleaner, and then re-downloaded and re-installed Eddie 2.13 in the hope that it would quit as normal, but as is the case with all versions of Eddie that I use now, it froze completely and required a complete shutdown of my Mac.

 

It was my belief that by re-installing it in this way the preferences would have reverted to the default setting, as if it was being installed for the first time, and given me a clean start; however, when I checked I noticed that my customised preference settings from the previous installation were still in place.

 

So, I'm wondering if this indicates that there are still some traces of Eddie 2.14 hidden on my system somewhere that AppCleaner can't detect. Is anyone aware of a Terminal command that will reveal them to me so that I can finally remove them and then go back to a clean start with Eddie 2.13? Needless to say, I'll be asking support for their help, too.

 

Thanks

 

"Reset to default settings" in preferences would not do this?

 

Yes, but what I'm asking is why were the preferences not set to default after I removed all versions of Eddie from my system before re-downloading and re-installing. If it is a completely new download of Eddie that I am installing, then how can it remember my preferences from before - unless there is still something on my system from the previous download. Surely it should start afresh with the preferences set to default. If I can get a completely new version of Eddie 2.13.6 to install, then perhaps it won't inherit the quit/freeze problem from my earlier problematic installation of 2.14. It's only since my problems with 2.14 that I am now having the same problem with 2.12 and 2.13 - as if the overlapping problems that occurred with 2.14 on your system might also have happened to me, thereby 'infecting' 2.12 and 2.13 with the same quit problem.

 

So, basically what I want to do is remove all traces of Eddie 2.14 from my system, then start anew with a fresh download of Eddie 2.13.6, as if it was being installed for the first time.

[Staff 9950]

 

So, basically what I want to do is remove all traces of Eddie 2.14 from my system

 

Hello,

 

please make sure to delete AirVPN.xml, the configuration file..

 

Kind regards

[stookie 4]

 

 

So, basically what I want to do is remove all traces of Eddie 2.14 from my system

 

Hello,

 

please make sure to delete AirVPN.xml, the configuration file..

 

Kind regards

 

Thanks, Staff. I tried that but no file was found. 

 

Can madrat please open up Activity Monitor, and look for Eddie under the CPU tab and then check under the User column to see if Eddie is running under 'his/her name' or as 'root'.

Eddie is the only app I have that is running as 'root', all others are under 'my name'. I have read elsewhere that it isn't wise to run apps as 'root' because "the Mac OS X frameworks are not intended to be used this way, and undesirable behaviour will result (e.g, files/folders owned by root in the user's Library; process not responsive to "force quit"; potential security vulnerabilities)."

 

Now that sounds pretty much like the problems I've been having since downloading Eddie 2.14. Perhaps madrat or someone else can check for me, please?

 

Staff are continuing to help me, but I'm hoping that other Mac users can give me their feedback.

[george493 2]

Running Eddie 2.14.0 for 10 hrs now, on Xubuntu 17.10.1, no problems, a considerable lessening on system resources, including CPU. Default preferences, IPv4 and Ipv6

[madrat 19]

 

 

 

So, basically what I want to do is remove all traces of Eddie 2.14 from my system

 

Hello,

 

please make sure to delete AirVPN.xml, the configuration file..

 

Kind regards

 

Thanks, Staff. I tried that but no file was found. 

 

Can madrat please open up Activity Monitor, and look for Eddie under the CPU tab and then check under the User column to see if Eddie is running under 'his/her name' or as 'root'.

Eddie is the only app I have that is running as 'root', all others are under 'my name'. I have read elsewhere that it isn't wise to run apps as 'root' because "the Mac OS X frameworks are not intended to be used this way, and undesirable behaviour will result (e.g, files/folders owned by root in the user's Library; process not responsive to "force quit"; potential security vulnerabilities)."

 

Now that sounds pretty much like the problems I've been having since downloading Eddie 2.14. Perhaps madrat or someone else can check for me, please?

 

Staff are continuing to help me, but I'm hoping that other Mac users can give me their feedback.

 

Both Eddie and openvpn are running as "root". I have many programs running as "root".

[madrat 19]

 

 

 

 

So, basically what I want to do is remove all traces of Eddie 2.14 from my system

Hello,

 

please make sure to delete AirVPN.xml, the configuration file..

 

Kind regards

Thanks, Staff. I tried that but no file was found. 

 

Can madrat please open up Activity Monitor, and look for Eddie under the CPU tab and then check under the User column to see if Eddie is running under 'his/her name' or as 'root'.

Eddie is the only app I have that is running as 'root', all others are under 'my name'. I have read elsewhere that it isn't wise to run apps as 'root' because "the Mac OS X frameworks are not intended to be used this way, and undesirable behaviour will result (e.g, files/folders owned by root in the user's Library; process not responsive to "force quit"; potential security vulnerabilities)."

 

Now that sounds pretty much like the problems I've been having since downloading Eddie 2.14. Perhaps madrat or someone else can check for me, please?

 

Staff are continuing to help me, but I'm hoping that other Mac users can give me their feedback.

Just another thought. Would booting into safe mode and using Appdelete to remove Eddie work?

[harold.lewis 21]

Eddie 2.14.0 Portable Linux_x64 on Manjaro Plasma, ipv6 disable system wide

 

seems to work fine except for tray icon

[Guest]

Running 2.14.0 for 80 hours on ubuntu 16.04.

 

resident memory usage is 1.8 gb.

 

the memory leak I've had in earlier versions seem to persist.

[InfiniteInt 0]

I've been trying to pinpoint my problem, but I had no luck so far. As soon as I start the client I get a window asking me to provide a custom bootstrap URL. I can click cancel, but it pops up again and again. My system is a cleanly installed win10 pro. accessing the internet works while being connected to the vpn.
 
The log shows a messed up character encoding while eddie tries to fetch new server data.

 

I've attached the log of eddie.

Eddie_20180208_094615.txt

[Staff 9950]

@InfiniteInt

Eddie 2.14beta allows entering custom manifest URL (for example if Fortinet blacklists all auth servers), as you might have seen in the changelog. It looks like you just need this new feature. Please open a ticket.

 

Kind regards

[Staff 9950]

Running 2.14.0 for 80 hours on ubuntu 16.04.

 

resident memory usage is 1.8 gb.

 

the memory leak I've had in earlier versions seem to persist.

 

Hello,

 

please see here in order to avoid common pitfalls when you measure memory (even resident memory) usage of a process:

https://stackoverflow.com/questions/131303/how-to-measure-actual-memory-usage-of-an-application-or-process

 

Can you confirm your quote after you have taken care of the above (make sure to not measure the resident shared memory etc. etc.).?

 

Kind regards