The console is the fastest diagnostic tool you have. It shows live server output and lets you run commands directly, without needing to be in game.
Reading startup
A healthy start ends with a line confirming the server is ready and reporting how long it took. If output stops before that, the last few lines usually name the problem.
Common warnings
- "Can't keep up" — the server took longer than its tick budget. Occasional instances during world generation are normal; constant ones mean a performance problem.
- Failed to bind to port — the previous process has not fully stopped. Stop the server and wait before starting it again.
- Plugin or mod errors on startup — usually a version mismatch or a missing dependency.
- Out of memory — the allocation is too small for what you are running.
Always stop a server properly rather than killing it. An unclean shutdown is a common cause of corrupted world data.
Hosting documentation. The original publication date was not recorded; the maintained update date is shown above.
Related articles
- Lag spikes: how to run a WinMTR testCapture the network route to your server while lag spikes happen, then send the results to EnderHost support.3 min read
- What Are Minecraft TPS and MSPT?Read tick rate and tick duration together to distinguish sustained server lag, brief stalls and network delay.3 min read
- How Much RAM Does a Minecraft Server Need?Choose memory from the server workload, JVM heap and total process limit—not a promised number of players per gigabyte.3 min read
