Read the full message, not only 1147405308
Error 1147405308 has appeared with failed-authentication or access-denied messages in WARDOGS support threads. It does not identify one universal cause. Start by recording the exact wording and the last screen you could reach.
If the server browser opens and only joining a server fails, use the join branch instead. If the text explicitly says banned or restricted, go to the restriction branch; a normal file or network check does not appeal a ban.
| What you can reach | Use this branch |
|---|---|
| Cannot reach the menu or server browser; authentication fails | Update and verify once, then check the connection and session result. |
| Browser opens, but joining returns an error | Connection guide: server population, region, ping limit and timeout. |
| Message explicitly says banned/restricted | Record the message and contact the appropriate support channel. |
| Game closes to desktop or shows a crash dialog | Startup/crash checks and a private diagnostic report. |
Update the client and verify the installation once
Read the words beside the code. An explicit ban needs support; an authentication failure alone does not identify a ban. For a non-ban authentication error, work through these checks in order.
- Finish any pending WARDOGS download in Steam. Exit the game completely, then launch once and check whether you reach the server browser.
- Verify the installation: Steam → Library → right-click WARDOGS → Properties → Installed Files → Verify integrity of game files. Wait for completion, let Steam replace any files, then try again. Team17 prescribed this for a player kicked from a match who then received 1147405308.
- If verification changes nothing, optionally try the same PC and account briefly on a trusted mobile hotspot. Limit the test to login if mobile data is expensive. If it works there but fails on home internet, the home connection or route deserves investigation; it is not proof that changing game files will help.
- If both connections fail, stop cycling through reinstalls. Record both results and send the support details below. Success for this branch means reaching the server browser; a later Join error belongs to the next branch.
Please note: One September player regained access after their home public IP changed. That is a case result, not a guaranteed repair or a recommendation to bypass a restriction.
Check the session and clock before changing more settings
After the update and file check finish, close WARDOGS completely and make one fresh launch. Record whether you get past the point that failed. Repeating the same reinstall without a different result does not narrow the cause.
In a September 25 support case, Team17 also asked the player to check the correct time zone. Check Windows Settings → Time & language → Date & time and compare the displayed time and zone with your location. Correct an actual mismatch, then retry once. The thread also records that this did not resolve that player’s case, so it is a check rather than a guaranteed fix.
Team17 authentication and clock-check threadCompare connections only when it helps narrow the cause
If you can test safely, try the same PC and account briefly on a trusted mobile hotspot. Restrict the test to login if mobile data is costly. Keep the game version and account the same so you are comparing the connection rather than several variables at once.
Success on one connection and failure on another points to a route or home-network difference worth reporting. It does not prove an account ban, identify a specific router setting or justify bypassing an access restriction. Failure on both connections is useful information too.
| Observed result | What to do next |
|---|---|
| Home fails; trusted second connection reaches browser | Report both results and the times to support; investigate the original connection with that evidence. |
| Both fail at the same screen | Send the exact message plus update, file-check and connection results. |
| A fresh login succeeds, but one server fails | Stop authentication troubleshooting and use the server-join branch. |
| Several players fail at the same time | Check an official notice for that time; a shared symptom alone is not proof of global downtime. |
What if the message explicitly says banned?
Team17 acknowledged incorrect bans on September 10–11 and applied backend changes. Its instruction was to launch and log in again, then contact support with a Steam ID if access was still blocked. That historical incident does not establish that every later ban is incorrect.
- Try one fresh login after any stated fix. If access returns, no further action is needed.
- If the restriction remains, send the full message and Steam ID privately to Team17. For a ban limited to a community server, contact that server’s administrators. Changing networks or verifying files does not appeal a ban.
Send a useful private support report
After the bounded checks, send the observed results rather than another list of things you intend to try. Team17’s file-verification reply requests a DxDiag if the problem remains. Review diagnostic files and send them privately through support rather than posting personal system details in a public comment.
- Exact error code and complete message; whether you were before the menu, joining or already in a match.
- First occurrence, local time and time zone, plus the game build and whether an update had just completed.
- File verification result: replaced files, no change, or not tested; what happened on the next launch.
- Connection comparison: same result, worked on the second connection, or not tested.
- Whether you can reach the server browser, and the server name/region if a later join attempt fails.
- Requested diagnostic attachment: Windows + R → dxdiag → Save All Information. Review it before sending.
Frequently asked questions
Does error 1147405308 mean a ban?
Not by itself. Read the accompanying message. Team17 has handled authentication failures through file and connection checks, while explicit bans require their own support path.
How do I verify WARDOGS files in Steam?
Library → right-click WARDOGS → Properties → Installed Files → Verify integrity of game files. Let the check and any replacement downloads complete before a fresh launch.
Is a VPN or changed IP a guaranteed fix?
No. A connection comparison can help diagnose routing differences, but a successful individual case does not establish a universal repair or a way to appeal a restriction.
What if I reach the browser but cannot join?
Authentication progressed further. Check the selected server’s population, region and ping-limit rules, then use the separate join-timeout checklist.
Read the original announcements and discussions below. Player reports are identified separately from official information.
- Team17: file verification and diagnostics official · September 18 support reply, rechecked November 10 · checked 2026-11-10
- Team17: authentication and time-zone checks official · September 25 case and follow-up, rechecked November 10 · checked 2026-11-10