Server error and Sign-in timeout

Issue Type (Required):

Error - SERVER ERROR

Issue Description (Required):

I keep running into server errors and crashes in Warhammer: Vermintide 2.

This issue mostly happens when I play Markus’ Mercenary and Huntsman careers. Most of the time, right after the party enters the portal and before the end-of-mission score screen loads, a server error pops up immediately followed by a silent game crash with no crash reporter window. The error message reads: Could not connect to game server, please try again later.
In fewer cases I can keep playing for a while, but the same server error will still appear eventually and crash the game. This identical error can also pop up while I am editing items or refreshing item properties.

After crashing, restarting the game leaves me stuck on the login screen with sign-in Timeout -1.

I have completed all of the troubleshooting steps below with no improvement:

  • Cleared game cache
  • Checked my hosts file (clean, no custom entries)
  • Flushed DNS
  • No VPN running
  • Repaired EAC
  • My network works fine for other online games such as Overwatch 2

Further details about the server error:
Log analysis shows corrupted inventory data for these careers:
Mercenary, Huntsman, Foot Knight, Ranger, Ironbreaker, Slayer, Engineer, Thornsister, Unchained, Bounty Hunter, Zealot.

I disabled Steam Cloud Save, launched the game, deleted all loadouts for these careers, remade them, and set emotes for each.
Even so, switching to Slayer in the Keep still triggers the server error and crashes the game. I also found that there is no emote slot available for Slayer at all; I cannot edit or assign an emote for this career.

I found a forum thread with nearly identical symptoms:

For the Login Timeout -1 error:
Logs indicate a failure to connect to the PlayFab backend. These two errors occur one after another, so I suspect they are linked.

Please help me fix these errors
Thank you very much.

[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] Crash Report (Optional):

The game closes directly without any crash popup

console-2026-10-26-09.18.25-0f00babc-9b07-4841-84c6-40ab1420c5f1.log (794.8 KB)

console-2026-10-26-10.24.07-623c7232-16d1-48e7-b70c-e97d37a1ebd4.log (126.0 KB)

Sorry to hear this @DearH1

I’ve shared your report with our backend developers, and I’ll update you once I’ve heard back from them!

Thank you for your patience in the meantime.

Thank you for your prompt reply. I will be eagerly waiting for your update. And about the “log analysis shows” I send my crash logs to an AI for analysis, and its conclusions are for reference only. I hope this will not mislead your team.:face_holding_back_tears: (I did follow the AI’s suggestions to troubleshoot.)

@DearH1 our backend developer has now repaired your account data for Slayer Bardin, so the weapon pose cosmetics should be accessible again.

It’s possible that the server error/sign-in timeout is an independent connectivity issue, so please let us know if there’s any issue still.

Unfortunately, both errors still persist: the top one is Sign-in Timeout -1, and the bottom one is Server Error -1. I just ran a mission on The Wastes and crashed again before the mission results screen. I’ve attached the log. Please let me know if there is any additional information I can supply.:face_holding_back_tears:

console-2026-10-28-00.13.46-39dc9311-1868-47ae-a223-27daa6977b41.log (117.5 KB)

console-2026-10-27-23.23.53-ed2c73c5-2acd-4d6b-a58d-5d39e6735b37.log (3.3 MB)

I apologise for any confusion caused by my previous description.
What I mean is: I cannot repair this error by modifying Slayer’s emote slot. It is normal that weapon‑specific emotes show as unavailable for axe with shield and hammer with shield loadouts, this is expected game behaviour.
However, the log still reports Broken item slots for career: "dr_slayer".
I am reaching out for support because even after your backend engineers performed repairs on my account, this error message still appears. I would like to clarify: Could corrupted local game data on my PC re‑pollute the backend save after a backend‑side fix? Also, please guide me what exact steps I should perform locally after your backend repair, to prevent this broken‑slot error from recurring.:sob:

@DearH1 I believe these are two separate issues, one being the broken weapon pose for Slayer Bardin - which is still repaired in the backend now.

Other broken item slots I’m admittedly not sure about, but local data could be the culprit. Could you please try a clean reinstallation of Vermintide 2 which involves deleting your AppData (this will reset custom settings e.g. graphics, keybinds etc.):

The connectivity errors ‘Sign-in Timeout’ I suspect are unrelated to the above. You previously tried some of our usual suggestions, but I also recommend trying:

  • Changing your DNS to 1.1.1.1 or 8.8.8.8. For how to change to 1.1.1.1, please see: Set up 1.1.1.1 on Windows · Cloudflare 1.1.1.1 docs
  • Checking Anti-Virus and Firewall and ensure connection for Vermintide 2 is not being blocked, and no files quarantined. It may also help to add appropriate Anti-Virus and Firewall exceptions for both Vermintide 2 and Easy Anti-Cheat. You’ll need to add the following exceptions:
  • vermintide2.exe in \Program Files (x86)\Steam\steamapps\common\Warhammer Vermintide 2\binaries
  • vermintide2_dx12.exe in \Program Files (x86)\Steam\steamapps\common\Warhammer Vermintide 2\binaries_dx12
  • EasyAntiCheat_EOS.exe in C:\Program Files (x86)\EasyAntiCheat_EOS
  • Perform a ‘Selective Startup’ to disable background applications that may be conflicting:
  1. Press the Windows key
  2. Type ‘msconfig’ and select ‘System Configuration’
  3. On the ‘General’ tab, select ‘Selective Startup’
  4. Deselect ‘Load startup Items’
  5. Reboot your PC

If the above is unsuccessful, could you please try temporarily switching to a mobile data hotspot connection and check to see if the Sign-in Timeout error occurs? This can help to determine if the issue is network/ISP-related. If the error does still occur, please could you provide the console log from this session so we can check this for comparison?

Please let me know how things go!

Thank you for your reply.

I have followed all the troubleshooting steps you suggested. I used 8.8.8.8 because 1.1.1.1 kept timing out on requests.

However, I still crashed right before receiving mission rewards after entering the exit portal in a Chaos Wastes run, with the server error: Could not connect to game server, please try again later. -1. This time I was playing Zealot. Fortunately, there was no sign-in Timeout -1 when I relaunched the game. I managed to log back in and finish that Chaos Wastes run, which was a pleasant surprise.:face_holding_back_tears:

The first log is from after the crash with the error. The second log was captured after I rejoined and finished the game.

console-2026-10-29-02.51.27-14d0369d-e3e7-4e22-86ca-62686192413d.log (3.8 MB)

console-2026-10-29-03.56.56-75eda8b5-c054-4617-b6a3-57cbf22d7944.log (922.9 KB)

@DearH1 thanks for the update! I’m glad to hear that the sign-in time out error has resolved after changing DNS.

Looking at your initial log, it appears connection to our backend was disrupted and resulted in an error:

Error Code: 1123 | Error Override: COULDNT_CONNECT

Unfortunately, we can’t determine specifically what triggered this error from the log data alone. Backend Error 1123 typically indicates a network issue that occurs when the game client can’t communicate correctly with the backend. This can sometimes be a symptom of iPv6/iPv4 routing issues or a temporary connectivity/ISP issue.

It may be helpful to try disabling iPv6 on the adapter you’re using (for this, I recommend searching online for specific steps for your setup)

Also, were you able to test a mobile data hotspot connection, and if so, did you experience any connectivity issues?

I disabled IPv6 (though I re-enabled it shortly after the error occurred). I’m using a mobile hotspot, but the error still persists.
Also, after switching my DNS to 8.8.8.8, I noticed higher latency while playing Overwatch 2.
logs are attached below.
Let me know if more information is needed.:face_holding_back_tears:

console-2026-10-30-04.02.23-c7ce7ea9-3ec9-4aef-aa0f-c269b128b267.log (2.2 MB)

Thanks for the update @DearH1, I’ve shared this information and your console log with our backend developers and have asked if they have any further insight or suggestions.

I’ll let you know as soon as I’ve received a response! Thank you for your continued patience.

Please let me know immediately if there is any solution! I simply cannot bring myself to abandon this game that has been with me for so long!:face_holding_back_tears:

By the way, I’d like to know whether this issue is on my local end or the server side. If it’s a local problem, will restoring my PC to factory settings help?

@DearH1 I’ve just nudged our backend developer, and I’ll let you know what they say.

As we haven’t observed widespread reports, and our backend service provider has reported no outages, this likely indicates the issue to be a local network/ISP-related problem.

I can’t guarantee that restoring your system will help, but it would at least provide a clean baseline to work from, and could be worth trying! If you’re happy to do so.

@DearH1 our backend developer has reviewed your log, and can confirm that there appears to be a local network or ISP issue at play:

https://5107.playfabapi.com/Client/ExecuteCloudScript, Name: COULDNT_CONNECT
EAC Challenge Request Timed Out - Resending

Unfortunately, they advised there isn’t anything specific that we can do on our end. Though hopefully we can troubleshoot and still get to the bottom of it! Please let me know how things are after trying the factory reset mentioned above.

Thanks for all your help. I’ve been using a VPN/network accelerator, and after testing over the past few days, the error occurrences have dropped significantly. It’s not completely fixed, but it’s now within an acceptable range. As for resetting my PC to factory defaults, I have too much important data on this computer, so that’s unnecessary.
Anyway, thank you for your assistance. Have a nice day. :):grin: