What this error means
The "The server has stopped responding" error, often accompanied by a "Can't keep up!" warning in your console, indicates that your server's main thread is blocked. This happens when the server takes longer than 50 milliseconds to process a single tick, causing the game loop to stall.
Common causes
- Overloaded CPU: Too many entities, complex redstone machines, or inefficient plugins.
- Insufficient RAM: The server is constantly garbage collecting, causing "stop-the-world" pauses.
- Disk I/O bottlenecks: The server is struggling to read or write world data to the storage drive.
- Corrupt chunks: A specific area of your world is causing the server to crash or hang when loaded.
How to fix it
1. Check your resource usage
If your server is consistently hitting 100% CPU or RAM usage, it may be time to upgrade your plan. On AwakeNode, you can upgrade your plan (choose Upgrade on your server's page), and your RAM (Xmx) will update automatically without manual config changes.
2. Optimise your server configuration
- On AwakeNode: Use the File Manager to edit your
server.properties,spigot.yml, orpaper-world-defaults.yml. Lowering theview-distanceandsimulation-distancecan significantly reduce CPU load. - On other hosts: Use an SFTP client to download and edit these files manually, then re-upload them to your server directory.
3. Remove problematic plugins or mods
- On AwakeNode: Use the Files tab to remove recently added plugins or mods that may be causing the lag.
- On other hosts: Manually remove files from your
pluginsormodsfolder and restart the server to see if performance improves.
4. Contact support for advanced tuning
To add your own JVM flags, set a custom startup command in your server's Startup tab.
Questions
Does the 'Can't keep up!' message mean my server is broken?
Not necessarily. It usually means your server is struggling to process game logic in time, often due to heavy player activity or inefficient plugins.
Can I manually change my server's RAM settings?
You can set your own startup command, JVM flags included, in the Startup tab; the memory setting follows your plan. If you need more RAM, you should upgrade your hosting plan, which will automatically update your limits.
How do I know which plugin is causing the lag?
You can use a profiling tool like Spark to identify which plugins or entities are consuming the most CPU time on your server.
Will restarting my server fix this error permanently?
A restart will clear the current lag, but it will not fix the underlying cause if your server is consistently overloaded. You must identify the source of the load to prevent it from happening again.