A WARDOGS access denied message calls for a service and access check before changing your PC. The September Beta became an open beta in the September 5 announcement, with a scheduled end of September 6 at 08:00 UTC. Use the current beta access page to check the window before retrying. [open-beta]

Error code 1147405308

Players have reported 1147405308 beside Access Denied and failed to authenticate with online services. This records the failed authentication stage; the number alone does not prove a version mismatch, an account ban, or damaged files. [steam-error-report] [error-message]

During the August 21 Beta opening, BULKHEAD confirmed a new problem under heavy login demand and said the team was working on the queue. Players reported this code during the same period. That timing is a reason to check for a shared incident first, not proof that every later occurrence has the same cause. [queue-update] [steam-error-report]

The code has also appeared in player reports after a match was already underway. In a second-Beta discussion, an OCE player reported that verifying files and restarting Steam did not resolve the failure. This community observation cannot establish the region's current status or the cause of another player's error. [oce-reports]

Work through the failure in order

  1. Check the announced window. A client you can download or launch does not by itself establish that the test is open. If the announced session has ended, look for a new official opening rather than reinstalling.
  2. Look for a shared login incident. Compare official updates with the time of your failure. Reports from other players are useful context, but do not establish that every region is down.
  3. Confirm your account and client. Use the Steam account with the relevant access and the client named for that test or release. Let its updates finish before retrying.
  4. Investigate locally if others can connect. Restart the client once. If you also have missing content or a client crash, use Steam's Properties → Installed Files → Verify integrity of game files check. Valve documents this for installation symptoms; it does not define or fix WARDOGS authentication code 1147405308. If other applications also have connection problems, investigate that broader issue separately. [valve-files]

These are diagnostic checks. Completing them does not grant access or repair a shared authentication service. A successful retry means you can authenticate and join an available session; if the same failure returns, retain the error details instead of stacking more changes.

If the server browser is empty

An empty list happens at a different stage from a login rejection. For the August Beta, BULKHEAD instructed players to select only one region in the Server Browser and described that limit as part of the test. Treat that as historical build guidance and check current notices before assuming the same restriction still applies. [queue-update]

What to include when asking for help

Record the complete code and message, time and time zone, client name, build if available, and whether the failure occurred before the queue, after it, or during a match. Include your region and the result of each check. Post through the official WARDOGS Steam discussions or the support route in the current developer announcement.

Keep passwords, account recovery codes and session information out of screenshots or logs. This error alone is no reason to disable antivirus or firewall protection, bypass anti-cheat, or buy a network booster. If the application closes instead of displaying an access error, use the crash report guide.