Luarmor error codes: what each one means
Every official Luarmor status code, the layer it belongs to, and what to do first. The message changes; the code string stays the same.
A Luarmor code is a short status from the licence check, not a description of your script. It names the layer that failed: the key, the script ID, the client that sent the request, or the service behind it. Read the code before the message, because the message is prose and the code is what the seller can act on.
How to read a code
The key check library returns a table with code,
message and, on success, data. The code is a fixed
string such as KEY_EXPIRED. The message is a sentence meant for a
human. A protected script can print its own text or kick with it, so the same
failure can look different in two scripts.
Sort the code by the layer it comes from. That decides who can fix it.
| Layer | Codes | Question it answers |
|---|---|---|
| Key |
KEY_VALID, KEY_EXPIRED,
KEY_BANNED, KEY_HWID_LOCKED,
KEY_INCORRECT, KEY_INVALID
|
Is this key usable on this device and this project? |
| Project | SCRIPT_ID_INCORRECT, SCRIPT_ID_INVALID |
Does the script the loader names exist? |
| Client | INVALID_EXECUTOR, SECURITY_ERROR, TIME_ERROR |
Can the service trust and identify the request? |
| Service | UNKNOWN_ERROR |
Did the request reach a working backend? |
The response reports one condition. A second problem can appear after the first is fixed, so the code only describes the moment when you asked.
Where the code appears
The library returns the code in a table. A script can print the table, show
status.message in an interface, or kick with a custom sentence. The
protected build that Luarmor generates already includes a whitelist check, so many
users never see the raw table. They see the script's rendering of it.
If you have the Lua console, print the whole table. code is the
stable field. message is documentation text that can be reworded
between builds. In a ticket, the code plus the message is better than either one
alone.
The seller's dashboard records executions and key states, but it does not necessarily show the exact code the client received. Ask the seller to compare the key record at the time you tried, because the record can change after a reset or a renewal.
Key codes
These six codes come from the key check. Five are failures and one is the success state.
KEY_VALID
The documentation says the key has no HWID assigned, which is the reset state, or
the assigned HWID matches the client and the key is not expired. On this code the
response also carries auth_expire, note and
total_executions. A value of -1 or 0 in
auth_expire means a lifetime key.
KEY_VALID means the licence layer passed. It does not promise that
the script will run, because the script can still stop on its own checks or on a
game update.
KEY_EXPIRED
The key is valid, the HWID matches, and the expiry date has passed. The key is not deleted. Renewal depends on the seller: some sell an extension, some send users through an ad page for extra time. The options are in Luarmor key expired.
An expired response does not carry the data field, so you cannot read
the old expiry from the error. If you noted auth_expire on an earlier
valid check, compare that value with the current time. A lifetime key that reports
expiry is worth raising with the seller, because auth_expire should
have been -1 or 0.
KEY_BANNED
The key is valid, the HWID matches, and the key is blacklisted. The documentation is explicit that the reason is not exposed through the library. You cannot read the cause from the code, and no local step lifts the block. Only the seller can see the reason and reverse it. How keys reach that state is in Luarmor blacklist.
KEY_HWID_LOCKED
The key is valid but its hardware link points at a different machine. The documented fix is a reset through the bot panel or the ad page, not a new key. A fresh key is unclaimed until its first check, which is why a key can work once and then lock to that first machine. What counts as a different device is in Luarmor HWID locked.
KEY_INCORRECT
The format looks right, but the key is not in the database. It may have been deleted, or it may never have been generated. The usual causes are a key from another project, a project that was deleted and recreated, or a character copied wrong in a way that still looks like a 32-character key.
A recreated project has a new ID and a new key space. An old key can look correct, pass the length test and still return this code, because the record it pointed at no longer exists.
KEY_INVALID
The key is empty, too long or too short. The documentation calls it an invalid format and its key check example passes a 32-character key. It does not publish an alphabet, so a copied string with the wrong characters can still look valid. A trailing space or a line break is enough to fail this check before any lookup happens.
Copy the key from the original message rather than from a screenshot or a chat preview. A wrapped line can add a break in the middle, and a prefix such as a quote can add a character that the check counts.
Project codes
The project layer asks whether the script ID in the loader exists. It runs before any judgement about the key.
SCRIPT_ID_INCORRECT
The script ID does not exist, or it was deleted after the loader was issued. The loader URL carries the ID, so an old loader can point at a project that no longer exists even when the key is fine. For how a loader and a key get out of step, see Script ID incorrect.
SCRIPT_ID_INVALID
The ID is the wrong shape: too short, too long, or containing characters that are not hexadecimal. This is a format error, not a missing project. It usually comes from an edited URL or a copy that lost characters. The service never looks the ID up.
Client codes
All three are about the request, not about the key, and they arrive at the same point in the flow, which makes them easy to read as a ban.
INVALID_EXECUTOR
The documentation says the HWID header contains invalid data and adds that the executor might not be supported. This is the code behind the kick message about an unsupported executor. The key is not read on this branch. What the service checks is in Executor not supported by Luarmor.
SECURITY_ERROR
The request could not be validated by Cloudflare, and the documentation gives the meaning as a signature mismatch. The licence has not been judged. A client that rewrites headers, an edited loader or a proxy can produce it. The causes, in order, are in Luarmor security error.
TIME_ERROR
The client time is invalid. The documentation gives two causes: the request took
too long to complete, or os.time() is broken. The timestamp is one of
the values the service checks, so a wrong clock fails the request before the key is
considered. The fix is in
Luarmor time error.
Service codes and the catch-all
UNKNOWN_ERROR
The documentation calls this an unknown server error and points to the support server. Its stated meaning is an upstream connection that closed, from an outage or an API restart. Unlike the three client codes, this one can affect every user at once. Retry after a pause and compare with other users before changing anything local. How to make that comparison is in Luarmor status and outages.
Full table
| Code | Layer | What it reports | First action |
|---|---|---|---|
KEY_VALID |
Key | Key usable here, with data attached | Run the script |
KEY_EXPIRED |
Key | Expiry date passed | Renew with the seller |
KEY_BANNED |
Key | Blacklisted, reason not exposed | Ask the seller |
KEY_HWID_LOCKED |
Key | Bound to another HWID | Reset the HWID |
KEY_INCORRECT |
Key | Not in the database | Check the project and the copy |
KEY_INVALID |
Key | Empty or wrong length | Recopy the full key |
SCRIPT_ID_INCORRECT |
Project | Script ID missing or deleted | Get a fresh loader |
SCRIPT_ID_INVALID |
Project | Script ID malformed | Re-copy the loader URL |
INVALID_EXECUTOR |
Client | Invalid HWID header, client not recognised | Update or change the client |
SECURITY_ERROR |
Client | Signature does not match | Re-copy the loader, clear the proxy |
TIME_ERROR |
Client | Clock or request timing is wrong | Set the clock to automatic |
UNKNOWN_ERROR |
Service | Upstream connection closed | Wait and retry |
What to send the seller
Send the exact code string, not a paraphrase. Add the message as it appeared, the time with your timezone, the executor name and version, the script name, and what you changed before the failure. Say whether the code appears on the first run or after a reset, because that changes which state the key moved through.
Put the key in the ticket, not in a public channel. The seller needs the key to look up its record, and a public post exposes it to everyone reading. If the seller asks for a screenshot, include the console line with the code. A screenshot of a kick message alone can be the script's own text.
Why the same key returns a different code
Key states change. A reset clears a hardware lock, a renewal clears an expiry, a seller can lift a blacklist, and a project can be recreated with a new ID. Each change produces a new answer from the same key.
The opposite is also true: if nothing changes, the same key should return the same code. A code that flips between two values without any action points at the request path or at two different clients, not at the key record. Server-side state does not usually alternate on its own.
FAQ
What is the most common Luarmor error?
No published count exists. The threads we read lean towards key states and client rejections, but that is not a ranking. The code tells you which layer failed, and that is faster than guessing from the message. Start with the code, then read the section for that layer.
Is every red code a ban?
No. The documentation colours several failures red in its table, including KEY_INCORRECT and KEY_INVALID. Only KEY_BANNED reports a blacklist. A red cell is presentation, not a verdict. Read the code string, because the colour does not travel with the response.
Why do I get SECURITY_ERROR only on one executor?
That pattern points at the client. One client can rewrite or normalise request headers in a way another does not, and the signature no longer matches. Try the same loader on a second client. If the code disappears, the first client is the cause, not the key or the service.
What does UNKNOWN_ERROR mean?
It means the service could not complete the check and the connection closed upstream. The documentation names an outage or an API restart. Retry after a pause. If other users report the same code at the same time, wait for the service. If you are the only one, check your network before anything else.
What does TIME_ERROR have to do with my clock?
The request carries a timestamp, and the service checks it. If the device clock is wrong, or the request takes too long between signing and arrival, the timestamp falls outside the accepted window. The exact tolerance is not published. Set the clock to automatic and retry before changing the key.
Can an error code tell me if my key is banned?
Only KEY_BANNED reports a blacklist, and the reason is not exposed through the library. Other codes can appear on a key that is also banned, because the check reports one condition at a time. If you need the reason, the seller has to look it up on the project dashboard.
Where is the official list of codes?
The key check section of Luarmor's user manual lists the codes and their messages. We checked that page on 19 October 2026. Codes can be added or reworded, so compare the list with the code you actually received rather than assuming an old screenshot is current.
Does KEY_VALID mean the script will run?
No. It means the licence check passed. The script still has to load, the game still has to accept it, and the executor still has to support the functions the script calls. A valid key with a broken script produces no Luarmor code at all, which is why the console matters.
Why does my script show a different message for the same code?
Scripts can wrap the code in their own text, translate it, or kick with a custom sentence. The code string is the stable part. If you only have the message, search the exact words, but treat the code as the source. Ask the seller which code their build prints for that message.