Player can't join but everyone else can, a checklist

The server is up. 5 players are online and playing. But one player keeps getting some error and can't join. This is one of the most-puzzling support scenarios. The cause is on the player's side, the server's whitelist, or some interaction specific to them.

This article is the checklist.

The full diagnostic flow

What error are they seeing?

This is the most important question. Different errors point to different causes. Get the exact message.

Common possibilities:

"You are not whitelisted on this server"

Self-explanatory. They're not on the whitelist.

Fix: /whitelist add <username>. Confirm spelling.

If their username has changed (Minecraft allows username changes), the whitelist file may still show their old name. Whitelists are keyed on UUID, so the entry usually still works; if it doesn't, re-add with the new name to refresh it.

"You are banned from this server"

Also self-explanatory. They're banned.

Fix (if intended): explain why. Fix (if unintended): /pardon <username>.

If they're banned by IP (not just username), the ban entry is in banned-ips.json and you'd need to look there.

"Failed to verify username" / "Bad login"

Their Mojang authentication failed. Either:

• They're using a cracked / non-premium account on an online-mode server.
• Mojang's auth servers are down (rare).
• Their account password recently changed and their client hasn't re-logged.

Fix: ask them to log out of Minecraft, then log back in.

"Outdated client" / "Outdated server"

Version mismatch. They're on a different MC version than the server.

Fix: confirm version. Player updates client.

"You are already connected to this server"

Their previous connection didn't close cleanly. Server still thinks they're online.

Fix: wait a few minutes (usually times out automatically). Or restart the server.

"Connection refused"

See the connection refused article. If everyone else can connect, the issue is specific to that player's network or their address.

"Internal Exception: ..."

See the Internal Exception article. Usually player-side network.

"Server is full"

Player count cap. Free up a slot or upgrade.

"Failed to load chunk"

World file may be having issues at their spawn point. Rare.

Fix: if they have admin help, teleport them elsewhere via console. If not, try restarting.

A specific mod / plugin error

Modded servers can produce errors from mod-level kicks. Read the message carefully.

Step-by-step diagnosis

If the error doesn't immediately point to a fix:

Step 1: get the exact error

Don't accept paraphrases. Screenshot or exact wording.

Step 2: have them try basic fixes

• Restart their Minecraft client.
• Confirm they're using the exact address you've given.
• Try once more.

Solves about 30 percent of cases.

Step 3: confirm their identity

• Confirm their Minecraft username.
• Confirm they're using the right account (some players have alts).
• Cross-check with whitelist / ban lists.

Step 4: have them try from a different network

If possible, mobile data or a friend's house.

• Works from elsewhere: their home network has something wrong.
• Doesn't work anywhere: their account or your server's restriction.

Step 5: have them check Minecraft service status

Mojang authentication status. There is no first-party public status dashboard, so check community trackers (xpaw.me/mcstatus and similar) plus social-media reports. If Mojang's auth is down, no one can connect with online-mode anyway; a partial outage looks like "some players blocked, some fine."

Step 6: check your server logs

The server logs the attempted connection and the rejection reason. Often more verbose than what the player sees.

[INFO] [user]: disconnect for user1 (xxxxx) reason: Not whitelisted

Match the reason in the log to the fix.

Step 7: try removing all of their state

If nothing else works:

• Remove them from the whitelist.
• Restart server.
• Add them back to whitelist.
• Have them retry.

This clears any in-memory state that might be stuck.

Step 8: replicate

Try connecting with your account (or a test account) from their network if feasible. If you can connect, the issue is account-side. If you can't, network-side.

Player-side issues that look server-side

A few that masquerade as server problems:

Outdated launcher / client.

Minecraft launcher updates sometimes break things. Have them update or reinstall.

Mod compatibility (modded).

A modpack version mismatch. Even a single mod difference can fail.

Their account is locked / suspended.

Mojang occasionally locks accounts for unusual activity. Most fixes are out of your hands.

Their game cache is corrupt.

The asset cache (assets/objects inside their .minecraft folder) can become corrupt. Delete it and let the launcher re-download.

Antivirus / firewall on their PC.

Some overzealous antivirus software blocks Minecraft connections. Worth asking about.

A specific scenario: "I was just playing, now I can't"

Player was online 10 minutes ago. Now can't connect.

Common causes:

1. Their session token expired. Re-login.
2. They were kicked (anti-cheat, ban, etc.). Check logs.
3. Their network just went down on their side.
4. The server restarted and their client hasn't refreshed the server list.

Re-login is the most common fix.

A specific scenario: "I can join, but I'm immediately kicked"

They connect, see the world for a fraction of a second, get kicked.

Likely causes:

1. Anti-cheat plugin: false positive at login.
2. Their player file is corrupt: they spawn into invalid state.
3. They land in a chunk that's having issues.

Diagnostic: try teleporting them to spawn (or 0,0) via console as they connect. If they survive, their previous location was bad.

A specific scenario: "Multiple people from one network can't connect"

Family members on the same home network. Or roommates.

Common causes:

1. Their router doing something funny (NAT issues, double-NAT).
2. Their ISP doing something funny (CGNAT, traffic shaping).
3. Their network's MTU is wrong for the path.

Diagnostic: have one of them try from a different network. If it works, their network has the issue.

A specific scenario: alt accounts

A player is on the server with their main account. They try to join with an alt and fail.

Common causes:

1. Whitelist only has their main account.
2. They don't have permission for two simultaneous sessions.
3. Their alt has a different IP and triggers a security flag.

Fix: explicitly handle alts per your community's policy. Some allow, some don't.

Common admin mistakes

Assuming "everyone else is online so the server is fine."

The server can be fine and still have a specific player kicked for a specific reason. Read the log.

Not getting the exact error message.

"Some error" or "it didn't work" is impossible to diagnose. Insist on screenshots.

Restarting the server to "fix" a player-specific issue.

Disrupts the other 5 players for no benefit. Make sure it's a server-side issue first.

Forgetting to check the username spelling.

Minecraft usernames can have similar-looking characters (l vs I vs 1). Get the username from the player's profile, not their typing.

Treating bans / whitelists case-sensitive.

Most ban / whitelist systems are case-insensitive but some plugins aren't. Confirm with your specific plugin.

A diagnostic template

When taking a "I can't connect" report:

1. Exact error message (screenshot ideal):
2. What did you try? (restart client, retry, etc.):
3. Are other players online right now?
4. What's your Minecraft username (exact spelling)?
5. When did this start?
6. Can you try from another network if possible?

The first three answers usually resolve it.

Conclusion

"Player can't join but others can" is annoying but almost always diagnosable. Get the exact error, check the obvious (whitelist, ban, version), have them try basic client fixes, read your server log for their attempted connection.

90 percent of these cases are: username changed, version mismatch, or their network. The remaining 10 percent need more digging but follow the same systematic approach.

Don't restart the server in panic. Diagnose.