ANSWERED Cannot login to Eddie, or access airvpn.org

[tuttiface 0]

Hello! I've been having an issue since last night, for some reason I cannot access airvpn services, when trying to login on Eddie it goes through a very long "checking login..." Then gives me an error message stating Airvpn was unable to obtain bootstrap information. My first instinct was to come here and post, but then I realized I could no longer access this website on my home network(airvpn.org took too long to respond), so I've had to use my phone to post this. Very strange, I've used Airvpn for about 5 or so years I believe, and I have never had an issue like this in the past. Any help is greatly appreciated.

[Rebelyouth 1]

Same here

[tuttiface 0]

13 minutes ago, Rebelyouth said:

Same here

Ah, hopefully an Admin can chime in and help us to remedy the issue.

[Tex257 0]

Same. Got a couple of replies from support but none helped. Tried different devices, diff OS, Tried using cell data from a diff carrier than my isp. Problems no matter what. I could connect thru my cellular carrier but couldn’t connect to ANY website via browser once connected to the VPN. Disconnect and I am able using cell data to view and login to the website. 

[jhonatan 0]

Same here. I cannot login to Eddie and I cannot access to the airvpn website. In order to write this post I had to use the tor browser in whonix. I can only access the airvpn website if I use an online proxy or the tor browser.

[Rebelyouth 1]

Finally is connecting. Airvpn and ipleak are accessible only if I am on VPN.

If I disconnect, I can 't connect to them, other web sites are fine.

[tuttiface 0]

5 hours ago, Rebelyouth said:

Finally is connecting. Airvpn and ipleak are accessible only if I am on VPN.

If I disconnect, I can 't connect to them, other web sites are fine.

Unfortunately I still cannot connect to Eddie, Airvpn or ipleak

[Staff 9972]

Hello,
we have experienced a problem with VPN server LetsEncrypt certificates deployment. The system procedure got stuck and failed to deploy updated certificates. In turn, such a failure caused "route check" failures on Eddie desktop editions, and ONLY on them, due to expired certificates verified by cURL during the route check phase.

The problem has been affecting a wide amount of VPN servers for about 8 hours and has been resolved completely now. We deeply apologize for any inconvenience.

IMPORTANT: you also mention different problems (access to web sites etc.) which are probably different and separate and that we do not reproduce. For them, please open a ticket.

Kind regards
 

[tuttiface 0]

8 hours ago, Staff said:

Hello,
we have experienced a problem with VPN server LetsEncrypt certificates deployment. The system procedure got stuck and failed to deploy updated certificates. In turn, such a failure caused "route check" failures on Eddie desktop editions, and ONLY on them, due to expired certificates verified by cURL during the route check phase.

The problem has been affecting a wide amount of VPN servers for about 8 hours and has been resolved completely now. We deeply apologize for any inconvenience.

IMPORTANT: you also mention different problems (access to web sites etc.) which are probably different and separate and that we do not reproduce. For them, please open a ticket.

Kind regards
 

Hello, thanks for your reply regarding the issue, however I am still unable to login through Eddie with the same error persisting. Also the inability to access airvpn.org and ipleak seems to have happened simultaneously, with the inability to log on with eddie.

Regards.



 

[tafn 0]

EDIT: My apologies, I didn't see the answer above. Please disregard.

Had the same problem, but it fails at checking route for IP4 (just disconnects). The service was working for one machine that had been connected most of the day, the other suddentley failed. When I tried a new server with the first it too failed.

I got the problem using the client configurator to get opvn files, then install and use OpenVPN GUI directly, but I hope to be able to use Eddie UI soon.

Edited ... by tafn
Tired, didn't see it being answered. Sorry.

[rabidwolv 0]

I am having the same issue as the internet works but cant login to eddie and cant access the airvpn.org site and ipleak.net unless I use openvpn software using the config files.

[Staff 9972]

Hello!

Ok, so this might be some new type of block against AirVPN, ignore our previous message related to a momentary problem on our side which is now resolved. Would it be possible to collect info about your ISP, a system report from Eddie, and also whether you can access airvpn.info or not? The block against ipleak.net is particularly puzzling as it is not in the AirVPN pool of servers of any kind...

And also antivirus, packet filtering tools, "Internet security" suites if you run them, as we should not assume prematurely that the block comes from the ISP, it could be local.

traceroute to airvpn.org, ipleak.net and airvpn.info might help as well to understand the nature of the block (or maybe of some transient routing problem).

Kind regards
 

[Yet another user 0]

Similar deal here. Still can't log in in Eddie or reach airvpn.info, but I can reach airvpn.org. This happens in both Windows and Linux; neither is running any security or filtering software except Windows Defender. My ISP is Charter.
 

$ traceroute airvpn.info
traceroute to airvpn.info (54.93.175.114), 30 hops max, 60 byte packets
 1  OpenWrt.lan (192.168.1.1)  1.906 ms  1.963 ms  3.272 ms
 2  * * *
 3  cts05wrcsma-tge-1-0-0.wrcs.ma.charter.com (96.34.84.169)  17.696 ms  20.598 ms  21.057 ms
 4  dtr02davlvt-tge-0-0-1-3.davl.vt.charter.com (96.34.84.212)  22.218 ms  22.214 ms  22.208 ms
 5  bbr01gdisne-bue-2.gdis.ne.charter.com (96.34.2.142)  22.204 ms  22.194 ms  22.189 ms
 6  bbr01nwtwct-bue-4.nwtw.ct.charter.com (96.34.0.51)  25.936 ms  24.076 ms  23.041 ms
 7  bbr01blvlil-tge-0-0-0-11.blvl.il.charter.com (96.34.0.137)  27.467 ms  42.338 ms  46.915 ms
 8  prr01ashbva-bue-6.ashb.va.charter.com (96.34.3.89)  44.833 ms  43.635 ms  42.435 ms
 9  * lag-35.ear2.WashintgonDC12.Level3.net (4.68.74.61)  43.621 ms *
10  * * *
11  212.73.243.150 (212.73.243.150)  116.391 ms  112.251 ms 212.73.243.158 (212.73.243.158)  95.980 ms
12  52.95.60.70 (52.95.60.70)  98.089 ms 52.95.60.86 (52.95.60.86)  108.757 ms 52.95.60.118 (52.95.60.118)  104.171 ms
13  52.95.60.47 (52.95.60.47)  103.722 ms 52.95.60.129 (52.95.60.129)  101.961 ms 52.95.60.125 (52.95.60.125)  100.516 ms
14  * * *
15  52.93.134.157 (52.93.134.157)  109.378 ms 52.93.134.109 (52.93.134.109)  116.495 ms 52.93.134.157 (52.93.134.157)  116.389 ms
16  * * *
17  54.239.106.106 (54.239.106.106)  142.616 ms 54.239.106.42 (54.239.106.42)  142.595 ms 54.239.106.64 (54.239.106.64)  142.580 ms
18  52.93.111.252 (52.93.111.252)  142.549 ms 52.93.111.222 (52.93.111.222)  142.213 ms 52.93.111.210 (52.93.111.210)  142.036 ms
19  52.93.111.249 (52.93.111.249)  142.527 ms 52.93.111.217 (52.93.111.217)  113.291 ms 52.93.111.223 (52.93.111.223)  117.763 ms
20  54.239.106.139 (54.239.106.139)  120.772 ms 54.239.106.73 (54.239.106.73)  116.426 ms 54.239.106.51 (54.239.106.51)  115.393 ms
21  52.93.23.130 (52.93.23.130)  118.016 ms  119.006 ms 54.239.5.172 (54.239.5.172)  124.886 ms
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Eddie System/Environment Report - 8/18/2019 10:54 PM UTC

Eddie version: 2.16.3
Eddie OS build: linux_x64
Eddie architecture: x64
OS type: Linux
OS name: Linux Mint 19 Tara \n \l
OS version: Linux chinmoku 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
OS architecture: x64
Mono /.Net Framework: 4.6.2 (Debian 4.6.2.7+dfsg-1ubuntu1); Framework: v4.0.30319
OpenVPN driver: Found, /dev/net/tun
OpenVPN: 2.4.4 - OpenSSL 1.1.1  11 Sep 2018, LZO 2.08 (/usr/sbin/openvpn)
SSH: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017 (/usr/bin/ssh)
SSL: stunnel 5.44 (/usr/bin/stunnel4)
curl: 7.58.0 (/usr/bin/curl)
Profile path: /home/user/.airvpn/default.xml
Data path: /home/user/.airvpn
Application path: /usr/lib/eddie-ui
Executable path: /usr/lib/eddie-ui/Eddie-UI.exe
Command line arguments: (5 args) path="/home/user/.airvpn" path.resources="/usr/share/eddie-ui" path.exec="/usr/bin/eddie-ui" console.mode="none" linux.dbus="unix:path=/run/user/1000/bus"
Network Lock Active: Yes, Linux iptables
Connected to VPN: No
Detected DNS: 127.0.0.53
Test DNS IPv4: Ok
Test DNS IPv6: Ok
Test Ping IPv4: -1 ms
Test Ping IPv6: 19 ms
Test HTTP IPv4: Error:curl: (28) Connection timed out after 20000 milliseconds
Test HTTP IPv6: Error:curl: (28) Connection timed out after 20001 milliseconds
Test HTTPS: Error:curl: (7) Failed to connect to eddie.website port 443: Connection timed out
----------------------------
Important options not at defaults:

netlock: True
ui.skip.provider.manifest.failed: True
gui.notifications: False

----------------------------
Logs:

. 2019.08.18 18:51:34 - Eddie version: 2.16.3 / linux_x64, System: Linux, Name: Linux Mint 19 Tara \n \l, Version: Linux chinmoku 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux, Mono/.Net: 4.6.2 (Debian 4.6.2.7+dfsg-1ubuntu1); Framework: v4.0.30319
. 2019.08.18 18:51:34 - Reading options from /home/user/.airvpn/default.xml
. 2019.08.18 18:51:35 - Command line arguments (5): path="/home/user/.airvpn" path.resources="/usr/share/eddie-ui" path.exec="/usr/bin/eddie-ui" console.mode="none" linux.dbus="unix:path=/run/user/1000/bus"
. 2019.08.18 18:51:35 - Profile path: /home/user/.airvpn/default.xml
. 2019.08.18 18:51:36 - OpenVPN Driver - Found, /dev/net/tun
. 2019.08.18 18:51:36 - OpenVPN - Version: 2.4.4 - OpenSSL 1.1.1  11 Sep 2018, LZO 2.08 (/usr/sbin/openvpn)
. 2019.08.18 18:51:36 - SSH - Version: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017 (/usr/bin/ssh)
. 2019.08.18 18:51:36 - SSL - Version: stunnel 5.44 (/usr/bin/stunnel4)
. 2019.08.18 18:51:36 - curl - Version: 7.58.0 (/usr/bin/curl)
. 2019.08.18 18:51:36 - Certification Authorities: /usr/share/eddie-ui/cacert.pem
! 2019.08.18 18:51:36 - Activation of Network Lock - Linux iptables
. 2019.08.18 18:51:36 - Updating systems & servers data ...
I 2019.08.18 18:51:45 - Ready
. 2019.08.18 18:52:57 - Cannot retrieve systems & servers data. (curl: (28) Connection timed out after 20001 milliseconds)

----------------------------
Network Interfaces and Routes:

{
    "support_ipv4": true,
    "support_ipv6": true,
    "routes": [
        {
            "address": "0.0.0.0\/0",
            "gateway": "192.168.1.1",
            "interface": "wlp26s0",
            "metric": "20600"
        },
        {
            "address": "fd83:e6d4:9fb1::\/48",
            "gateway": "fe80::204e:7fff:fe85:e611",
            "interface": "wlp26s0",
            "metric": "600"
        },
        {
            "address": "::\/0",
            "gateway": "fe80::204e:7fff:fe85:e611",
            "interface": "wlp26s0",
            "metric": "20600"
        }
    ],
    "interfaces": [
        {
            "friendly": "lo",
            "id": "lo",
            "name": "lo",
            "description": "lo",
            "type": "Loopback",
            "status": "Unknown",
            "bytes_received": "297980",
            "bytes_sent": "297980",
            "support_ipv4": true,
            "support_ipv6": true,
            "ips": [
                "127.0.0.1",
                "::1"
            ],
            "gateways": [],
            "bind": true
        },
        {
            "friendly": "eno1",
            "id": "eno1",
            "name": "eno1",
            "description": "eno1",
            "type": "Ethernet",
            "status": "Down",
            "bytes_received": "0",
            "bytes_sent": "0",
            "support_ipv4": true,
            "support_ipv6": true,
            "ips": [],
            "gateways": [],
            "bind": false
        },
        {
            "friendly": "wlp26s0",
            "id": "wlp26s0",
            "name": "wlp26s0",
            "description": "wlp26s0",
            "type": "Wireless80211",
            "status": "Up",
            "bytes_received": "11908363",
            "bytes_sent": "606050",
            "support_ipv4": true,
            "support_ipv6": true,
            "ips": [
                "192.168.1.199",
                "fd83:e6d4:9fb1::30c",
                "2600:6c64:607f:f19b::30c",
                "fd83:e6d4:9fb1:0:fee0:99bf:d3e9:ca1",
                "2600:6c64:607f:f19b:600:7ca9:450:57a0",
                "fe80::3bcc:9aea:34e:6061"
            ],
            "gateways": [
                "192.168.1.1",
                "fe80::204e:7fff:fe85:e611"
            ],
            "bind": true
        }
    ],
    "ipv4-default-gateway": "192.168.1.1",
    "ipv4-default-interface": "wlp26s0",
    "ipv6-default-gateway": "fe80::204e:7fff:fe85:e611",
    "ipv6-default-interface": "wlp26s0"
}
----------------------------
UID: 0
Run as normal user: True; ID:1000; Name:user
----------------------------
ip addr show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 30:9c:23:a8:87:2e brd ff:ff:ff:ff:ff:ff
3: wlp26s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether d4:6d:6d:a6:e1:c7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.199/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp26s0
       valid_lft 41669sec preferred_lft 41669sec
    inet6 fd83:e6d4:9fb1::30c/128 scope global dynamic noprefixroute 
       valid_lft 84872sec preferred_lft 84872sec
    inet6 2600:6c64:607f:f19b::30c/128 scope global dynamic noprefixroute 
       valid_lft 84872sec preferred_lft 84872sec
    inet6 fd83:e6d4:9fb1:0:fee0:99bf:d3e9:ca1/64 scope global dynamic noprefixroute 
       valid_lft 7185sec preferred_lft 1785sec
    inet6 2600:6c64:607f:f19b:600:7ca9:450:57a0/64 scope global dynamic noprefixroute 
       valid_lft 7185sec preferred_lft 1785sec
    inet6 fe80::3bcc:9aea:34e:6061/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
----------------------------
ip link show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 30:9c:23:a8:87:2e brd ff:ff:ff:ff:ff:ff
3: wlp26s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether d4:6d:6d:a6:e1:c7 brd ff:ff:ff:ff:ff:ff
----------------------------
ip -4 route show:

default via 192.168.1.1 dev wlp26s0 proto dhcp metric 20600 
169.254.0.0/16 dev wlp26s0 scope link metric 1000 
192.168.1.0/24 dev wlp26s0 proto kernel scope link src 192.168.1.199 metric 600
----------------------------
ip -6 route show:

2600:6c64:607f:f19b::30c dev wlp26s0 proto kernel metric 600 pref medium
2600:6c64:607f:f19b::/64 dev wlp26s0 proto ra metric 600 pref medium
fd83:e6d4:9fb1::30c dev wlp26s0 proto kernel metric 600 pref medium
fd83:e6d4:9fb1::/64 dev wlp26s0 proto ra metric 600 pref medium
fd83:e6d4:9fb1::/48 via fe80::204e:7fff:fe85:e611 dev wlp26s0 proto ra metric 600 pref medium
fe80::/64 dev wlp26s0 proto kernel metric 256 pref medium
fe80::/64 dev wlp26s0 proto kernel metric 600 pref medium
default via fe80::204e:7fff:fe85:e611 dev wlp26s0 proto ra metric 20600 pref medium

[tuttiface 0]

Hello again, my ISP is Verizon, My only AV is Windows defender, to reiterate I cannot access airvpn.org, ipleak.net, and I can confirm I also cannot connect to airvpn.info, the only way I'm currently able to post here is by using my cellphone carrier. Please bear with me as I have never posted logs here before, I hope I am doing this correctly.airvpntracert.txteddielogs.txt 

Regards

[Tex257 0]

Was in midst of long reply when I got bumped off airVPN. 

Short version: I have windows, MacOS and iOS devices. Could not logon on any (Eddie, OpenVPN) starting 15th or 16th, nor see the air sites. All are configured differently. Unlikely to be antivirus or firewall related.

Use Frontier FiOS as ISP. So does neighbor. I can see the air sites on his computer. Seems not to be ISP

[Tex257 0]

I also had turned off wifi and tried ATT cellular on iOS device. Could connect via OpenVPN but the VPN was not functional (could not access any website via browser).

Tonight, I can login on iOS using either Frontier or ATT, can only see sites when connected to VPN.
Hotspotted MacOS to ATT and can login using Eddie and see sites when logged in.

So iOS works regardless of ISP/data. Eddie only on ATT cellular data.

 

[Yet another user 0]

I played around with a virtual machine a bit. If the host is connected to the VPN, everything works as expected. If it's not, the VM can't reach airvpn.org or ipleak.net, even though the host can.

That seems to be an IPv4/6 thing. If I'm not connected, ipleak.net says "IPv4 test not reachable." If I'm connected, IPv4 and IPv6 both work. The VM doesn't seem to support IPv6 at all.

Non-authoritative answer:
Name:    ipleak.net
Address: 95.85.16.212
Name:    ipleak.net
Address: 2a03:b0c0:0:1010::509:d001

Disconnected, I can ping the IPv6 address, but not the IPv4 address. Connected, they both work.

[eliboy 0]

Still can't connect my airvpn. Did anyone resolve this issue?

[dzp8dq 0]

ISSUE:  People unable to use a browser to access any site unless VPN'd.

Sounds like a route / vpn issue. 

I've seen that happen before, when you use network lock and select remove default route.  You then had an issue and the settings were not reversed.  Therefore, you can only connect when VPN.... because your device still has the network config based on a VPN connection.

Either - 1 -- the DNS entry was not reversed by EDDIE, therefore it only works when VPN'd..... so, go into settings, set yourself to DHCP and reset your connection, or hard code GOOGLE public DNS (8.8.8.8, 8.8.4.4).
or       - 2 -- You may have selected remove default route in EDDIE, and it didn't get put back.  Resetting your device (OFF/ON) will reinsert a default route if DHCP is turned on.

This will solve the connectivity problem.  In the future don't select remove default route, just use the Net Block by itself - it works without you having to remove the default route.  Otherwise, write a script to insert the route into your routing table manually, and then run that when you disconnect.

 

[tuttiface 0]

1 hour ago, dzp8dq said:

ISSUE:  People unable to use a browser to access any site unless VPN'd.

Sounds like a route / vpn issue. 

I've seen that happen before, when you use network lock and select remove default route.  You then had an issue and the settings were not reversed.  Therefore, you can only connect when VPN.... because your device still has the network config based on a VPN connection.

Either - 1 -- the DNS entry was not reversed by EDDIE, therefore it only works when VPN'd..... so, go into settings, set yourself to DHCP and reset your connection, or hard code GOOGLE public DNS (8.8.8.8, 8.8.4.4).
or       - 2 -- You may have selected remove default route in EDDIE, and it didn't get put back.  Resetting your device (OFF/ON) will reinsert a default route if DHCP is turned on.

This will solve the connectivity problem.  In the future don't select remove default route, just use the Net Block by itself - it works without you having to remove the default route.  Otherwise, write a script to insert the route into your routing table manually, and then run that when you disconnect.

 

This is not the issue.

[vicktrosk 1]

I have had this issue for the last 3 days. unable to connect to airvpn or login through eddie on my pc (win 10), phone or tablet (both android). I could connect to every other website. when using mobile data on my phone I could connect to airvpn.

other win 10 users with the same isp as me could connect to airvpn. I have been dealing with my isp and there are no blocks on their end. they were at the point today of telling me they will send a technician out to resolve the problem. Now out of nowhere with no changes from me it is resolved and I can connect to airvpn and through eddie. I would like to know the cause or if this will happen again?

have others in this post regained access to airvpn? please post.

[Hyperlooney 0]

59 minutes ago, vicktrosk said:

I have had this issue for the last 3 days. unable to connect to airvpn or login through eddie on my pc (win 10), phone or tablet (both android). I could connect to every other website. when using mobile data on my phone I could connect to airvpn.

other win 10 users with the same isp as me could connect to airvpn. I have been dealing with my isp and there are no blocks on their end. they were at the point today of telling me they will send a technician out to resolve the problem. Now out of nowhere with no changes from me it is resolved and I can connect to airvpn and through eddie. I would like to know the cause or if this will happen again?

have others in this post regained access to airvpn? please post.

Hello, I know staff is working on issues so it may be that they fixed your particular issue. I’m personally still unable to log into Eddie (still getting timeout). Oddly, when first turning on my pc I just entered random username and pass and it did alert me that the username and pass was invalid, so it got through. Once I enter my real details it went back to timing out, and then I entered random username and it still timed out. 

If I was you, I’d not log off just in case  

[willee_wonkee 0]

Starting last Friday 16th until Monday AM (now), unable to login through Eddie, unable to ping IP address of airvpn.org, unable to browse to airvpn.org from multiple machine types (Win, Linux, Mac, Chromebook) and multiple browsers via Frontier from USA West coast. Everywhere else on the entire Internet [I checked them all :) ] was OK.
Frontier deny blocking. Error was consistently a connection time out.
Concurrently, cell service to airvpn.org was OK, access indirectly via a work VPN (not a Frontier client) was also OK.

[Staff 9972]

Hello!

Can you please try again and report back?

Kind regards
 

[Yet another user 0]

It's working perfectly for me today.