WARDOGS error code 1147405308: what it means, and the fix

The number is the diagnosis. If your screen reads "failed to authenticate with online services" and carries no number, that is the login service turning you away under load, it is not on your machine, and it has its own page. This page is for the code.

The 1147405xxx family is a version and entitlement mismatch rather than a permissions problem, which is why the wording varies so much between players. The last digits change with the specific mismatch, so a code ending in a different pair of digits is usually the same fault and takes the same fix.

One in the family is not, and it used to be listed on this page as though it were. 1147405316 is a full server rather than a wrong build: on 23 August it arrived with "Failed to join server. Server queue is full" printed under it, and players who restarted the game and the PC before verifying anything got nowhere. It has its own answer on the empty server browser page.

Launch night: the fix stopped working for the people who already had it

This code was expected to get more common on 10 September, on the reasoning that a launch-day patch would catch anyone who started the game before Steam had finished updating. That was half right. It was the commonest thing in the feed all evening — but the second wave of it, after 20:20 UTC, came from players who had already taken Launch Stability Hotfix #1. One posted the Build ID, 25238722, and the install time, 20:29 UTC; another wrote that Steam reported all 631 files validated and the code came back anyway; several verified, restarted Steam and verified again; and one said plainly that the verify step had not fixed it.

For them it had not. The hotfix put every player back into the login queue and Bulkhead said it would readmit them in controlled batches; a client on the current build, with files validated, refused at the front of that queue is the backend saying not yet, in a code that reads as a mismatch. Nothing on the machine answers that. The verify step stays on this page because the mismatch it fixes is real and was most of the August traffic — but if the Build ID already matches, it has done its job, and what is left is the wait that the queue page describes.

Since 11 September: kicked, then locked out at login

The newest version of this code arrives at the end of a different fault. Players are kicked partway through a match, land on the main menu, and the game hangs on "fetching data" or "Logging in" before timing out with "Failed to authenticate with online services" and 1147405308. The reports came from North America, Europe and Oceania through 11 and 12 September, several from players who had played for hours that morning without trouble, and at least one from a player who had never got past this screen at all.

None of the repairs work on it. Players rebooted the PC and the router, verified, reinstalled and restarted Steam, and got the same code. The thing that has worked is the least satisfying: relaunch the game, and keep relaunching, because one attempt in several lets you through. A handful of reports point at the network path instead — one player fixed it by resetting the Windows system proxy, another only gets in over a US VPN — but players in Russia with a VPN are still stuck, so that is not the general answer either.

Patch 0.11, scheduled for 08:00 UTC on 14 September, does not name this fault. Until a patch does, the kick is the thing to report, because the lockout follows it.

The third cause, and it was not a mismatch either

Late on launch night the same code started arriving with different words under it: Access denied - No license found, and for some players a flat statement that the account was permanently banned, printed the moment they picked a server. Those players were not banned. Bulkhead posted in the Steam thread that a small number of players, seemingly related to FirstLook linking, were being incorrectly banned when attempting to join a server, and that it was hitting people who took part in past internal tests — lingering permissions from those builds.

Nothing on the machine touches an account flag, which is why the usual advice failed so loudly here: players verified, reinstalled, cleared Steam and got the ban screen back every time. It was fixed on Bulkhead's side within the night. Players reported being unbanned without a ticket, an appeal or any other action, and a dev post on the pinned INCORRECT BANS thread said the team was still working through the rest.

So if this is your version of 1147405308: relaunch and see. If the ban notice is gone, it was this, and it is over. If it is still there after a day, that is when a support ticket is the right move — not before, because the queue of appeals is longer than the fix was.

A shorter tail, still open: 1147405290

Since 17 September a small number of players have hit 1147405290 instead, unable to log in to a match at all. It surfaced in the WARDOGS Discord developer forum, where community lead Lossy said the team had "flagged this one the other day" and was chasing an update — one early report points at wired connections, but that is one data point, not a pattern. No fix has come back yet, and nobody has posted a workaround that held. It reads as the same version-and-entitlement family as 1147405308, so the steps above are worth trying in order, but treat this one as open rather than solved until Bulkhead or a confirmed fix says otherwise.