WARDOGS error 1147405308 needs an access and service check before a reinstall. Players have reported it both at login and after being disconnected. Its appearance does not, by itself, identify an account ban or a damaged installation. The original August discussion was marked resolved after the author pointed to a shared login incident, rather than publishing a PC repair.

Checked 9 September 2026: the announced September beta window ended on 6 September at 08:00 UTC. Early Access is scheduled for 10 September. A downloaded Playtest client does not extend that window. If you are trying to enter that finished session, wait for the next announced access period and use the client specified for it. See the beta access guide and release schedule.

Separate the code from the cause

There are two documented reasons to check the service first:

  • A test has closed. An August support thread records authentication failures after that beta finished. The official recap confirms the test had ended. Owning the game or retaining Playtest access does not mean those test servers remain open.
  • The login system is under load. On 21 August, developer G_Medlin confirmed a queue problem caused by login volume beyond what the earlier alpha had encountered. That announcement explains the incident at that time; it is not a permanent definition of every later numeric error.

Neither source provides a universal code-to-cause lookup. Preserve the full message: an authentication rejection, an empty server list and an Elytra launcher failure stop at different points and need different checks.

Choose the action that matches your failure

SituationActionWhat counts as progress
You are launching a Playtest outside its announced windowStop retrying that session and check the next official opening.The relevant client and session become available at the announced time.
A current developer notice confirms login disruptionFollow that incident's updates; retry after recovery is announced.Login reaches the main menu or server browser. A queue position alone is not admission.
Steam still has an update pendingFinish the download for the client you intend to launch, then restart it.You are testing the updated client rather than the earlier build.
You can log in, but the server browser is emptyCheck the region filter. During the August test, the developer required exactly one selected region.Servers appear. Joining one is a separate check.
The application closes or Windows restartsRecord the crash stage and use the crash guide.You identify a client or system failure rather than treating it as a queue error.

The one-region instruction is documented beta guidance. If your current browser allows different behavior, follow its current instructions instead of treating an August limitation as permanent.

When local checks are useful

If an announced session is open and there is no matching incident notice, confirm that you are signed into the Steam account holding the relevant access. Check the Library entry and let its downloads finish. The official beta announcements used WARDOGS Playtest; follow the release instructions when moving from a test to the main game.

If the client also crashes or reports missing content, use Properties → Installed Files → Verify integrity of game files in Steam and let the scan finish. Valve documents this as an installation check. It does not grant Playtest entitlement or establish a fix for authentication code 1147405308.

Try the relevant connection once after each change and record its result. If it fails in the same place, stop repeating the same repair. Changing several unrelated settings at once makes it harder to tell whether an update, a local change or service recovery made the difference.

Send a report the support team can use

Use WARDOGS Steam Support or the official community route linked from our Discord guide. Include:

  • The complete message and number, plus the time and time zone.
  • Whether you were starting the client, leaving the queue, joining a server or already playing.
  • The client name, build if shown, region and current access window.
  • Any matching official incident notice, and what happened after each check.

A new report is especially useful when the announced session is open, the client is updated and the rejection continues after a reported recovery. Omit passwords, recovery codes and session tokens from screenshots. Do not treat the error as a reason to disable protection software, bypass the launcher or buy another copy of the game.