Could not load 'plugins/…' (plugin failed to initialize)
On Paper/Spigot servers, a plugin that fails to initialize prints 'Could not load plugin …' with the reason on the following lines. The server usually keeps running without that plugin, but a hard dependency can also abort the whole boot. The named jar plus the reason line is the entire diagnosis.
Fastest path: paste your crash report into the Crash Doctor — it identifies this pattern and 40+ others automatically. No signup.
How to fix it
- 1
Read the reason line
Common reasons: Invalid plugin.yml, Unsupported API version, and NoClassDefFoundError for a missing dependency plugin. Each points at a different fix.
- 2
Match the plugin to your server version
Plugins are built per Minecraft and Paper version. A plugin for MC 1.20 on a 1.21 server fails to load. Download the build listed for your exact server version.
- 3
Install the required dependency plugins
Many plugins need a library plugin (Vault, PlaceholderAPI, ProtocolLib). The error names the missing class — the plugin's project page lists which dependency provides it.
- 4
Remove the broken jar
A 0-byte or interrupted download fails with Invalid plugin.yml. Delete it and redownload. Two copies of the same plugin (plugin name duplicates) also fail — keep one.
- 5
Restart and verify
After the fix, the boot log should list the plugin as enabled. Test its main command once — an enabled-but-broken plugin usually errors on first use.
Alternative causes
These can produce the same error message — worth ruling out if the steps above don't resolve it.
Java version mismatch for the plugin
Plugins compiled for newer Java throw UnsupportedClassVersionError at load. The fix is the same as for mods: run the Java the plugin was built for.
Trying to load mods as plugins
A Forge/Fabric mod jar dropped into plugins/ fails immediately. Mods belong to a mod loader; Paper servers take plugins only.
Frequently asked
Can a Paper server run Forge mods?
No. Plugins and mods are different systems. For hybrid setups there are limited bridge projects, but the reliable path is choosing one ecosystem per server.
Why does one broken plugin stop the whole server?
Plugins can declare hard dependencies on each other. If a critical one fails, everything depending on it aborts too — the boot chain refuses rather than run half-installed.
Where do I find which version a plugin supports?
The project page lists supported server versions per download. Modrinth and Hangar make this explicit; SpigotMC resources list it in the description.
Want this auto-fixed on your server?
CoalHosting's Minecraft hosting runs the same pattern database against every crash and applies the known fix before your players notice. Free crash diagnosis works on any server, hosted or not.
Related crashes
Bad config file (TOML / JSON parse error)
Fix Minecraft mod config parse errors — a config/*.toml or *.json got corrupted, manually edited wrong, or out…
Server exited with code 1
Exit code 1 means the JVM hit an unhandled error. The code itself says nothing — the real cause is in the log …
Duplicate mod found / mod id already present
Two jars claiming the same mod id — usually two versions of one mod — stop Forge or Fabric from loading. Keep …
Last reviewed 2026-09-06. If a step is wrong or out of date, tell us — we'll fix the article and the auto-pattern at the same time.