#Troubleshooting Dedicated Server crash to desktop issue

1 messages · Page 1 of 1 (latest)

tough ore
#

I am another person experiencing the "crash to desktop" issue when using a Dedicated server. This is (potentially) unrelated to ISP issues, as I'm running it via LAN in my house ("potentially" because there are still some external calls and the connection isn't purely p2p). I do understand that this issue becomes much more complicated when I'm running some unofficial WINE implementation of the server software, but I have hosted multiple game servers this way and this is the only one that fails like this.

I took the logs from both the server and client and ran them through Claude and discussed them -- while I am not a game developer, I do work professionally in the observability space and am well acquainted with logging and error tracking, so the output sounds plausible, but of course there is a massive black box of the game itself and related infrastructure where I cannot confirm these findings. My hope is that I give you enough context and IDs and data so you can confirm in Sentry and follow this issue end to end.

Server info

OS: Unraid
Dedicated Server repo: https://github.com/jcoker85/UnraidGameServers/tree/windrose (https://hub.docker.com/r/jcoker85/windrose/)
(though same issues occur on https://hub.docker.com/r/nodiaque/steamcmd/)

Major issue: When connecting to dedicated server, client crashes to desktop
Minor issue: ServerDescription.json is reset to defaults on start, could be unrelated

Attached files

Logs attached for client (R5.log, fresh from game start) and server (windrose-server.log, tail of last 700 lines up to crash) in windrose-logs.zip
Windrose bug report -- .md file with findings from logs, plenty of GUID and timestamps for this specific issue in windrose_bug_report.md

📎 windrose-logs.zip 📎 windrose_bug_report.md
wet drum
#

Seems like their windrose relay infrastructure is down, running into the same problem here. I was connected, I disconnected and then I get the crash into desktop after that. So from what I can tell from my log is that seems like a routing issue when it tries to route trough their servers to establish a connection. (might be wrong i am no wizard)

tough ore
#

That sounds about right. And it seems twofold, the client doesn't handle the connection loss gracefully and completely crashes.

topaz crescent
#

Good day sir, I am very sorry to hear that you are having issues, And thank you very much for providing amazing report.

We do have some issues of runing the game from within the same network, we are working on a fix, and will also be adding ability to connect directly by IP avoiding all handshakes and coturn services that we are doing right now.

Do you hink you can try to connect yo your diedicated server via wi fi?

tough ore
topaz crescent
#

Thank you very much sir!

One thing that could help as well - is if you are playing RIot's games - try dissabling Vanguard

tough ore
# topaz crescent Thank you very much sir! One thing that could help as well - is if you are play...

Interesting! Connecting on wifi still failed but the game didn't crash. Changing the docker container's networking to use a VPN container with no LAN access made it work -- so it's definitely isolated to LAN connections.

Of course my dedicated server is now technically hosted in Amsterdam instead of the other room and I have 300 ping, but I can change that 😂 Thanks for the information and if you need me to supply any more logs or do any additional legwork, let me know, happy to help