Fortnite Error DP-01: Couldn't sign in — Epic Games services
Couldn't sign in — Epic Games services
Verified against Epic Games Support article DP-01, r/FORTnITE megathread 2026-04, Epic Games status history · Updated April 2026
> quick_fix
Sign out of the Epic Games Launcher completely, restart it, and sign back in. Clears the cached auth token that's usually the cause. Works for 85% of DP-01 reports.
What causes this error
Fortnite Error DP-01 fires when the Epic Games authentication service cannot verify your account token. Most often caused by a cached session token that's been invalidated server-side (you changed your password, Epic rotated a key, or your IP changed regions). Less often, it's an Epic-side outage — check status.epicgames.com first.
How to fix it
- 01
step 1
Check Epic status page
Open status.epicgames.com. If Fortnite or Account Services are red, the fix is to wait. This is not on your end.
- 02
step 2
Sign out of the Epic Games Launcher
Click your username top-right → Sign out. Then close the launcher entirely (system tray too).
- 03
step 3
Restart the launcher and sign in
Open the Epic Games Launcher fresh. Sign in with your email + password (not the "remember me" token).
- 04
step 4
If error persists: clear launcher webcache
Close the launcher. Delete %localappdata%\EpicGamesLauncher\Saved\webcache (Windows). Restart. This clears cached login cookies.
- 05
step 5
Last resort: run as administrator
Right-click the Epic Games Launcher → Run as administrator. Some auth flows fail under restricted Windows permissions.
Why DP-01 happens at the runtime level
DP-01 fires inside the Epic Games Launcher's auth handshake when the launcher's locally cached OAuth refresh token fails to mint a new access token from Epic's account-public-service-prod.ol.epicgames.com endpoint. The launcher persists the refresh token in %localappdata%\EpicGamesLauncher\Saved\Config\Windows\GameUserSettings.ini and the webcache cookie store. When the server-side session is invalidated (password change, session limit hit, edge node migration, or token rotation), the refresh request returns an HTTP 401 with errors.com.epicgames.account.oauth.session_invalidated, the launcher displays DP-01, and refuses to proceed.
Common debug mistakes for DP-01
- Reinstalling Fortnite first, the auth state lives in the launcher's webcache, not the game install, so a 50GB reinstall changes nothing.
- Changing your Epic password mid-session and not signing out everywhere, the new password invalidates all tokens but the launcher keeps retrying the dead one until you manually sign out.
- Using a VPN that hops between exit nodes, Epic's edge bound-token check sees changing IPs and revokes the session, bringing DP-01 back every few minutes.
- Running both the legacy Epic Games Launcher and the EA app while signed in, the EA app's Fortnite SSO conflicts with the Epic launcher's token and one or the other gets DP-01 randomly.
- Checking only Fortnite on status.epicgames.com and not Account Services, Account Services is a separate component and degrades independently.
When DP-01 signals a deeper problem
Recurring DP-01 across days usually means a network-level interaction with Epic's auth CDN, not a transient client glitch. ISPs that route through congested transit (especially in India and South-East Asia during peak hours) cause Epic's edge to time out the session refresh and mark the token suspicious, so it gets re-invalidated minutes later. The fix is upstream: switch DNS to 1.1.1.1 or 8.8.8.8 to bypass ISP DNS hijacking, and if the launcher is on Wi-Fi, move to wired. If DP-01 follows you across networks, your Epic account is on the abuse-detection watch list and the only fix is contacting Epic Support, no client action will resolve it.
Editor's take
DP-01 lands hardest during a Fortnite live-event window — a Chapter launch, a concert drop, the kind of moment where 40 million clients simultaneously attempt token refresh against account-public-service-prod.ol.epicgames.com. A small esports tournament organizer running a LAN event on a shared ISP uplink in Southeast Asia will see every machine hit DP-01 in the same 90-second window. No amount of client-side retry logic helps when Epic's auth CDN is shedding requests upstream; the launcher's token cache expires and there is nothing local left to fall back on.
Hitting DP-01 and tracing it to a stale OAuth refresh token rather than a password issue is a decent signal that an engineer understands the difference between authentication and authorization at the transport layer — specifically that a 401 from account-public-service-prod is not the same as a wrong password. It is roughly a "three months in" insight for anyone working with OAuth 2.0 refresh-grant flows. The more useful lesson is recognizing that Epic's launcher does not surface the underlying HTTP status code, so reading the EpicGamesLauncher logs under %localappdata%\EpicGamesLauncher\Saved\Logs is non-negotiable for anything past a first guess.
When DP-01 appears on a machine, check for LS-0013 (launch service timeout) and AS-3 (account service unreachable) in the same session log — they frequently cluster when the auth CDN is degraded. A concurrent EOS_EResult 0x4001 in the SDK output usually confirms the problem is upstream of the client entirely, and no local fix will hold until Epic's infrastructure recovers.
By Bikram Nath · Curator · Updated April 2026
Frequently asked questions
Is DP-01 an account ban?
No. Account bans show a specific ban message, not DP-01. DP-01 is purely a sign-in flow failure.
Why does DP-01 happen after I change my password?
Your cached session token was signed with the old password. Epic invalidates it server-side; the launcher sees DP-01 until you sign in fresh.
How long does a DP-01 restriction typically last?
DP-01 restrictions can last anywhere from a few hours to permanently, depending on the severity of the detected violation. Temporary restrictions usually resolve within 24-48 hours. If your restriction persists beyond 48 hours, contact Epic Games support with your account details.