1147405309
WARDOGS error 1147405309: your account does not have permission to log in
This one is not your machine
The servers refused the login rather than failed it: you are outside a test window, or your invite wave has not landed yet. No local fix exists and verifying files will not help.
Check whether WARDOGS is down right now →What you see
Login is refused outright with "Your account doesn't have permission to log in at this time", or the same thing localised — "zugriff verweigert", access denied — usually seconds after the launcher reaches the sign-in step. It hits people who have already paid.
Also reported as: Your account doesn't have permission to log in at this time · zugriff verweigert · fehlercode 1147405309 · access denied 1147405309
This is a Closed Beta behaviour. It comes from how the closed-test builds are configured rather than from the game itself, so it may not apply once Early Access opens on 10 September. We will re-check this page that day.
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.
01 Check the clock against the window before anything else
ConfirmedClosed Beta 02 runs from 19:00 UTC on Thursday 3 September to 08:00 UTC on Sunday 6 September. Outside those hours the login is refused by design and every other step on this page is wasted effort. Early Access on 10 September ends the problem for good.
02 If you are inside the window, wait for your wave
ReportedBulkhead is releasing Beta 02 access in waves rather than to everyone at once, so a pre-order guarantees a place but not a place at 19:00. An invite showing on the Steam page is not the same as the entitlement having reached the login service.
03 Do not verify game files for this one
ReportedVerifying is the right move for 1147405308, which is a version mismatch, and it is the advice most search results give for the whole 1147405xxx family. It does nothing here: this code is a refusal from the server, not a broken install, and a full verify costs you twenty minutes of the window.
04 Check you are launching the Playtest entry, not the store page
ReportedThe closed tests ship as a separate "WARDOGS Playtest" item in your Steam library. Launching the main WARDOGS entry while only holding playtest access produces a refusal from the same family.
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.
This code is worth separating from the rest of the 1147405xxx family, because the usual advice for that family actively wastes your time here. 1147405308 is a version mismatch and verifying game files clears it. 1147405309 is the login service saying no — the client is fine, the install is fine, and there is nothing on your machine to repair.
The pattern in our own report feed is what makes the case. Every mention of this code so far has arrived outside a live test window: one before Closed Beta 01 opened on 21 August, and the rest across the morning of 3 September, from Germany, Austria, Australia, Russia and Türkiye, all of them in the hours before Closed Beta 02 was due to open at 19:00 UTC. Several came from players who had bought the game weeks earlier and reasonably assumed a purchase meant access now.
That is the confusion underneath it. Two things arrive at different times: the entitlement, which a pre-order gives you immediately, and the window, which opens when Bulkhead opens it. The Firing Range being reachable while matches are not has made this worse — people take it as proof the servers are up and read the refusal as a fault on their account.
Because this is a closed-test behaviour rather than a property of the game, it should stop existing on 10 September, when Early Access removes the gate that produces it.
If that did not do it
Every WARDOGS error, by symptom
Start from what you can see on screen rather than from the code.
Is WARDOGS down right now?
Live server state and player reports, updated continuously.
Can your PC run it?
Some crashes are a spec problem wearing an error code.
Server regions and browser
Which regions exist, and how to find a match in one.