Command Palette

Search for a command to run...

Your license key

What the .key file is, where it lives and how to keep it safe.

Your server proves who it is to the AstroShield backend with a license key. The key lives in a file named .key inside the AstroShield resource folder.

What it is#

  • It is a signed token that identifies your license. It is generated for you every time you download the resource, and it is placed in the ZIP for you.
  • The resource reads it when it starts and sends it to the backend. If it is missing the console says No license key found (.key file).
  • Next to it, .version holds the version of the resource that is installed.

You never type the key anywhere. It travels inside the ZIP.

Keep it private#

Treat the key like a password

Anyone who has your .key can try to connect to AstroShield as your server. Sharing a license key is also against the Terms and Conditions.

  • Do not post the AstroShield folder, a screenshot of it or the key in Discord, GitHub, forums or support tickets.
  • Do not commit the resource folder to a public repository. Add .key to your .gitignore if you keep your server in Git.
  • When you ask for help, share console output instead. It never contains the key.
  • The IP lock limits what a leaked key can do, because the license only works from your server's IP. It is a safety net, not a reason to be careless.

One key, one connection#

A license allows one live connection. If a second server starts with the same key while the first is still connected, the second one is refused with Already Connected. This is why you cannot share a license between a live and a test server.

Replacing a key#

Download the resource again from the dashboard. The new ZIP contains a key for the same license, so you can overwrite the old files. If you think a key has leaked, contact support on Discord or at astroshield@gmail.com.

Common problems#

Console messageCauseFix
No license key found (.key file)The file is missing, empty or in the wrong folder.Make sure resources/AstroShield/.key exists. Upload hidden files, or download the resource again.
Auth failed: Invalid TokenThe file was edited, truncated or corrupted.Download the resource again and replace the file.
Auth failed: Already ConnectedThe same key is already connected from another server or an old instance.Stop the other instance. After a crash, wait a minute and restart AstroShield.