Jump to content

DST LOGIN SERVER CONNECTION ISSUE (Ukraine)


Recommended Posts

We are aware of an ongoing problem with Don't Starve Together players in Ukraine not being able to connect to our servers. We are looking into this currently, however, we will need more information from users affected in order to be able to debug this issue.

If you have any information that you think may be able to help us investigate this issue, please respond to this thread and we will look into it. 

Link to comment
Share on other sites

I think all the problem with VPN, cause if I use new VPN it begins to work, but that is not solving my problem, cause VPN programs require money and sometimes fall down. Th broblem began at 00:00 in Ukraine. 

Link to comment
Share on other sites

Hi, I don't live in Ukraine, but my friend and I who both live in the US, are also having server problems.  When we connect to any server, it says "could not connect to klei servers.  This sort of thing is important in the Online Game business( more or less what it said) right.  Try again?"  We both live in different parts of the country, but neither of us can connect

Link to comment
Share on other sites

Hi there.
I live in Ukraine and have same issue.  If it could help - here is my tracert log

Tracing route to geologin.klei.ca [52.74.178.51]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2     2 ms     2 ms     2 ms  46-185-7-253-kie.broadband.kyivstar.net [46.185.7.253]
  3     *        *        *     Request timed out.
  4     6 ms     3 ms     3 ms  149.6.190.154
  5     4 ms    15 ms     4 ms  te0-6-0-2.rcr21.kbp01.atlas.cogentco.com [149.6.190.153]
  6    28 ms    21 ms    21 ms  be2679.ccr21.bts01.atlas.cogentco.com [130.117.48.93]
  7    22 ms    22 ms    22 ms  be2988.ccr21.vie01.atlas.cogentco.com [154.54.59.86]
  8    28 ms    27 ms    28 ms  be2974.ccr21.muc03.atlas.cogentco.com [154.54.58.5]
  9    36 ms    34 ms    33 ms  be2959.ccr41.fra03.atlas.cogentco.com [154.54.36.53]
 10    34 ms    33 ms    34 ms  be2184.agr21.fra03.atlas.cogentco.com [130.117.48.69]
 11    34 ms    34 ms    37 ms  pccw.fra03.atlas.cogentco.com [130.117.14.234]
 12   338 ms   338 ms   338 ms  TenGE0-1-0-19.br02.hkg12.pccwbtn.net [63.218.174.177]
 13   348 ms   343 ms   342 ms  amazon.buneth1.br02.hkg12.pccwbtn.net [63.217.254.74]
 14     *        *        *     Request timed out.
 15   307 ms   307 ms   307 ms  54.240.241.79
 16     *        *      302 ms  54.240.241.121
 17   312 ms   311 ms   313 ms  52.93.9.86
 18   306 ms   306 ms   307 ms  52.93.9.77
 19   312 ms   309 ms   311 ms  52.93.9.98
 20   326 ms   326 ms   325 ms  52.93.9.117
 21   330 ms   325 ms   324 ms  203.83.223.77
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *		  *     Request timed out.

 

Link to comment
Share on other sites

Well, as it has been written here - the some proxy servers help with this issue.

Seems it's kind of global routing issue because a few proxies show that tracert dies after specific IP range.

I used proxy and reached the login server -  I got the another IP for login server. So I just added it to my hosts in Windows and now I can login to game. This is also dirty temporary solution like proxy but it works.

If you're interested in solution which helped me (be aware it cannot help you and you do it on your own risk!):
 

104.154.85.165 login.kleientertainment.com

The IP range where tracert dies:
 

203.83.223.19 - 203.83.223.23

which are Amazon servers.

Link to comment
Share on other sites

13 hours ago, philin said:

If you're interested in solution which helped me (be aware it cannot help you and you do it on your own risk!):
 


104.154.85.165 login.kleientertainment.com

 

yes, this is quick solution, that works... you should pay attention :)

on windows 10 you should look for and modify "hosts" file, not "hosts.txt" (i'm not sure was it there by default, or from my previous tests with hosts). And run Notepad as Administrator.

at first i was trying to modify the hosts.txt (extensions was hidden, that's why the confusion) - it didn't help at all :) . Modifying the correct file works as it should. And https://login.kleientertainment.com/HealthCheck shows OK. And the game can see the servers.

I_VIEW32_2016-10-16_19-17-20.png

Link to comment
Share on other sites

55 minutes ago, nome said:

We have both Amazon and Google clusters - is there a clear consensus on which the Ukranian population would prefer to be pointed at by GeoDNS?

Hi nome.

I think it doesn't matter which cluster is used for Ukrainian segment and still it's unclear a bit why login server is unreacheable not only from UA. According to posts in Steam  community - some people can't reach login server from USA, South Korea etc.

Quote

Can't host a game in NYC either, same error message

Quote

same in Seoul Korea ! want to play 

 

Link to comment
Share on other sites

  • Developer
1 hour ago, philin said:

According to posts in Steam  community - some people can't reach login server from USA, South Korea etc.

That is the conflation of two independent issues sadly. The US cluster has been having stability issues due to a bug, there have been three short outages and all the reports from the US / etc correlate with these. We have not yet heard from anyone in the US who hasn't been able to connect for weeks. Independent to that, the Ukraine is having connectivity problems that're much longer lasting.

We are working on the stability problem in the US, but the Ukraine problem requires more information from people living in the Ukraine. If one cluster works and the other does not, that's an easy fix for us - we'll just point the Ukraine at that cluster and wait for DNS to update. If it's being blocked based on other criteria, we may need users to contact their ISPs and see what's going on.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Please be aware that the content of this thread may be outdated and no longer applicable.

×
  • Create New...