macinmac

I think that AirVPN {UK routing} servers keep our privacy.. anyway?

Maybe someone could elaborate more about this situation, it's not very clear what is going on here, or at least is not clear for me.

" Please make Eddie save custom size of its Window and the width of its rows.'

Very good point +1.

Bringing this thread back on with a little question:

On desktops we have the Network Lock option to avoid network leak; now, is this possible to have it on iOS, since logging into Twitter for example, I see my original IP from time to time, even though I have the VPN Status Bar Icon on, 99% of the time, but, it seems that for a tiny moment till the iPhone wakes up, and it gets connected to AirVPN it leaks something there.

It's not something that bothers me, but I would like to have a fix to it, IF would be possible.

Thank You.

I've had the same issue with Tunnelblick, but somehow there was an error somewhere, because all I had connected to AirVPN was the desktop one..and Client Area reported that there were two devices connected.

Restarted the computer, and the problem was gone, everything reported fine into AirVPN Client Area.

Maybe it will work for you too.

For the first couple of weeks I used AirVPN and Eddie, it had no problem connecting after waking from sleep.  But now it hangs.  If I kill the process and relaunch, it goes into an infinite loop, saying something about "Checking routes".  The only way I can get it to work again is to restart the machine.

 

I could probably manually quit Eddie, then sleep the computer, then relaunch it when I wake the computer, and retype my password.  But that is a pain in the ass.  Did something change that would cause Eddie to stop working after wake from sleep?

 

Thanks

I always hit disconnect before leaving the machine going to sleep or something else.

The {Eddie} window always remains open, and when I wake the computer from sleep, all I have to do is hit connect and I get no errors or any kind of troubles, well, till now I didn't. And it's connecting back extremely fast.

And yes, I do have Network Lock always on.

I'm on the 2.12.4 beta with macosx 10.12.4 beta and I'm getting  curl: (28) Connection timed out after 10004 milliseconds

I solved this curl: (28) problem {on macOS Sierra 10.12.3 (stable)} by doing a simple restart.

Also, since I learned from what I've read around the forum, never quit the app without disconnecting, and log out.

I always do the steps properly, and since then, I've encountered zero problems after.