Skip to content
← All errors

Cannot join a server

WARDOGS: cannot join a server

Published Data as of Season 2 · 15 Oct 2026

This one is not your machine

Five faults answer to this sentence and they have five different answers. What separates them is how far you got: the browser, the click, the loading screen, or the match itself.

Check whether WARDOGS is down right now →

What you see

You cannot get into a game. The browser is empty, or every server refuses you, or the loading screen hands you back to the main menu, or you get in and get dropped again — all of it described the same way, and none of it the same fault.

Also reported as: cant join server · can not join a server · unable to join a server · cannot join any server · cant join any games · unable to join match

What to do instead

The cause is not on your machine, so reinstalling and verifying will not reach it. These are the things that actually help while it lasts.

  1. 01 The server browser is empty, or nothing is listed for your region

    Confirmed

    You never get as far as clicking. During the betas this was the region filter and the fix was to select exactly one region; on launch night it was the servers coming back in batches after the hotfix, with nothing to select. Either way the answer is on the empty server browser page.

  2. 02 You click a server and it refuses you, with or without a code

    Confirmed

    Servers are listed, the join fails. If the message reads "Join Timed Out" or "Failed to connect to the server in a reasonable time", that is error 1628505091 and the launch hotfix names it. If it is 1147405316 or a server-full wording, every server was genuinely full at that moment.

  3. 03 The loading screen starts and hands you back to the main menu

    Confirmed

    Further than the click: the map begins to load and the game returns you to the main screen, sometimes after a few seconds in the world with "Server got closed" underneath. That is its own fault and its own page.

  4. 04 You are in a match and get dropped partway through

    Reported

    You joined successfully and played, and the game removed you before the match ended — often with whatever that run had earned. Bulkhead named this symptom in the launch hotfix and the reports carried on afterwards.

  5. 05 You never reach a server list at all

    Confirmed

    If the game stops before the browser — a queue that will not move, "failed to initialize player session", or a failure to authenticate at the front of the queue — this is the login step rather than the join step, and none of the four above apply.

Did this fix it for you?

Notes from other players who hit this code. Say what worked, what did not, and which region you are in — a fix that only works in one place is worth knowing about. Best-rated first, and there is no time limit: an answer from the first beta is still an answer.

No comments yet. Be the first to say whether this worked.

"I can't join a server" is the commonest sentence written about WARDOGS and the least useful one, because five separate faults produce it and the fixes have nothing in common. One of them is a setting, two are server-side and finished, one is server-side and unfinished, and one is not about servers at all. Telling them apart takes a single question: how far did you get?

The browser is empty

Nothing to click. In both closed betas this was the region filter — the browser needed exactly one region selected and showed nothing until it had one. After the launch hotfix it was the servers themselves being brought back in batches, which looks identical and has no setting to change. The empty server browser covers both, and which one you are looking at.

The click fails

Servers are listed and the join is refused. The wording decides which fault it is. Error 1628505091 reads "Join Timed Out" or "Failed to connect to the server in a reasonable time", arrives after you have cleared the queue, and was named in Launch Stability Hotfix #1 — restart to collect it. A code ending 1147405316, or anything about the server queue being full, is error 1147405300, capacity at join time instead: the server was genuinely full at that second.

The loading screen gives up

The map starts loading and you end up back on the main menu, sometimes after a few seconds in the world with "Server got closed" printed under it. That one is being dropped back to the main screen, and it is Bulkhead's end rather than yours.

You get in, and then you do not stay in

A match you were playing ends early for you alone. That is being kicked from a match: named in the launch hotfix, still reported after it, and the one fault in this list with no fix to offer yet.

You never reach a server list

Then this is not a join problem at all — it is the login step, and the question is which part of it. A position that stops moving is the queue; "failed to initialize player session" is the online services not answering; the panel with no code is failed to authenticate; and a long number on the screen is 1147405308, which has three causes of its own.

Every one of these is also visible from the other direction. If reports are spiking on the live tracker while you work through this, the fault is not yours and the page you land on will say so.

If that did not do it