Troubleshooting

The problems you are most likely to hit, and what to do about them.

The plugin will not load

UnsupportedClassVersionError, or the jar is silently skipped. EcoHub needs Java 25 or newer. It will not load on Java 21. Check with java -version and upgrade the JVM your server runs on.

Old server version. EcoHub targets Spigot or Paper 1.21.8 or newer.

"That does not look like an EcoHub code"

Codes are 8 characters, letters and numbers, with no I, O, 0, or 1 in the alphabet. If you have typed a letter O where a zero was meant, or vice versa, that is the usual cause. Hyphens, underscores, and spaces are ignored, so the shape of the code does not matter, only the characters.

This check runs locally, so a rejected code never reaches EcoHub. Copy the code again from hub.auxilor.io/link.

"This server is already linked"

Run /ecohub unlink first, confirm within 10 seconds, then link again.

"EcoHub accepted the code but sent an incomplete response"

The code was valid but the response could not be read. Run /ecohub link <code> again with a fresh code. If it keeps happening, set debug: true in config.yml, restart, and send the console output to support. API keys are redacted from debug output.

Updates say they are installed, but the plugin version has not changed

Updates are staged into plugins/update/ and applied by Bukkit at the next startup. A running plugin is never modified in place. Restart the server.

If a restart did not apply them, check that plugins/update/ exists, that the server process can write to it, and that no other update manager is emptying it.

A download was rejected

Downloads are checked against the SHA-256 hash EcoHub sent, and then checked to make sure the file is really a plugin jar. If either check fails, the file is thrown away and nothing is installed. This is almost always a truncated or proxied download. Run /ecohub check again.

A plugin is not being updated

Run /ecohub check and read the console output. EcoHub lists plugins it does not manage as unmanaged.

A plugin is unmanaged if its jar has no platform marker file inside it, which means it did not come from the Eco suite. EcoHub never downloads, replaces, or removes an unmanaged jar.

If an Eco plugin is listed as unmanaged, it was probably built from source or repackaged. Reinstall it from a published build.

If it is managed but has no update available, your account may not own that resource.

The filename looks wrong after an update

If a new build has a different filename to the one you had — for example EcoCrates-2026.29-polymart.jar being replaced — EcoHub writes a small helper jar that renames the file on the next boot and then deletes itself.

This is cosmetic and resolves on its own after one restart. The contents of the jar are already correct either way.

A plugin was deleted from my server

This happens when EcoHub reports a paid resource as revoked, which follows a chargeback ban on the account. Free plugins are never removed. See How Updates Work.

Deletion only ever happens on an explicit revocation in a response that came back cleanly. A server that cannot reach EcoHub, or that gets a timeout or an error, never deletes anything.

check-interval-minutes was N; clamped to 30

The minimum check interval is 30 minutes. Set a value of 30 or higher to clear the warning.

Getting more detail

debug: true

Restart the server. Request and response details are printed to the console, with API keys redacted. Turn it back off when you are done.

Where to go next

  • Setup steps: Getting Started.

  • Config reference: Plugin Config.

  • Commands: Commands and Permissions.