Direct answer

For routine shutdowns, announce downtime, allow saves to complete, and use stop in the Minecraft server console. Abruptly killing Java risks interrupted writes.

Safe shutdown

  1. Warn players and stop scheduled automation that would immediately restart the service during maintenance.
  2. From the real server console, use save-all flush if supported by your exact server version, then stop. When entering commands at the console, omit the leading slash.
  3. Wait for the shutdown process to finish and verify the host panel reports the process stopped before editing worlds, plugin files or the server JAR.
save-all flush
stop

Restart after plugin changes

Do not replace plugin JARs while the server is running. Stop fully, install the planned JAR, start the server and inspect the startup log for a missing dependency or version conflict. Test key plugin commands before reopening to players.

Before maintenance

A successful save-all is not a substitute for a consistent offline backup. Replacing JARs or editing world files during a running process is unsafe.

If the server is frozen

If shutdown is stuck, inspect logs and the provider’s recommended graceful termination procedure before resorting to force-killing the process. Record crash reports and logs before restarting; a force kill is a last resort, not routine maintenance.

Automated restarts

Pause any panel or systemd restart loop during scheduled maintenance so it does not restart the server while world files or JARs are being replaced. After the clean start, re-enable the service policy and verify the scheduled restart path. Start the server again, read the end of the old and beginning of the new log, check world loading and verify player data persists.

Official references

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