Cardinal ReviewError library
148 server errors, explained.
Every error Cardinal Review recognises in a console or log file, with what it means and how to fix it. Find yours below, or paste your whole log into the live demo to match it for you.
Minecraft 43
Paper, Spigot, Folia, Purpur, Velocity, BungeeCord, Forge, NeoForge and Fabric: what each console message means and what to change.
- Minecraft EULA has not been accepted
- Server can't keep up (ms ms behind)
- Server stopped responding (watchdog)
- Server crashed in the tick loop
- Crash report written
- Plugin failed to load: file
- Error while enabling plugin plugin
- Plugin plugin disabled itself
- Plugin is missing a dependency: deps
- Plugin targets an unsupported API version
- Plugin plugin does not support this server version
- Same plugin installed twice: plugin
- Plugin plugin threw an error handling an event
- Broken config file: a plugin config
- Errors trace back to a plugin
- Plugin plugin task crashed
- Command command crashed
- Console command ran without a world
- Plugin uses outdated or unsafe server APIs
- Server software is outdated
- Player connected with the wrong Minecraft version
- Connections dropped while logging in (unreadable login packet)
- Player rejected: 'Failed to verify username'
- Mojang login servers could not be reached
- Players time out while logging in
- World was saved by a newer Minecraft version
- Data packs failed to load
- Entities share the same UUID
- A JSON file could not be read
- Server icon could not be loaded
- Geyser cannot log Bedrock players in to the Java server
- Player movement rejected ('moved too quickly')
- Server runs in offline (insecure) mode
- Proxy forwarding is misconfigured
- World chunk could not be read or saved
- World level.dat is damaged
- Crash while ticking an entity or block entity
- World is locked by another process
- Console command not recognised
- Mods are incompatible or missing dependencies
- A mod's Mixin failed to apply
- Client-only mod installed on the server
- Mod needs a newer Forge or NeoForge
Java 21
Memory limits, Java versions, startup flags and the exceptions that end up in a Minecraft or other Java server log.
- Java ran out of heap memory
- Java spent almost all its time collecting garbage
- Java ran out of Metaspace
- Java could not create a new thread
- Java ran out of direct (off-heap) memory
- Not enough memory to start the JVM
- JVM could not reserve the heap it was asked for
- Invalid Java heap size flag
- Needs a newer Java version
- Server jar file not found
- Main class could not be found
- JVM did not recognise an option
- The Java runtime itself crashed
- Stack overflow (endless recursion)
- A class the code needs is missing
- Plugin or mod built for a different version
- Java module system blocked reflective access
- Concurrent modification in plugin code
- Null pointer exception
- Long garbage collection pause (ms ms)
- A jar file is damaged or incomplete
Pterodactyl and Wings 10
The messages the panel and Wings print when a server stops, is killed or can't start.
- Server went over its disk space limit
- Automatic restart stopped: the server keeps crashing
- Wings detected that the server process crashed
- Container was killed for running out of memory
- Process was force-killed (exit code 137)
- Process crashed with a segmentation fault (exit code 139)
- Startup command not found (exit code 127)
- Startup file is not executable (exit code 126)
- Server stopped with exit code code
- Docker image could not be pulled
Steam, Source and other games 21
SteamCMD and srcds, Garry's Mod and SourceMod, Rust and Oxide, FiveM, Unity and BepInEx, Factorio, tModLoader and Unreal Engine servers.
- Steam API failed to initialise
- Game Server Login Token problem
- Could not connect to Steam
- Game server needs an update
- Source engine fatal error: message
- Map not found: map
- Lua error in an addon
- SourceMod plugin error
- Oxide/Carbon plugin failed to compile: plugin
- Plugin plugin failed in hook hook
- Null reference in mod or plugin code
- Unity could not load library library
- BepInEx mod error
- tModLoader mod failed to load
- Unreal Engine fatal error
- Factorio mods failed to load
- Save is from a newer Factorio version
- FiveM/RedM license key problem
- Resource resource failed to start
- Script error in a resource
- server.cfg could not be loaded
Node.js and Discord bots 17
Errors from Node.js apps, npm installs and discord.js bots running on a Pterodactyl egg.
- Node.js module 'module' not found
- require() used on an ES module
- import statement used in a CommonJS file
- Node.js ran out of heap memory
- Unhandled promise rejection crashed the app
- JavaScript syntax error
- Package requires a different Node.js version
- package.json not found
- npm install failed (code)
- Native module failed to build
- Discord bot token is invalid
- Bot uses privileged intents that are not enabled
- Bot is missing Discord permissions
- Rate limited by an API
- Discord bot replied to an interaction too late
- Discord bot replied to the same interaction twice
- Node.js is too old for fetch()
Python 8
Errors from Python bots and apps, pip installs and asyncio, as they appear in a server console.
Databases and services 9
When a plugin, bot or app can't reach its database or runs out of connections.
- Database refused the login for 'user'
- Could not reach the database server
- Database 'database' does not exist
- Database connection limit reached
- Database connection pool failure
- SQLite database is locked
- Could not connect to Redis
- Could not connect to MongoDB
- MySQL refused the login method ('Public Key Retrieval is not allowed')
System and container 19
Ports, disks, permissions, missing libraries and network problems inside the server's container.
- Port port is already in use
- No space left on the disk
- Permission denied while accessing a file
- Binary was built for a different CPU architecture
- Command 'cmd' was not found
- Script has Windows line endings
- Too many open files
- Native crash (segmentation fault)
- CPU does not support an instruction the server needs
- Process was killed by the system
- Docker image has an older C library than the binary needs
- Missing shared library library
- DNS lookup failed
- Connection refused
- Network connection timed out
- Connection was reset by the other side
- TLS/SSL certificate could not be verified
- Memory allocation failed
- Required file not found
Let it read the console for you.
Cardinal Review Lite checks every server on your Pterodactyl 2.0 panel against these rules and tells you the moment one matches. It's free.