Oops... looks like the spiders padded through here
Add products to your cart and remove them from here Lets buy🪪 Licensing
On this page, you will find everything you need to know about activating your license and what to do when the validation fails.
Only the Premium version is licensed. The Lite version has no license and never contacts our servers.
#Your License Key
Every jar downloaded from our website is stamped with the license of the account that downloaded it, so in almost every case there is nothing for you to fill in. The key lives in config.yml under product-license.
product-license: 'your-license-key'
If you ever need to set it by hand, the key is on your account page on phoenixplugins.com. Paste it exactly as it appears, save the file and restart the server.
#What Happens on Startup
On every start the plugin prints Validating license... and contacts our servers. Once the check passes you will see:
Great news! Your license is valid and active.
Plugin loaded successfully!
The same check is renewed periodically while the server runs, so a license that is revoked mid-session is noticed without a restart.
The server needs outbound internet access to phoenixplugins.com. A permanently offline machine cannot run the Premium version.
#When Validation Fails
A failed validation does not disable the plugin. Placed crates keep working, but every PhoenixCrates command is blocked, and any player who runs one is told why. Fix the cause and restart to restore the plugin.
#"It appears that it does not exist for this product"
The key was not recognised for PhoenixCrates. Check for a typo, a stray space or a newline in product-license, and make sure the key belongs to this plugin rather than another one of ours.
#"Maximum concurrent sessions allowed reached"
The same license is already active on more servers than your plan allows. This is the usual one to hit on a network, where the plugin gets copied to several servers behind a proxy.
Stop the extra instances and restart. If you have a genuine reason to run more sessions at once, contact us on Discord and we can raise the limit for your account.
A server that crashes without shutting down cleanly can leave a session registered for a short while. If you are certain nothing else is running, wait a few minutes and start again before contacting us.
#"HttpResponseCode: 429"
Our API answered with a rate limit. This is not a problem with your key: too many validation requests arrived from your license in a short window.
The usual causes are a server that is restarting in a loop, a start script that keeps relaunching after a crash, or a whole network of servers booting at the same moment with the same key. Each start sends one validation request, so a restart loop turns into a burst very quickly.
Stop the server, leave it down for a few minutes, then start it once and let it finish booting. The limit clears on its own. If the plugin cannot reach us it retries every 5 minutes, so leaving a rate limited server running keeps the requests coming — shut it down rather than letting it retry.
#Other "HttpResponseCode" numbers
Any other number in that message is the raw reply from our API and points at the connection rather than your license.
| Code | What it usually means |
|---|---|
| 403 | The request was refused. Usually a host, firewall or proxy in front of the connection rather than us. |
| 404 | The endpoint could not be found. Almost always a very old build — update the plugin. |
| 5xx | Our side is having a problem. Wait for the grace period message and try again later. |
#"connect timed out" or "UnknownHostException"
The server never reached api.phoenixplugins.com. Check that outbound HTTPS is allowed and that the host is not blocking or filtering the domain. Shared and budget hosts sometimes block outbound connections by default and need a support ticket to open them.
#"Authentication expiration time already expired. Is your clock with right time?"
The machine's clock is wrong. The validation reply carries an expiry timestamp, and if your system time is far enough behind or ahead it looks already expired. Sync the server clock with NTP and restart.
#"Signature is invalid."
The cached validation file in plugins/PhoenixPlugins is corrupt or was edited. Delete the *_auth.json file in that folder and restart with a working connection.
#Grace Period
If our servers cannot be reached at all — your host blocks the connection, or we are down for maintenance — the plugin does not shut you out. A grace period is activated and the console tells you how long is left:
Oh no! Apparently there was an error contacting our server.
But don't worry, the grace period has been activated.
Grace period will expire in 23h 41m, so contact us before that happens!
Everything keeps working normally until the grace period expires. If you see this message and your server does have internet access, check your firewall before contacting us.
#Version Notices
The same check tells the plugin which version is current, so the console reports whether a newer build is available. Players holding phoenixcrates.admin are also told on join, which can be turned off with notify-if-new-version in config.yml.