Troubleshooting Common Minecraft Server Errors & Security Warnings

When running a Minecraft server, you may occasionally encounter error messages in your console or crash logs. While many errors are simple configuration issues or Java version mismatches, certain error messages indicate serious security threats caused by infected or pirated plugins.

This comprehensive guide covers how to identify and resolve common Minecraft server errors, with a special focus on critical malware warnings.

🚨 Critical Security Warnings & Malware Errors

If you see either of the two errors below in your server console, take immediate action. These warnings indicate that your server is running compromised or malicious plugin code.

1. BlackSpigot & DirectLeaks Errors / Tags

• Console Symptom: References to BlackSpigot, DirectLeaks, or unauthorized license check bypasses appearing during server boot.
• The Cause: Downloading pirated or "leaked" premium plugins from unauthorized third-party sites. These sites frequently inject hidden backdoors, force-op exploits, or ransomware scripts into plugin .jar files.
• What to do:
  1. Delete the plugin .jar file from your /plugins/ folder immediately.
  2. Never download plugins from unauthorized leak sites. Always obtain plugins directly from official sources like SpigotMC, PaperMC, Modrinth, or CurseForge.
  3. If your server was compromised or you suspect an admin account was accessed, contact Cubes Support immediately so our team can assist you in auditing your files.

2. "Set PluginClassLoader as parallel capable" Warning / Error

• Console Symptom: A stack trace or error message containing Set PluginClassLoader as parallel capable during startup.
• The Cause: This error is a known signature of malicious bytecode injection (such as the Fractureiser malware or malicious obfuscated plugin backdoors). The malware attempts to illegally hook into Java's PluginClassLoader to inject unauthorized code, steal credentials, or spread to other server files.
• What to do:
  1. Stop your server immediately.
  2. Remove the newly added plugin .jar that triggered this error message.
  3. Change your Game Panel and RCON passwords as a safety precaution.
  4. Contact Cubes Support so we can help inspect your server container and verify that no hidden background scripts remain.

⚠️ The Dangers of Using Cracked & Nulled Plugins

It is tempting to download paid plugins for free from "nulled" or "leaked" sites, but there is no such thing as a free pirated plugin. People who operate leak sites modify the plugin's Java bytecode to insert malicious backdoors.

Running cracked plugins exposes your server to:

• Hidden Force-OP Backdoors: Malicious developers add secret chat commands or trigger words. Anyone who knows the secret code can type it in your server chat to instantly grant themselves full OP administrator status, bypassing all security!
• Credential & Database Theft: Infected .jar files can silently scan your server folder for server.properties and plugin config files to steal your RCON passwords, database credentials (MySQL/SQLite), and secret API keys.
• Server Container & World Corruption: Malware like Fractureiser infects other .jar files on your server, corrupting world saves and spreading to any other plugins in your /plugins/ folder.
• Botnet & Spam Relays: Compromised servers are often used in the background to send out spam or participate in DDoS attacks without the server owner's knowledge.

Rule of Thumb: Always download plugins from trusted, official distribution platforms such as SpigotMC, PaperMC (Hangar), Modrinth, or CurseForge.

🛠️ Common Startup Errors & Fixes

Below are standard technical errors that occur due to configuration mismatches:

3. "Has been compiled by a more recent version of the Java Runtime"

• The Cause: You are trying to run a modern Minecraft version or plugin using an older Java version (e.g. trying to run Minecraft 1.20+ on Java 8).
• The Fix: Go to your Cubes Hosting Game Panel > Configuration > Startup Parameters, and switch your Java Version to the required version:
  • Minecraft 1.20.5+: Requires Java 21
  • Minecraft 1.17 – 1.20.4: Requires Java 17
  • Minecraft 1.12 – 1.16.5: Requires Java 8 or Java 11

4. java.lang.OutOfMemoryError: Java heap space

• The Cause: Your server has run out of allocated RAM. This happens when too many chunks are loaded at once, or when running too many plugins/mods for your current plan.
• The Fix:
  • Lower your server's view and simulation distances (see our View Distance Optimization Guide).
  • Upgrade your Cubes Hosting plan to allocate more RAM to your server.

5. Can't bind to port / Port already in use

• The Cause: Another server process is still shutting down in the background, or your server.properties has an incorrect IP/port specified.
• The Fix:
  • In server.properties, ensure server-ip= is left blank (server-ip=).
  • Restart your server from the Game Panel to force-kill any lingering background processes.

6. java.lang.NullPointerException: Ticking entity / Corrupted Entities

• The Cause: A mob, item frame, armor stand, or tile entity in your world became corrupted and crashes the server loop whenever its chunk is loaded.
• The Fix: Enable auto-remove-corrupt-tile-entities in your paper.yml configuration file or use coordinate-based kill commands. Check out our step-by-step guide on How to Fix Ticking Entity Crashes for full instructions!

7. MissingModsException / ModLoadingException: Mod X requires Mod Y

• The Cause: A mod on your Forge, Fabric, or NeoForge server relies on a required library or API dependency mod (e.g. Fabric API, Architectury API, Cloth Config, Curios API, or GeckoLib) that is missing from your /mods/ directory.
• The Fix:
  1. Open your server console log (/logs/latest.log) and read the exact missing mod name listed in the error message (e.g. Requires fabric-api 0.90+).
  2. Use your Game Panel Tools > Plugin & Mod Installer (or download from Modrinth/CurseForge) to install the missing library .jar into your /mods/ folder.
  3. Restart your server.

8. Mismatched Mod Channel List / Incompatible Mod Set

• The Cause: A player gets disconnected when attempting to join a modded server because their local computer's launcher has different mods, missing mods, or mismatched mod version numbers compared to the server.
• The Fix:
  1. Match Client & Server Mods: Ensure players use custom launchers (like CurseForge App, Prism Launcher, or Modrinth App) to install the exact same modpack and mod versions as the server.
  2. Remove Client-Only Mods from Server: Ensure client-side-only rendering mods (such as Iris Shaders, Sodium, OptiFine, Rubidium, or Custom FoV) are NOT installed in your server's /mods/ directory. Placing client-only mods on the server will trigger channel mismatch disconnects!

Summary Action Plan

Whenever your server fails to start:

1. Check the Console Logs: Always read the top lines of the crash log in /logs/latest.log.
2. Isolate New Plugins: If an error occurred after adding a plugin, remove it to test if the server boots cleanly without it.
3. Reach Out to Support: If you encounter suspected malware, backdoors, or unresolvable crashes, our Cubes Hosting support team is always here to help!