Troubleshooting

Server won't start

First things to check when your server refuses to boot.

If your server is stuck on Starting or flips back to Stopped immediately, work through this list.

Read the console

The very last few lines of the console almost always tell you exactly what went wrong. Stack traces look intimidating; the first line of the exception is usually enough.

Common causes

  • EULA not accepted. First-time start? Open eula.txt in the file manager and change eula=false to eula=true. (We try to do this for you, but if you uploaded your own server.jar, it may have reset.)
  • Port in use. Almost never the cause on Kyrbit because public ports are assigned by the platform, but possible if you've changed server-port to something the platform doesn't expose.
  • Bad mod or plugin. If you just added something, remove it and try again. A mod jar built for the wrong Minecraft version is the #1 modded-server crash.
  • Corrupted world. Restore the most recent backup.
  • Wrong Java version for your modpack. This usually means the server was created with the wrong Minecraft version or loader for that pack. Create a fresh server with the matching version/loader, or open a support ticket before changing an existing world.

When to open a ticket

If the console shows an error that doesn't look like any of the above, or shows nothing useful at all, copy the last 50 lines into a support ticket and we'll dig in. During beta we'll usually reply within a few hours.

Didn't find what you needed? Open a support ticket. During the closed beta you'll get a real human reply, usually within a few hours.