Jump to content

Servers aren't showing up


Baked Potato18
  • Pending

When I enter Browse Games, it tells me that there are 0 out of 0 servers are showing up. The problem has been present since the new update came out, is there a fix?


Steps to Reproduce

As said before, the problem showed up abruptly when the update came out.




User Feedback


Can you post your client_log.txt file so we can see what errors are coming up when you trying to download the server listings? Thanks!

You can find this file at Documents\Klei\DoNotStarveTogether\client_log.txt

  • Like 1
  • Thanks 1

Share this comment


Link to comment
Share on other sites

On 4/8/2022 at 11:33 AM, PeterA said:

Can you post your client_log.txt file so we can see what errors are coming up when you trying to download the server listings? Thanks!

You can find this file at Documents\Klei\DoNotStarveTogether\client_log.txt

 

client_log.txt

Share this comment


Link to comment
Share on other sites

Can you try opening up a terminal window and grabbing the server listing manually by running these two commands.
 

curl -vvv https://lobby-cdn.klei.com/US-Steam-noevent.json.gz

 

curl -kvvv https://lobby-cdn.klei.com/US-Steam-noevent.json.gz

and send us the results of both.

  • Thanks 1

Share this comment


Link to comment
Share on other sites

22 hours ago, PeterA said:

Can you try opening up a terminal window and grabbing the server listing manually by running these two commands.
 


curl -vvv https://lobby-cdn.klei.com/US-Steam-noevent.json.gz

 


curl -kvvv https://lobby-cdn.klei.com/US-Steam-noevent.json.gz

and send us the results of both.

Last login: Wed Apr 13 14:40:44 on console

ramcels-iMac:~ ramcelcorpuz$ curl -vvv https://lobby-cdn.klei.com/US-Steam-noevent.json.gzcurl -kvvv https://lobby-cdn.klei.com/US-Steam-noevent.json.gz

*   Trying 13.224.2.125...

* TCP_NODELAY set

* Connected to lobby-cdn.klei.com (13.224.2.125) port 443 (#0)

* WARNING: disabling hostname validation also disables SNI.

* SSL peer handshake failed, the server most likely requires a client certificate to connect

* Closing connection 0

curl: (35) SSL peer handshake failed, the server most likely requires a client certificate to connect

* Hostname lobby-cdn.klei.com was found in DNS cache

*   Trying 13.224.2.125...

* TCP_NODELAY set

* Connected to lobby-cdn.klei.com (13.224.2.125) port 443 (#1)

* WARNING: disabling hostname validation also disables SNI.

* SSL re-using session ID

* SSL peer handshake failed, the server most likely requires a client certificate to connect

* Closing connection 1

curl: (35) SSL peer handshake failed, the server most likely requires a client certificate to connect

ramcels-iMac:~ ramcelcorpuz$

Share this comment


Link to comment
Share on other sites

Other users are experiencing the same issue with your specific OS version and this is what I have stated to them.

Quote

From these logs and reading over Apple's security policy revolving around SSL certificates, it would appear that your root certificates have been set to an expired state and can no longer properly initiate an SSL handshake somewhere in the start of the connection. I would expect more errors with websites and services in the future going forward with how strict Apple's security policy is with SSL certificates.

Let me be clear in that it is highly recommended for you to update your OS to a more recent version. OS X 10.12 stopped receiving critical security patches on December 31, 2019. This will not only keep your device more secure than it is but it will help fix some of these issues with other services in the coming future.

I know you may not be able to update your OS under certain situations. A workaround does exist for updating your root certificates. Let me be even more clear here that doing this is a bandage and your devices will still be out of date in terms of critical security updates. In no way can Klei assist or support doing this. If you have access to a more up to date version of OS X then you can use Keychain Access to export its System certificates. You would then be able to transfer and import these certificates on an out of date computer to use. This can be a higher technical requirement to do this and I can not assist with this process. I do not recommend installing root certificates you find somewhere online. These certificates are used in a connection to verify that a server is really who it says it is. Malicious actors would be able to falsify their credentials if you have their custom certificates installed.

 

  • Like 1
  • Thanks 1

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...