Sign-in Timeout after opening 2 chests

Issue Type (Required):

Error - SIGN-IN TIMEOUT

Issue Description (Required):

After an extended period of time spent standing around in lobby after a chaos wastes run, I decided to open a couple of random chests. The first one took a noticeable second longer to have the items pop up, the second one entirely failed to showed the items and booted me to main menu. After getting booted I was then prompted with sign-in timeout and the game closed. I now get timed out anytime I try launching the game and it is impossible for me to play.

[PC] Do You Use Mods? (Optional):

Yes, and I’ve tried disabling them

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

Steam (PC)

Player ID (Optional):

[PC] Upload Console Log & vermintide2_launcher.log (Optional):

console-2025-10-02-20.04.19-92271684-d859-495e-92d1-f5937376fe78.log (4.77 MB)

Sorry to hear this @maocimoxi

I’ve requested for one of our backend developers to check your account data and ensure everything is okay - I’ll let you know once I hear back from them.

In the meantime, there’s a possibility that the chest opening coincided with a network/ISP issue. If possible, are you able to temporarily switch to a mobile data connection and check to see if the error persists? This can help us in isolating the issue.

Thanks!

@maocimoxi from a backend perspective everything seems to be correct - so we suspect the issue here is connectivity-related.

I recommend running through our possible solutions here:

https://support.fatshark.se/hc/en-us/articles/24597329643933--PC-Experiencing-SSL-CONNECT-ERROR-and-SIGN-IN-TIMEOUT-Connectivity-Errors

and

https://support.fatshark.se/hc/en-us/articles/360034654113-How-to-Resolve-Connectivity-Errors-Latency-Issues-in-Vermintide-2

As of now the issue appears to have resolved itself? I’ve at least been able to get past sign-in and opened a box without things going kaput.

The problem had persisted through PC/router/modem restarts and my ISP has never had any issues with this game before so I’m left frustratingly curious as to what the root cause ended up being. I didn’t think to try connecting via mobile hotspot at the time, but considering what is previously mentioned I suppose an erroneous block on my ISP’s end is most likely. Still very odd to only have this sort of problem crop up once after ~800 hours of playtime.

Regardless, fixed is fixed I guess! Thank you for your help and thank you to backend for the check-in. I’ll keep the troubleshoot articles bookmarked for if any problems surface again (And don’t un-problem themselves after a day or so…)