Fix "Exception in server tick loop" crash

The server stops, the Console prints a crash report, and the report's description reads Exception in server tick loop. That is a general title that does not name a cause, so the real reason is further down the report. Find the report, read the cause out of it, then deal with the usual ones.

Checked against Minecraft 26.3 and the Paper documentation, October 2026.

Find the crash report

1. Open the Console tab. Near the end of the output the server prints This crash report has been saved to: with the path. The panel also shows a red Your server crashed - restarting automatically… line.
2. Open the File Manager and go into the crash-reports folder.
3. Names look like crash-2026-10-21_14.02.31-server.txt, which is the date and time of the crash. Pick the one with the latest date.
4. Click the file to read it in the panel.

If the crash happened a while ago, press Download Log on the Console tab instead and choose Last hour, or Earlier boots (7 days) for an older crash. Find Minecraft server logs and crash reports goes through the sections of a report in more detail.

Read the cause

The top of the file has a Description: line, then a Java stack trace. Skim it for three things:

• Lines starting Caused by:. The last one is the deepest cause Java recorded.
• The name of a plugin or mod. It often shows as a package such as com.example.myplugin. The Paper documentation says that in most cases the plugin whose name is found in a stack trace is causing the problem.
• A Ticking entity, Ticking block entity or Ticking player section further down. It names the thing the server was processing when the crash hit.

The most common causes are mods, bugs in the game itself, updates and running out of memory (minecraft.wiki's list). Match what you found:

A mod or plugin is named in the trace

1. Open the Mods tab (Plugins on Paper, Purpur and Folia) and switch to Installed.
2. Press Disable next to the one named, or the last one you added, then restart from the Console tab.
3. If the server now runs, press Check for updates on the same tab. A newer build often fixes it. If not, leave it off.

A specific entity or block entity is named

Something in the world is crashing every time the server tries to process it. Fix ticking entity crashes on modded servers covers removing it.

OutOfMemoryError

The server ran out of memory. Our servers get their memory from the plan, and you cannot change the Java settings, so reduce the load or move up a plan. In the Config Editor, under Performance, lower View distance (chunks) and Simulation distance (chunks). How much RAM does my Minecraft server need? and Upgrade or downgrade your plan help you decide.

No space left on device

The disk is full. Server out of disk space? Free it up shows how to clear it. Open the Disk Analyser tab first to see what is taking the room.

The related "single server tick took 60 seconds" crash

A different line also ends in a crash: A single server tick took 60.00 seconds (should be max 0.05), followed by Considering it to be crashed, server will forcibly shutdown. The server's watchdog stopped it because one tick ran far too long. The limit is Watchdog timeout (ms) in the Config Editor, under Performance, and it defaults to 60000. Setting it to -1 turns the watchdog off, but that only hides the stall. Find what stalls with a profiler instead: Reduce Minecraft lag with spark and plugins.

After the crash

If the world looks wrong after a crash, restore a backup from before it: How to create and restore backups. Take a fresh backup before you change mods, so the next crash is easy to undo.