OS: macOS Catalina 10.15.6.
I have a dedicated server which is able to start without issues, but when I try to join it I get this crash: https://pastebin.com/jxADQ6UG.
This is what the terminal records:
Master: [00:09:01]: [P2P] Received from 148.235.9.47|1 '76561198870384878'
Master: [00:09:01]: [P2P] Sent to 148.235.9.47|1 '76561198870384878'
Master: [00:09:01]: New incoming connection 148.235.9.47|1 <1930935359921702111>
Master: [00:09:01]: Client connected from 148.235.9.47|1 <1930935359921702111>
Master: [00:09:01]: ValidateGameSessionToken pgs-usc^KU_or9kA0Ka^DontStarveTogether^2T1tNHXBSHJs9zdkVQlhOeonO/ACzBhWLmc0PC0HC4c= for <1930935359921702111>
Master: [00:09:01]: Client authenticated: (KU_or9kA0Ka) licet_insanire
Master: [00:09:02]: [Steam] Authenticated host '76561198870384878'
Master: [00:09:04]: There is no active event to validate against.
Master: [00:09:04]: [Shard] Read save location file for (KU_or9kA0Ka)
Master: [00:09:04]: Registering master server in EU lobby
Master: [00:10:49]: [Join Announcement] licet_insanire
Caves: [00:10:49]: [Join Announcement] licet_insanire
Master: [00:10:59]: [Steam] SendUserDisconnect for '76561198870384878'
Master: [00:10:59]: [Leave Announcement] licet_insanire
Master: [00:10:59]: Connection lost to 148.235.9.47|1 <1930935359921702111>
Master: [00:10:59]: [Shard] (KU_or9kA0Ka) disconnected from [SHDMASTER](1)
Master: [00:10:59]: Registering master server in EU lobby
Caves: [00:10:59]: [Leave Announcement] licet_insanire
Caves: [00:11:06]: Registering secondary shard in EU lobby
Master: [00:11:08]: [P2P] Connection failed for '76561198870384878'
Caves: [00:16:06]: Registering secondary shard in EU lobby
Master: [00:20:59]: [P2P] Session timed out for '76561198870384878'
Master: [00:20:59]: [P2P] Remove session: 148.235.9.47|1 '76561198870384878'
Caves: [00:21:06]: Registering secondary shard in EU lobby
Unlike other people, I can open the DST application without issues.
open the game and try joining a dedicated server.
A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
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 accountSign in
Already have an account? Sign in here.
Sign In Now