Direct answer

Compare that player’s client, account, network, player data, resource pack, mods, and logs when the server works for everyone else.

What it means

When everyone else can join, the shared server path is probably working. The useful differences are that player’s account/UUID, client profile, network route, cached/resource data, or player-specific server data.

If you are a player

  • Record the exact kick message, client edition/version, timestamp and whether you can join another server.
  • Try a clean client with required mods and packs only; check account session without sharing login credentials.
  • Ask whether the problem occurs on a second network; do not repeatedly reinstall the server.

If you run the server

  1. Find the affected UUID and exact login exception in the proxy and backend logs; determine which host rejects the connection.
  2. Check player-specific bans, whitelist records, permission/limit plugins and authentication; do not reset all player accounts.
  3. If the log names a malformed inventory or player NBT, back up that player’s data before testing targeted recovery on a copy.
  4. Compare working and failing clients for protocol bridge, mod/registry set and server-required resource pack.

Verify the result: Confirm this specific player can enter and retain inventory/location after disconnecting, while unaffected players still join normally.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000