Minecraft server logs and crash reports are some of the most useful tools for finding out why a server will not start, why a plugin or mod is failing, or what caused a server crash.

This guide explains where to find logs on a Down Side Hosting Minecraft Java server, what common messages mean, and what information to provide when contacting support.

Open your Minecraft server in the Down Side Hosting server panel and select:

Console

The console shows messages produced while the server starts and runs.

Look for terms such as:

ERROR
FATAL
WARN
Exception
Caused by:
Failed
Could not load
OutOfMemoryError
UnsupportedClassVersionError

A server may display many normal informational messages, so do not assume every warning means the server is broken.

A common troubleshooting mistake is looking only at the final line before the server stops.

The real problem may appear much earlier.

For example, the end of a log may simply say that the server stopped, while an earlier section identifies:

• A missing mod
• An incompatible plugin
• A Java version problem
• A damaged configuration
• A world-loading error

Scroll upward and look for the first meaningful error.

Minecraft normally stores the current server log at:

logs/latest.log

In the Down Side Hosting server panel:

1. Open Files.
2. Open:

logs/

1. Select:

latest.log

This file usually contains the most recent Minecraft server session.

The logs folder may also contain older log files.

These are useful when:

• The server problem happened earlier
• The server has since restarted
• You need to compare a working startup with a broken startup
• A problem occurred at a particular time

Do not assume latest.log still contains an error from several restarts ago.

When Minecraft generates a crash report, it is commonly stored under:

crash-reports/

A crash report filename may look similar to:

crash-2026-09-03_04.15.22-server.txt

The exact filename will depend on when the crash occurred.

A server stopping does not guarantee that Minecraft created a file under crash-reports/.

Some failures may only appear in:

• The console
• logs/latest.log
• Plugin logs
• Mod-loader logs

If crash-reports/ is empty, check the console and latest.log instead.

Java errors often contain a long section of text called a stack trace.

A simplified example may look like:

java.lang.RuntimeException: Example problem
    at example.plugin.SomeClass.method(SomeClass.java:100)
    at example.plugin.OtherClass.method(OtherClass.java:50)
Caused by: java.lang.IllegalArgumentException: Invalid setting
    at example.plugin.Config.load(Config.java:25)

The stack trace shows which parts of the software were involved when the error occurred.

One of the most useful phrases in a Java error is:

Caused by:

There may be several Caused by sections.

The deeper cause may contain a more specific explanation than the first error message.

For example:

Caused by: java.io.FileNotFoundException

or:

Caused by: java.lang.NoClassDefFoundError

can point toward very different problems.

When troubleshooting plugins or mods, search the error for:

• Plugin name
• Mod name
• Mod ID
• JAR filename
• Package name

If the same plugin or mod appears repeatedly near the actual error, it may be involved.

However, the first plugin or mod mentioned is not always the cause.

One piece of software may fail because another dependency is missing or broken.

A plugin problem may contain messages such as:

Could not load plugin

Unknown dependency

Error occurred while enabling ExamplePlugin

If you see a plugin name, check:

• Plugin version
• Minecraft version
• Paper/Purpur/Spigot compatibility
• Required dependencies
• Plugin configuration

See:

Minecraft Plugin Troubleshooting Guide

An error may look similar to:

Unknown dependency: Vault

This means the plugin expects another plugin or library that is not available.

Check the plugin's official documentation and install the required compatible dependency.

Forge, Fabric, or NeoForge errors may mention:

ModLoadingException

ModResolutionException

Missing mandatory dependency

or a specific mod ID.

Check:

• Minecraft version
• Mod loader
• Loader version
• Mod version
• Dependencies
• Whether the mod supports dedicated servers

See:

Minecraft Mod and Modpack Troubleshooting Guide

A mod loader may tell you directly that one mod requires another.

For example:

ExampleMod requires LibraryMod version 3.0 or later

Install the required dependency using the version intended for your Minecraft and mod-loader version.

If you see:

UnsupportedClassVersionError

this usually points to a Java version compatibility problem.

A plugin, mod, or server software component may have been built for a newer Java version than the server is currently using.

Do not randomly change Java arguments to fix this.

If the required Java version needs to be changed in the Down Side Hosting environment, contact support with the complete error and your server version information.

If the log contains:

OutOfMemoryError

the server may have run out of available Java memory.

Possible reasons include:

• Modpack requires more memory
• Too many plugins or mods for the current allocation
• Memory-heavy workload
• Software problem causing abnormal memory use

The amount of RAM available to your server is based on the Down Side Hosting plan you purchased.

If more memory is genuinely required, your server can be upgraded.

See:

How Much RAM Does a Minecraft Java Server Need?

Java may keep allocated memory available for future use.

Seeing a high memory number in the panel does not automatically mean the server ran out of memory.

An actual:

OutOfMemoryError

or related failure is much stronger evidence of a memory problem.

The console may display:

Can't keep up! Is the server overloaded?

This means Minecraft took longer than expected to process its ticks.

An occasional message during:

• Startup
• World generation
• Teleportation
• Heavy modpack loading

may not indicate a serious problem.

Repeated messages during normal gameplay may indicate a performance issue.

See:

Minecraft Server Lag Troubleshooting Guide

A networking error may contain:

Failed to bind to port

or:

Address already in use

Down Side Hosting servers are assigned their network port through the hosting environment.

Do not randomly change:

server-port=

or:

server-ip=

If you receive a binding error and have not changed the networking settings, contact Down Side Hosting support with the complete error.

Minecraft plugins frequently use YAML files.

An error may point to:

config.yml

and include a line number.

For example:

while parsing a block mapping

or another YAML parsing message.

Check for:

• Incorrect indentation
• Tabs
• Missing quotation marks
• Invalid formatting
• Duplicate entries

If the error began after editing a configuration file, restore the previous working version if available.

Minecraft also uses JSON files such as:

ops.json
whitelist.json

Plugins and mods may use JSON as well.

Errors involving JSON can be caused by:

• Missing comma
• Missing quotation mark
• Missing bracket
• Invalid value
• Manual editing mistake

If the problem began after editing a JSON file, compare it with your backup.

Logs may indicate a problem while loading:

• A world
• Chunk
• Entity
• Dimension
• Player data

If an error involves your world, do not immediately delete it.

Create or preserve a backup before attempting repairs.

See:

How to Back Up and Restore a Down Side Hosting Minecraft Server

A modded world may depend on content provided by mods.

If the server log mentions missing:

• Registry entries
• Blocks
• Items
• Entities
• Dimensions

check whether a mod was removed, downgraded, or replaced with an incompatible version.

Opening an important modded world without its required mods can damage or remove content.

Sometimes a server works until a particular player joins.

The log may identify:

• Player username
• UUID
• Player data
• Dimension
• Chunk
• Modded item
• Entity

Check the log immediately around the time that player connects.

Server logs usually contain timestamps.

These can help you match an error with a specific event.

For example:

• 03:15 — server starts
• 03:18 — player joins
• 03:19 — error begins
• 03:20 — server crashes

Knowing what happened immediately before an error can greatly narrow down the cause.

If older logs are available, compare:

• A startup when the server worked
• The startup when it failed

Look for changes involving:

• Plugins
• Mods
• Versions
• Java
• Configuration
• World loading

This can be especially useful after an update.

When asking for help, a single screenshot such as:

Server stopped

usually does not provide enough information.

Whenever possible, provide the relevant section of the log or the complete crash report.

The lines before the visible error may contain the actual cause.

Before sharing logs publicly, check for sensitive information.

Do not publicly post:

• Database passwords
• API keys
• Access tokens
• Private credentials
• Other secret configuration values

Most normal Minecraft console logs do not contain this information, but plugins may sometimes log configuration details.

When requesting help, provide:

• Minecraft version
• Server software
• Paper, Purpur, Spigot, Forge, Fabric, or NeoForge version
• Modpack name and version, if applicable
• What happened before the issue started
• Relevant console output
• latest.log when useful
• Crash report if one exists
• Plugin or mod name involved
• Whether the server previously worked

The exact error is usually much more useful than simply saying:

My Minecraft server crashed

When reading a Minecraft log:

1. Find where the problem begins.
2. Look for ERROR or FATAL.
3. Look for Exception.
4. Look for Caused by:.
5. Check for plugin or mod names.
6. Check for missing dependencies.
7. Check Minecraft and software versions.
8. Check Java-related errors.
9. Check memory-related errors.
10. Check recent configuration changes.
11. Check whether a crash report exists.
12. Compare with what changed before the failure.

The main current log is normally:

logs/latest.log

When Minecraft generates one, crash reports are normally stored under:

crash-reports/

Not every server failure generates a Minecraft crash report.

Check the console and logs/latest.log instead.

It indicates an underlying exception that contributed to the larger error.

The Caused by section can often provide a more specific clue about what actually failed.

It indicates that Java could not obtain the memory it needed.

Check your workload and RAM allocation before deciding whether additional memory is necessary.

It usually indicates that software was compiled for a newer Java version than the currently running Java environment supports.

Contact Down Side Hosting support if your server requires a Java environment change.

Not automatically.

The named plugin or mod might only be affected by another underlying problem.

Read the surrounding error and check dependencies before removing software.

No.

It can contain useful troubleshooting information.

Preserve the log until the problem has been diagnosed.

• Minecraft Server Won't Start: Troubleshooting Guide
• Minecraft Plugin Troubleshooting Guide
• Minecraft Mod and Modpack Troubleshooting Guide
• Minecraft Server Lag Troubleshooting Guide
• How to Back Up and Restore a Minecraft Server
• Minecraft Java Arguments and RAM Settings

If you cannot determine what caused the problem, contact Down Side Hosting support and provide the relevant log or crash report along with your Minecraft and server-software versions.

Contact Down Side Hosting Support

Down Side Hosting provides Minecraft Java hosting with server panel access, console controls, file management, backups, and support.

Minecraft Java hosting starts at $2/month.

View Minecraft Java Server Hosting

← Back to Minecraft Java Server Guides