Plugin crashed while enabling (Error occurred while enabling)
- Platforms
- Paper · Purpur · single server
- Verified
- Verified
- Confidence
- Confidence 90%
What it looks like in the log
Any one of these lines is enough. The agent matches them locally, on your server.
logs/latest.log
[ERROR] while enabling
Symptoms
- The plugin is loaded but disabled (red in /plugins); its commands and features do not work
- In the log: “Error occurred while enabling <plugin> (Is it up to date?)” and a stack trace
Cause
The plugin's onEnable method threw an exception and Paper disabled the plugin. The stack trace (Caused by) shows the specific reason: version incompatibility, an unreachable database, a broken config.
Possible causes
- The plugin version is incompatible with the server version (NoSuchMethodError/NoClassDefFoundError in the trace)
- An external resource is unavailable: database, web API, port (SQLException/ConnectException in the trace)
- An error in the plugin config (YAML/a value of the wrong type in the trace)
- A plugin bug or a conflict with another plugin
How to fixLow risk
- Read the first line of the exception and the last
Caused by:line in the evidence — that is the real cause. NoSuchMethodError/NoClassDefFoundError/ClassNotFoundException— update the plugin to a version that supports your server version.- Database/network connection errors — check the address, port and service availability in the plugin config.
- YAML/config errors — fix the indicated file in
plugins/<plugin>/(or keep a copy and let the plugin regenerate the config). - Restart the server (not
/reload); if the error persists, report it to the plugin author with the full trace.
Translated from the Russian original; log lines are quoted verbatim.