Eddie repeatedly fails on "Checking DNS"

[snoodlehouse 1]

This problem started a few days ago. I'm using Eddie on Linux Mint 18.2. I'm in the US but Eddie usually chooses a Canadian server. I'm closer to Vancouver BC than the other sites.

 

I click "Connect to recommended server" and chooses one for me in Canada like usual, but it will hang on "Checking DNS." Eventually it times out, disconnects and tries a different server. I tries about 3-5 times before it finally find a server it can connect to. Obviously that's annoying. Also, the server I can use usually has a load in the 40%-60% range. That makes me think that a lot of people are having the same problem and can only connect to certain servers. 

 

I have attached the log.

Eddie_20171020_103031.txt

[Konsog 0]

I'm on OSX 10.11.6 and usually connect to UK servers, but I seem to be having a similar problem. Turning Network Lock off sometimes seems to help. But with it on I seem to be unable to connect to UK servers.

 

This is also a recent problem. I haven't encountered it before today.

 

 

Eddie_20171020_201428.txt

[Staff 10024]

I'm on OSX 10.11.6 and usually connect to UK servers, but I seem to be having a similar problem. Turning Network Lock off sometimes seems to help. But with it on I seem to be unable to connect to UK servers.

 

This is also a recent problem. I haven't encountered it before today.

 

 

Eddie_20171020_201428.txt

 

Please upgrade to Eddie 2.13.6 (latest stable release), reboot both the router and the system and test again.

 

Kind regards

[madrat 19]

This problem started a few days ago. I'm using Eddie on Linux Mint 18.2. I'm in the US but Eddie usually chooses a Canadian server. I'm closer to Vancouver BC than the other sites.

 

I click "Connect to recommended server" and chooses one for me in Canada like usual, but it will hang on "Checking DNS." Eventually it times out, disconnects and tries a different server. I tries about 3-5 times before it finally find a server it can connect to. Obviously that's annoying. Also, the server I can use usually has a load in the 40%-60% range. That makes me think that a lot of people are having the same problem and can only connect to certain servers. 

 

I have attached the log.

Same problem here. Takes 2 or 3 times to connect to Vancouver server. Connecting to US server no problem.

[lifeoftheBonsai 0]

Same here ..

[lifeoftheBonsai 0]

I have the same problem and tried both :

1)Preferences > Advanced > unmark "Checking if the tunnel effectively works"
 and 2) disabling DNS check
, no change ..

It is also odd that i can successfully connect to all german servers but close to no dutch servers, dont know if that indicates anything though as i am not tech-savvy. 

But i think its important to note that the problem persists ( in my case) since a few days, and it`s usually always the same servers since then that i cant connect to . (time out at "checking dns" or "checking route")
by the way i also got the newest version of eddie installed & also tried reinstalling eddie.

[RaineyPass 12]

Same general issue here, I'm in US.   If I use speed as my priority, US servers have no stars (all white) and I'm always connected to a canadian server if I use "connect to recommended server."  I can manually, sometimes connect to a US server if pick one myself.  Either method takes a long time to connect, minutes at times and my connection isn't very stable, sometimes I can't connect at all and Eddie takes forever to close down.  I get the same error messages as described plus some others.     

 

Using latency as my priority, "connect to recommended server" gives me a US server, unless they're heavily loaded.  They typically have five gold stars. I can connect manually to servers most anywhere and connections are much faster, less than a minute and my connection is very stable.

 

The white stars for all US servers using speed has been going on for a month or so with me and happened periodically before that, back to April or thereabouts.  Latency as my scoring rule has always performed much better, speed as the scoring rule has always been hit or miss.

 

I'm on Win10 64 bit, Eddie 2.13.6, the version before did the same, tap driver version doesn't matter; I've tried different TAP's, using 9.21 now, 9.9.2 didn't affect things. 

 

The only suggestion I have is use latency as the scoring rule.