LZ1

You got it! https://www.youtube.com/watch?v=hEDV3UjhCLA(re-arranged) 1 year on its way... Kind regards Thank you :)You do know Air will be flooded with Otaku's now that we can connect to Japan, right?

It has to be https://en.wikipedia.org/wiki/Space_Battleship_Yamato_(2010_film) Air is the Yamato spaceship and Iskandar is the destination, just like Japan. It has to be Otherwise I give up haha.

Hello! Wow epic! Well done ! Could it be this? http://fategrandorder.wikia.com/wiki/Iskandar No it must be a spaceship! http://yamato.wikia.com/wiki/Iscandar_(2199)

Eddie 2.14.2 on Linux Mint 18 Cinnamon is still getting bootstrap error pop-ups for me. Steps: Run Eddie as normal, connected to a location. Put PC into hibernation/sleep, mid-session. Re-open computer and Eddie sometimes shows bootstrap errors.Network Lock On.Air DNS On.Check Air tunnel On.UDP protocol.

We had that before, but it should be fixed already. See if this still works.

Simply disconnect from the location/server you connected to, on the Overview tab, and a button will appear on the same Overview tab page saying "Activate Network Lock". You're thinking of "Lock Current" from the location/servers tab, but that's something else.

Hello! Welcome to AirVPN! Perhaps these threads will be of help: https://airvpn.org/topic/20632-confused-over-port-forwarding/ https://airvpn.org/topic/16596-port-forwarding-for-dummies/ https://airvpn.org/topic/14949-help-with-port-forwarding/ You don't need to touch your router in most cases and yes you need to be careful about forwarding ports on your router that you use elsewhere too.

Hello! You could try the Beta client, since if it's still a problem there, it would be worth reporting.

They do change network conditions as it suits them, yes. It's unfortunate for the end user .

Please try SSL/SSH .

Hello! I'm glad you had a good experience . If you run into any trouble, please feel free to ask for help.

The Beta isn't dangerous or risky don't worry . It's up to you of course. Are you using any anti-virus or 3rd party security software perhaps? If so, you could try momentarily disabling them. Maybe you could also try running it as administrator or using the TCP protocol for a try. If nothing works, you're also welcome to contact support and then paste in the logs from the Eddie logs section lifebelt icon.

Hello! You say you're using sweden but getting .nl. So are you using the Eddie client, with Network Lock on? You could check ipleak.net too to confirm. Otherwise, did you try switch between servers? Did you try browsing to google.se instead?

Hello! That's because it's not a speed guarantee, but a minimum allocated bandwidth. Which speaks to the quality of Air connections, that it's possible to make such a thing. If you think Air can guarantee the speed any user would get, when each users conditions are totally different in terms of ISP, hardware, software, location and so on, then I think you need to look again. Ergo there's nothing wrong with the claim, but rather more likely, something in your setup. Your setup of which, we know next to nothing about. As Air makes clear, speeds users can reach, are uncapped. There is no need to make any excuses and to my knowledge Air certainly hasn't made any in regards to seeds, when it's pretty straightforward that there's a multitude of possible reasons for a slowdown, that may be completely unrelated to Air and seeds altogether. As it turns out, most users can find the origin of slowdowns in their own set up. If you're experiencing problems, why not try to troubleshoot them calmly, instead of writing posts like that? Which only underscores the well known fact that network conditions change all the time. And if you're suggesting that Air is throttling you, despite this being the complete opposite of one of Airs central policies, then I'd ask you to put forth some proper evidence that amounts to more than an Eddie graph, as it's tantamount to defamation otherwise and that won't be allowed around here. And yet those getting more than 300Mbit / sec would tend to disagree. So no, there's nothing false about Airs commitments. You could for instance have told us: Whether you forwarded any ports or not.What settings you put in your torrent client.Which torrent client you're using and which version.Who you ISP is.What hardware your computer runs on.What router you're using.If you tried different Eddie locations.If you tried different Eddie protocols.Whether you tried any experimental clients or not.Whether it's a wired or wireless connection.And so on. Before making such unfounded claims.

On 2.14.1 Otherwise NL, Check Air DNS and Check Tunnel are on. Linux Mint 18 Cinnamon. I get this pop-up in two scenarios: After waking up my computer from hibernation, with an Eddie instance which wasn't shut down properly beforehand. When I get an assertion failure and it just pops up out of nowhere: ! 2018.02.18 22:03:52 - Connected. . 2018.02.18 22:03:52 - OpenVPN > Initialization Sequence Completed . 2018.02.18 22:12:04 - Updating systems & servers data ... . 2018.02.18 22:12:06 - Systems & servers data update completed . 2018.02.18 22:22:07 - Updating systems & servers data ... . 2018.02.18 22:22:09 - Systems & servers data update completed . 2018.02.18 22:32:10 - Updating systems & servers data ... . 2018.02.18 22:32:12 - Systems & servers data update completed . 2018.02.18 22:42:13 - Updating systems & servers data ... . 2018.02.18 22:42:15 - Systems & servers data update completed . 2018.02.18 22:52:16 - Updating systems & servers data ... . 2018.02.18 22:52:18 - Systems & servers data update completed . 2018.02.18 23:02:19 - Updating systems & servers data ... . 2018.02.18 23:02:22 - Systems & servers data update completed . 2018.02.18 23:03:39 - OpenVPN > TLS: soft reset sec=0 bytes=34565305/0 pkts=51766/0 . 2018.02.18 23:03:41 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org . 2018.02.18 23:03:41 - OpenVPN > Validating certificate key usage . 2018.02.18 23:03:41 - OpenVPN > ++ Certificate has key usage 00a0, expects 00a0 . 2018.02.18 23:03:41 - OpenVPN > VERIFY KU OK . 2018.02.18 23:03:41 - OpenVPN > Validating certificate extended key usage . 2018.02.18 23:03:41 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication . 2018.02.18 23:03:41 - OpenVPN > VERIFY EKU OK . 2018.02.18 23:03:41 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Columba, emailAddress=info@airvpn.org . 2018.02.18 23:03:42 - OpenVPN > Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key . 2018.02.18 23:03:42 - OpenVPN > Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication . 2018.02.18 23:03:42 - OpenVPN > Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key . 2018.02.18 23:03:42 - OpenVPN > Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication . 2018.02.18 23:03:42 - OpenVPN > Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA . 2018.02.18 23:12:22 - Updating systems & servers data ... . 2018.02.18 23:12:25 - Systems & servers data update completed . 2018.02.18 23:15:51 - OpenVPN > [Columba] Inactivity timeout (--ping-restart), restarting . 2018.02.18 23:15:51 - OpenVPN > SIGUSR1[soft,ping-restart] received, process restarting . 2018.02.18 23:15:51 - OpenVPN > Restart pause, 2 second(s) ! 2018.02.18 23:15:51 - Disconnecting . 2018.02.18 23:15:51 - Routes, removed a route previously added, 194.187.251.115 for gateway 10.4.0.1 . 2018.02.18 23:15:51 - Sending management termination signal . 2018.02.18 23:15:51 - Management - Send 'signal SIGTERM' . 2018.02.18 23:15:51 - OpenVPN > MANAGEMENT: CMD 'signal SIGTERM' . 2018.02.18 23:15:51 - OpenVPN > MANAGEMENT: Client disconnected . 2018.02.18 23:15:51 - OpenVPN > Assertion failed at misc.c:785 (es) . 2018.02.18 23:15:51 - OpenVPN > Exiting due to fatal error . 2018.02.18 23:15:51 - Connection terminated. . 2018.02.18 23:15:51 - DNS of the system restored to original settings (Rename method) I 2018.02.18 23:15:54 - Checking authorization ... I suspect I'll still get it in 2.14.2, so I just wanted to post anyway. Besides this, which I thought was odd, as it doesn't tend to be 0: . 2018.02.18 23:19:47 - Flushing DNS I 2018.02.18 23:19:48 - Checking route IPv4 . 2018.02.18 23:20:08 - curl: (28) Operation timed out after 0 milliseconds with 0 out of 0 bytes received . 2018.02.18 23:20:08 - Checking route (2° try) . 2018.02.18 23:20:29 - curl: (28) Operation timed out after 0 milliseconds with 0 out of 0 bytes received . 2018.02.18 23:20:29 - Checking route (3° try) . 2018.02.18 23:20:51 - curl: (28) Operation timed out after 0 milliseconds with 0 out of 0 bytes received E 2018.02.18 23:20:51 - Checking route IPv4 failed. . 2018.02.18 23:20:51 - OpenVPN > Initialization Sequence Completed ! 2018.02.18 23:20:51 - Disconnecting . 2018.02.18 23:20:51 - Routes, removed a route previously added, 178.238.229.54 for gateway 10.4.0.1 While by contrast it normally looks more like this: ! 2018.02.18 23:33:00 - Disconnecting . 2018.02.18 23:33:00 - Connection terminated. I 2018.02.18 23:33:03 - Checking authorization ... . 2018.02.18 23:33:12 - Updating systems & servers data ..., 2° try failed (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) . 2018.02.18 23:33:23 - Checking authorization ..., 1° try failed (curl: (28) Operation timed out after 20001 milliseconds with 0 bytes received) . 2018.02.18 23:33:32 - Updating systems & servers data ..., 3° try failed (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) . 2018.02.18 23:33:43 - Checking authorization ..., 2° try failed (curl: (28) Operation timed out after 20001 milliseconds with 0 bytes received) . 2018.02.18 23:33:52 - Updating systems & servers data ..., 4° try failed (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) . 2018.02.18 23:33:53 - Cannot retrieve systems & servers data. (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) . 2018.02.18 23:34:03 - Checking authorization ..., 3° try failed (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) Either way, the curl 28 error is quite debilitating, as it doesn't matter where you connect to and there's no apparent reason to me why it happens. After switching to TCP and unchecking "check if tunnel works" to no effect and still getting the same error mostly: . 2018.02.18 23:49:20 - Checking authorization ..., 1° try failed (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) . 2018.02.18 23:49:40 - Checking authorization ..., 2° try failed (curl: (28) Operation timed out after 20001 milliseconds with 0 bytes received) . 2018.02.18 23:50:00 - Checking authorization ..., 3° try failed (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) . 2018.02.18 23:50:20 - Checking authorization ..., 4° try failed (curl: (28) Operation timed out after 20001 milliseconds with 0 bytes received) W 2018.02.18 23:50:20 - Authorization check failed, continue anyway (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) I 2018.02.18 23:50:20 - Cancel requested. The client takes a long time to disconnect. At the first line, I had already clicked "cancel" and yet Eddie still tried completing all of the rest. So then I tried logging out and logging back in. But now the problem is worse. Especially as when you're not logged in, you can't connect to anywhere, nor cancel the login attempt and I got a new popup: W 2018.02.18 23:50:20 - Authorization check failed, continue anyway (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) I 2018.02.18 23:50:20 - Cancel requested. I 2018.02.18 23:50:20 - Session terminated. ! 2018.02.18 23:51:51 - Logged out. I 2018.02.18 23:52:01 - Checking login ... . 2018.02.18 23:52:21 - Checking login ..., 1° try failed (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) . 2018.02.18 23:52:41 - Checking login ..., 2° try failed (curl: (28) Operation timed out after 20001 milliseconds with 0 bytes received) . 2018.02.18 23:53:01 - Checking login ..., 3° try failed (curl: (28) Operation timed out after 20001 milliseconds with 0 bytes received) . 2018.02.18 23:53:15 - Updating systems & servers data ... . 2018.02.18 23:53:21 - Checking login ..., 4° try failed (curl: (28) Operation timed out after 20001 milliseconds with 0 bytes received) F 2018.02.18 23:53:21 - Cannot login. (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) . 2018.02.18 23:53:35 - Updating systems & servers data ..., 1° try failed (curl: (28) Operation timed out after 20001 milliseconds with 0 bytes received) . 2018.02.18 23:54:07 - Updating systems & servers data ..., 2° try failed (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) . 2018.02.18 23:54:28 - Updating systems & servers data ..., 3° try failed (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) . 2018.02.18 23:54:48 - Updating systems & servers data ..., 4° try failed (curl: (28) Operation timed out after 20000 milliseconds with 0 bytes received) . 2018.02.18 23:54:48 - Cannot retrieve systems & servers data. (curl: (28) Operation timed out after 20001 milliseconds with 0 bytes received) Finally, I turned off NL, tried SSH and then turned off "Check Air DNS" and I logged in instantly and connected moments later. I then disconnected, turned ON NL and switched to UDP. Left Air DNS unchecked. I still connected. Sorry if the formatting is off. The forum software did this.

Hello! If by downgraded you mean you were using the experimental, then please post here.

Hello! Please turn on Network Lock and then head to ipleak.net and see. It happens on occasion that the wrong IP is shown on websites, due for instance to issues with maxmind. In particular, there's also no DNS leaks on Linux .

Hello! You could try the experimental client.

Hello! I would urge you to try out the latest experimental client and then report back in the thread dedicated to it, as I'm sure Eddie coders would be interested in that .

Hello! Please turn off Network Lock and try again. Topics merged.

I would say it does answer your question, by pointing out to you that it's precisely not about how many people use it, but about if it follows Airs requirements or not. You asked: And the answer is that it lives up to Airs requirements: Would you prefer that Air sets up shop in locations that you happen to desire, while compromising on security and other important aspects, such as the quality of the datacenter, that make Air worthwhile to begin with? Then you would perhaps be here again, saying that your connection is slow or something doesn't work . By comparison, there's many people who also want Australia made possible and it's not that Air doesn't want to do it. But it has to make sense, both security-wise, economically and in terms of connectivity. I'm glad you have other options. I wish you luck in exploring them in 2018 and finding out what suits your needs best .

Hello! The most straightforward answer would be that it follows Airs requirements, while being beneficial in other aspects, such as cost. If location choices were to be solely based on what Airs customers wanted at any point in time, then Air would surely be amongst the first of companies in mankind to establish servers on Mars too .

Hello! What version of Eddie are you using? You can go to Eddies menu>About.

This thread should hopefully be a little enlightening

Because as I said, it's not just the color, but also the code in one of the columns, such as HTTP 403. These codes are defined as a shortcut for meaning. So HTTP 403 means blocked, for example. No problem .