☰

Server Is Full

Players see 'The server is full!' and cannot join. The number of connected players has hit the configured maximum, so new logins are refused until a slot frees up.

What does this error mean?
The max-players value in server.properties caps how many players can be online at once. When that cap is reached, additional players are turned away. If it fills sooner than expected, stuck/ghost connections may be occupying slots. 
The server is full!
Most Common Causes
  • Genuinely reaching the max-players limit.
  • A max-players value set too low.
  • Ghost/stuck sessions holding slots after disconnects.
  • No reserved-slot bypass for staff.
  • A proxy miscount across backends.
How To Diagnose
  1. Check max-players in server.properties.
  2. Compare it to the actual online count.
  3. Look for ghost sessions if the count seems wrong.
  4. If using a proxy, verify slot counting across servers.
Recommended Fixes
  • Raise max-players
    Increase the limit in server.properties (within your hardware's capacity) and restart.
  • Add a slot bypass
    Grant staff a reserved-slot/bypass permission via a plugin so they can always join.
  • Clear ghost sessions
    Remove stuck connections that are occupying slots without a real player.
  • Mind the hardware
    Only raise the cap as far as your CPU/RAM can comfortably support.
Analyze My Log
Frequently Asked Questions

As high as your hardware supports, more players mean more CPU/RAM and entity load.

Ghost/stuck sessions may be holding slots. Clear them or restart to free the count.

Yes, with a reserved-slot/bypass permission from a plugin, even when the server is full.