Arc Raiders ARMR0006 Authentication Error Server Auth Fix

What is Arc Raiders Error ARMR0006?

Arc Raiders error ARMR0006 is an authentication failure that fires before you ever reach the main menu. The client successfully launches and contacts Embark's edge servers, but the Embark ID auth handshake fails — your session token is either rejected, never issued, or expired mid-call. You typically see "Authentication failed. Please restart the game." with the ARMR0006 code in the bottom-right corner. Affects PC (Steam App ID 1808500), PS5, and Xbox Series X/S.

ARMR0006 spiked sharply after the May 14, 2026 server-side identity rollout, when Embark migrated Arc Raiders auth onto a new Embark ID v2 token format. Clients caching the old token format get rejected on first contact, and players who linked accounts through Steam Family Share or shared a system between profiles are disproportionately affected.

ARMR0002 vs ARMR0006 vs ART00004 — which one are you actually seeing?

Most fix guides confuse these three. The error code tells you where in the connection chain it failed:

| Code | Stage | Meaning | First action |

|------|-------|---------|--------------|

| ARMR0006 | Pre-menu | Embark ID auth rejected your token | Sign out of Embark ID, re-link Steam/PSN/Xbox |

| ARMR0002 | Main menu → match | Matchmaking server can't find you a raid | Check ArcStatus, server load |

| ART00004 | Mid-match | Network timeout to the active game server | Network/NAT/router fixes |

If you cannot reach the main menu, it's ARMR0006, not the other two — don't waste time on NAT or DNS first.

When does it occur?

• Immediately after launching the game, before the title screen
• After the May 2026 server-side identity rollout if your client cached an old token
• When the linked Steam/PSN/Xbox account doesn't match the Embark ID on file
• After Embark account password change or 2FA reset
• When EasyAntiCheat boots but fails to forward the platform ticket
• On accounts created via Steam Family Share or shared PCs with multiple profiles

Common causes

• Stale Embark ID v1 token cached locally that the v2 backend rejects
• Platform-to-Embark account mismatch — Steam ID is linked to a different Embark ID than the one currently authenticated
• System clock drift of more than 5 minutes (token signature validation fails)
• EasyAntiCheat platform ticket not forwarded because of corrupted EAC install or anti-cheat service stopped
• Region lockout — VPN or geo-IP mismatch triggers Embark's regional auth gate
• Embark ID 2FA cooldown after a recent password change (5–15 minute window where auth is throttled)
• **Cached embark_auth.dat file** corrupted by abrupt game shutdown

Step-by-step fixes

1. Force a full Embark ID re-link — Go to [id.embark.games](https://id.embark.games), sign in, then Account > Linked Accounts and unlink Steam/PSN/Xbox. Wait 60 seconds. Re-link the platform you play on. This burns the cached v1 token and forces issuance of a fresh v2 token. This single step fixes the majority of post–May 2026 ARMR0006 cases.

1. Delete the local auth cache — Close the game completely. Navigate to %LOCALAPPDATA%\Arc\Saved\Config\WindowsClient\ (PC) and delete embark_auth.dat and EmbarkID.ini. On PS5/Xbox, hard-reboot the console (hold power 10 seconds, full power off, not rest mode). Relaunch Arc Raiders.

1. Sync your system clock — Open Settings > Time & language > Date & time, toggle Set time automatically off then on, then click Sync now. Token signature validation rejects clients with >5 minutes of clock drift. This is mandatory before any other fix on a fresh Windows install.

1. Repair EasyAntiCheat — Navigate to Steam\steamapps\common\ARC Raiders\EasyAntiCheat\ and run EasyAntiCheat_Setup.exe as Administrator. Select ARC Raiders from the dropdown, click Repair Service. EAC forwards the Steam ticket to Embark — a broken EAC blocks ARMR0006 even when your account is fine.

1. Disable any VPN and check region — Disconnect from NordVPN, ExpressVPN, Cloudflare WARP, Mullvad, etc. Embark's auth gate cross-checks your account region with your current IP — a U.S. account hitting EU servers via VPN trips ARMR0006. Make sure your Windows region (Settings > Time & language > Region) matches your physical location.

1. Reset your Embark ID password — Visit [id.embark.games/forgot-password](https://id.embark.games), reset the password, wait 15 minutes (2FA throttle), then sign back in via Steam/PSN/Xbox. If you have 2FA enabled, regenerate the recovery codes from the dashboard before retrying.

1. Verify game files in Steam — Right-click Arc Raiders in Steam > Properties > Installed Files > Verify integrity of game files. A corrupted EmbarkAuthLib.dll or OnlineSubsystemEmbark plugin will return ARMR0006 even when the account is healthy. The verifier should redownload 1–80 MB if these are damaged.

1. Reinstall EAC from scratch — If repair didn't help, delete both C:\Program Files (x86)\EasyAntiCheat AND C:\Program Files (x86)\EasyAntiCheat_EOS. Restart Windows. Launch Arc Raiders — EAC downloads fresh and re-pairs with Embark's auth service. This resolves ARMR0006 caused by corrupted EAC binaries left over from older Arc Raiders patches.

If it still doesn't work

If ARMR0006 persists after a full re-link and EAC reinstall, the issue is almost always server-side throttling on your specific Embark ID — open a ticket at [Embark Help Center](https://id.embark.games/arc-raiders/support) and include your Embark ID, the exact UTC timestamp of the failure, and your Steam/PSN/Xbox ID. Embark's auth team can manually flush the token cache server-side, which fixes accounts that are stuck in an inconsistent state after the May 2026 migration. While waiting, you can confirm whether it's account-specific by signing into Arc Raiders on a different Steam account on the same PC — if that succeeds, your Embark ID needs manual intervention rather than further client troubleshooting.