Direct answer

A restart loop can come from startup failure, the hosting panel’s auto-restart policy, an invalid Java command or an external watchdog killing Java.

Identify the failing layer

The first fatal error usually appears before a panel watchdog announces yet another restart.

First checks and evidence

  • Stop automatic restarts temporarily using the panel or service manager so the first failure remains visible.
  • Read the beginning and end of the full console output, not only the final “restarting” line.

Admin diagnosis and repair

  1. Check exit code, Java version, missing JAR/files, port conflicts, EULA and memory limit for the failed instance.
  2. Resolve the first specific fatal error, then start exactly once and confirm a stable running process.

Verify the fix: Verify the process stays up, reports startup complete and supports a normal join and graceful shutdown.

Important safety note

Repeated restarts can obscure crash logs and worsen corruption if the world is failing to save. Back up before experimenting with world or plugin data.

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