What the Authentication Errors Means

The Authentication Errors appears when EXM detects an authentication problem that requires the application to restart. This can happen if your login token is invalid, your session has expired, your account status changed, or the app hit an authentication-related failure that it cannot recover from without restarting.

In short, EXM is forcing a restart so authentication can be rechecked cleanly.

Why This Happens

The Authentication error is typically triggered by one of the following:

  • your login session expired

  • your auth token is invalid or no longer accepted

  • the app could not verify your account correctly

  • your account was signed out elsewhere

  • EXM detected a user or account auth issue

  • a temporary connection or backend auth failure occurred

When this happens, EXM may close, restart, or ask you to relaunch so it can attempt authentication again. The codebase description for AuthRestartModal notes it is tied to an invalid token, user-banned state, or auth error that forces restart.

How to Fix the Authentication Error

Follow these steps:

  1. Fully close EXM
    Make sure the app is completely shut down before reopening it.

  2. Reopen EXM
    Launch the app again and allow it to re-authenticate.

  3. Log in again if prompted
    If your session expired, signing in again may immediately resolve it.

  4. Check your internet connection
    Make sure EXM can reach its authentication services without interruption.

  5. Disable VPN or proxy temporarily if applicable
    In some cases, network routing or filtering can interfere with auth checks.

  6. Make sure your system time is correct
    Incorrect system time can sometimes create authentication issues.

  7. Restart your PC if the issue keeps appearing
    This helps clear stuck processes or session conflicts.

If the Error Continues

If you still get Authentication Errors after relaunching:

  • sign out and sign back in if possible

  • make sure you are using the correct account

  • check whether your subscription or account status changed

  • contact support if the app continues forcing restarts

When contacting support, include:

  • the exact error name: (ex: VPN detected)

  • when it appears

  • whether it happens every launch or only sometimes

  • whether you recently changed accounts, passwords, or billing

  • whether you are using a VPN, proxy, or custom DNS

Important Note

This error does not always mean your account is permanently blocked. In many cases, it is just a session or token problem that needs a clean restart and re-authentication. Based on the error mapping you shared, this modal is specifically used for invalid token, banned user, or general auth failures that require restart.