Darktide error 5002 stops you joining a mission, usually right after character select, with a failed to join server message. In roughly nine cases out of ten it is a backend problem on Fatshark side, most often server maintenance, not a fault on your PC.
Quick answer
Check the Darktide server status first, since 5002 is almost always server maintenance or downtime. If servers are up, restart the game, verify you are on the latest version, restart your router, and check your firewall is not blocking the game. When maintenance ends, the error clears on its own.
| Error snapshot | |
|---|---|
| Exact error code | 5002 |
| Error message | Failed joining server (Error Code: 5002) |
| Applies to | Warhammer 40,000: Darktide on PC and Xbox |
| Environment | Online play, after character selection |
| Severity level | High blocks all online missions, saves are safe |
| Quickest fix | Check official server status, since 5002 is usually maintenance, then wait or restart. |
What the error actually means
In plain English
Your game tried to shake hands with Fatshark servers and the connection did not complete. Most of the time the servers are down for maintenance, so the message is the game telling you the door is temporarily locked, not that your install is broken.
Error 5002 is a backend connectivity error. It appears when the client cannot complete the handshake with the Darktide servers, typically just as you try to load into a mission. Fatshark has confirmed that the main cause is server maintenance or temporary outages, which is why it spikes after big updates when servers are under load or still syncing.
In the smaller share of cases where the servers are clearly up, the cause shifts to your side, a version mismatch where the client did not auto update, outdated drivers, security software blocking the connection, corrupted files, or local network instability.
Before you start
Prerequisites and warnings
- Error 5002 does not crash your game or corrupt your saves, it only blocks online joining.
- Always confirm server status before troubleshooting your PC, to avoid chasing a problem you cannot fix.
- After a major patch, expect heavier load and occasional 5002 spikes for a while.
Step by step fixes
Confirm the servers first. Only move to local fixes if status is healthy.
| # | Step |
|---|---|
| 1 | Check the official server status. Look at the Darktide community channel on X and the Steam news for Darktide. If maintenance is announced, the only real fix is to wait for it to finish. |
| 2 | Restart the game. Fully close Darktide and reopen it. A fresh launch re attempts the handshake and clears a stuck connection state. |
| 3 | Verify the game is updated. Steam sometimes skips an auto update, leaving a version mismatch. Check for and install any pending Darktide update. |
| 4 | Restart your router. Power cycle your modem and router for a couple of minutes to clear local network issues that can block the connection. |
| 5 | Check firewall and antivirus. Confirm your security software is not blocking Darktide, and add an exception for the game and its launcher if needed. |
| 6 | Update graphics and network drivers. Outdated drivers can interfere after a new patch, so update your GPU and network adapter drivers. |
| 7 | Verify or reinstall files. Verify the integrity of the game files through your launcher, and reinstall as a last resort to replace anything corrupted. |
The technical context (the why)
Darktide is an always online cooperative game, so joining a mission means connecting to Fatshark backend services that place you with your squad and host the session. When those services are offline for maintenance or overloaded after a patch, the handshake cannot complete and the client returns 5002. There is no client side fix for that, only patience.
When the backend is healthy, the same error can still appear if your client cannot reach it cleanly. A version mismatch, a firewall rule, or an unstable connection all break the handshake locally. This is the same family of anti cheat and backend issues that also surface as Easy Anti-Cheat errors in Fatshark titles, which is why verifying files and exceptions matters.
Key points to remember
- About 90 percent of 5002 cases are server maintenance or downtime.
- Check official status before touching your PC settings.
- A skipped auto update can cause a version mismatch on your side.
- Saves are never affected, only online joining is blocked.
Still broken? Your safety net
If servers are confirmed up, your game is current, and your network and firewall are clean, but 5002 keeps blocking you, verify the game files and reinstall if needed. If your anti cheat layer is the deeper issue, see our guide on the Easy Anti-Cheat error 30005 fix. When all of that is ruled out, contact Fatshark support with your error logs.
Fatshark supportMore Error Fix guides
Was this fix helpful?
Yes, it workedNot yet
Your feedback helps us keep these guides accurate and updated.
Related error fixes
- Dokkan Battle “Unauthorized” error
- “Operation could not be completed (0x00000709)” printer error
- ChatGPT “Error 429: Too Many Requests”
- Peacock “Playback Error”
- PS4 “CE-32895-7” connection error
- DoorDash “Error validating basket”
- Google Gemini “Something went wrong (1101)”
- Easy Anti-Cheat “Error 30005 (CreateFile failed with 32)”
- Steam “Error Code 50”
- Xbox “Error code 0x87e5002c”
- FreeStyle Libre 3 “Sensor Error”
TLDR
- Check official server status first, 5002 is usually maintenance.
- Restart the game and confirm it is fully updated.
- Power cycle the router and check firewall and antivirus.
- Update drivers and verify the game files.
- Saves are safe, and when maintenance ends the error clears itself.
Written and maintained by: Freddy John, founder of Wings Infotech and editor at Seminarsonly. This guide is reviewed and updated as vendors ship new patches. Last reviewed: 26 June 2026.