All

You are logged in from another location / connection throttled

Two different mechanisms share this error. Account-side: Mojang's session service ends a session when the same account logs in elsewhere. Server-side: connection throttling delays rapid reconnects to stop join-spam. The wording and timing tell you which one is talking.

Fastest path: paste your crash report into the Crash Doctor — it identifies this pattern and 40+ others automatically. No signup.

How to fix it

  1. 1

    Was it you? If not, secure the account

    An unexpected 'logged in from another location' means another session exists — change your Minecraft/Microsoft password immediately and sign out all sessions.

  2. 2

    If it was you: old sessions linger

    Switching devices or a crashed client can leave a stale session. Wait a minute or two and reconnect; the session service clears it.

  3. 3

    Server-side throttling after rapid reconnects

    Paper/Spigot servers throttle join attempts (connection-throttle-limit in spigot.yml, or timeouts after a crash-loop of clients). Wait out the window or raise the limit if you run the server.

  4. 4

    Admins: check for a reconnect storm

    A misbehaving client auto-retrying joins can throttle itself and everyone behind it. One reconnecting player causing repeated throttles is worth investigating on its own.

Alternative causes

These can produce the same error message — worth ruling out if the steps above don't resolve it.

Shared or VPN IPs

VPNs and CGNAT put many players behind one address; some throttle logic is IP-based. Trying another network distinguishes IP-effects from session-effects.

Offline-mode UUID clashes

On offline-mode servers, name collisions masquerade as session errors. Running online-mode (premium accounts) removes the whole class of problem.

Frequently asked

Is my account hacked?

Not necessarily — crashed clients and second devices leave stale sessions. But an unexpected message with no explanation deserves a password change as the safe default.

What is connection-throttle-limit?

A Paper/Spigot setting controlling how aggressively the server delays reconnects from the same address. Default is fine for normal play; raise it only for scripted scenarios.

Does restarting the server clear it?

Server-side throttle state clears with a restart; Mojang session state does not — that lives on Mojang's side.

Want this auto-fixed on your server?

CoalHosting's Minecraft hosting runs the same pattern database against every crash and applies the known fix before your players notice. Free crash diagnosis works on any server, hosted or not.

Run Crash Doctor on your report →Get a server with auto-fix

Related crashes

Outdated client! Please use 1.21.x (protocol mismatch)

'Outdated client' means client and server run different Minecraft versions. Match the versions — or bridge the…

Server exited with code 1

Exit code 1 means the JVM hit an unhandled error. The code itself says nothing — the real cause is in the log …

Last reviewed 2026-09-06. If a step is wrong or out of date, tell us — we'll fix the article and the auto-pattern at the same time.