Reference
Statuses and errors reference
Every status badge, license plan state, license lock message, endpoint and extension status, and the error codes and messages a person can meet, each with what it means and what to do.
Covers YuviRed 1.0 for Windows (agent 1.8.2, extension 0.5.5). Messages are quoted as the product shows them, in the product's US spelling "license".
1. License plan states
The license panel (Configuration, License) and the license screen show the plan state of this server. The server computes it from the active license, its dates and this server's installation ID.
| Plan state | Badge in the console | Meaning | What to do |
|---|---|---|---|
grace | Not activated (amber); the panel line "You have N days left to activate this server. After that, the console is unavailable until the server is activated." and a banner: "This YuviRed server is not activated. You have N days left to activate it. After that, the console is unavailable until it is activated." (Activate now). The count reads "1 day" and then "less than 1 day". | A new server inside its 7-day activation window, counted from its first start. The console works with Lite limits (10 computers, 5 AI agents). | Activate the server within the window (activation code or license file). The day count is rounded down, so the banner may say 6 days right after install. |
not_activated | Not activated (red) | The 7 days ended with no activation. The console answers HTTP 402 license_activation_required (see section 2). | Activate the server. Enrolled computers keep reporting; YuviRed only monitors until then. |
active | Active (green) | A valid license is in force. For Lite: "YuviRed Lite is free and never expires." For Pro or Enterprise: "This license ends on <date>. When it ends, the console is unavailable until a new license is activated. There is no grace period." | Nothing. |
expiring | Ends soon (amber) | A Pro or Enterprise license ends within 30 days. A banner appears at 30, 14 and 7 days: "Your YuviRed Pro license ends in N days (date)... To renew, email support@yuvired.com." (the License link opens the license screen). | Renew before the end date at https://yuvired.com/request. The console keeps working until the end date. |
expired | Expired (red) | A Pro or Enterprise license has ended. Console is locked (license_expired). There is no grace after expiry. Lite has no expiry, so Lite never reaches this state. | Activate a new license. |
revoked | Revoked (red) | The license was revoked. For Lite only YuviRed can revoke, at the daily check-in. The lock text says who revoked it. | Email support@yuvired.com if you think it is a mistake; otherwise activate a new license. |
invalid | Not valid (red) | The license cannot be verified on this server (for example it is bound to another server, or its signature fails). Paid plans lock the console. Lite does not lock but refuses new computers: "This license is not valid on this server, so new computers are refused. Activate a new license, or email support@yuvired.com with this server's installation ID." | Activate a license bound to this server's installation ID. |
server_changed | Server changed (red); the panel heading reads "Needs a new license" and the license screen's title "This server needs a new license" | This server's hardware identity changed (a copy, a restore on new hardware, or a virtual hardware change), so YuviRed treats it as a copy of another server. | Email support@yuvired.com with the installation ID shown on the license screen. The old license does not work again by itself, even if you move back. |
legacy | an amber badge showing the word legacy (the console has no plain-language label for it) | A license that is not a Lite, Pro or Enterprise plan (an older tier). It keeps its earlier behavior and does not lock the console. | Not expected on a new install. |
unlicensed | an amber badge showing the word unlicensed | Reported only by a server that is not in license mode. Not expected on a YuviRed install. | None. |
Next to the badge the panel shows a heading: "Not activated" (grace and not activated), "YuviRed Lite", "YuviRed Pro" or "YuviRed Enterprise" (the plan in force), "YuviRed Lite (team build)" (a test entitlement, not a signed license), or "Needs a new license". Other labels you may see: the Computers used and AI agents used counters show "N / limit"; a counter turns red when usage is above the limit. A line "Every computer seat is in use. A new computer is refused until one is free..." appears when no seat is free. If the panel cannot load every detail it says "Could not load all license details. Choose Reload."
2. License lock messages (HTTP 402)
While the server is locked every console request answers HTTP 402 with a code and a message, and the console opens the license screen. Only sign-in and the account routes, the license routes, first-run setup and the roll-back of a response action keep working. Enrolled computers keep reporting. While locked, the browser extension gets the Monitor Only policy, which never blocks, and no new blocking action reaches a computer. Blocks applied earlier stay until rolled back (the roll-back route is the one exception to the lock, so an administrator can lift them).
| Lock code | Message shown | Screen title | What to do |
|---|---|---|---|
license_activation_required | "This YuviRed server is not activated. The 7 days to activate it have ended, so the console is unavailable until you activate it. Enrolled computers keep reporting, and YuviRed only monitors until then." | Activate YuviRed | Activate with a code or license file. |
license_server_changed | "This server's hardware changed, so YuviRed treats it as a copy of another server. The console is unavailable until a new license is activated for this server. Enrolled computers keep reporting, and YuviRed only monitors until then. If you moved or restored this server, email support@yuvired.com with the installation ID shown on this screen." | This server needs a new license | Email support with the installation ID. |
license_expired | "This YuviRed license has expired. The console is unavailable until a new license is activated. Enrolled computers keep reporting, and YuviRed only monitors until then." | Your YuviRed license has expired | Renew at https://yuvired.com/request and activate. |
license_revoked (by YuviRed) | "YuviRed revoked the license for this server. The console is unavailable until a new license is activated. Enrolled computers keep reporting, and YuviRed only monitors until then." | This YuviRed license was revoked | "If you think this is a mistake, email support@yuvired.com." |
license_revoked (on this server) | "This YuviRed license was revoked on this server. The console is unavailable until a new license is activated. Enrolled computers keep reporting, and YuviRed only monitors until then." | This YuviRed license was revoked | Activate a new license. |
license_invalid | "This YuviRed license could not be verified. The console is unavailable until a valid license is activated." | This YuviRed license could not be verified | Activate a valid license. |
Notes: the lock is decided by the server, not by the screen. A locked server's Add Computer shows no free seats. A revoked license cannot be activated again. The screen title during the 7-day window (opened from the banner) is also "Activate YuviRed".
3. Activation messages (license screen)
The license screen sends the activation code, this server's installation ID, computer name, Windows version and YuviRed version to https://activate.yuvired.com. A code is valid for 7 days and activates one server, once. The console shows the service's message and, for refusals that need a person, a "contact YuviRed" link. Every refusal also shows: "Need help? Email support@yuvired.com and include the installation ID."
Shown by this server
| Code | Message | HTTP | What to do |
|---|---|---|---|
invalid_code (empty) | "Enter the activation code." | 400 | Type the code. |
activation_unreachable | "YuviRed could not be reached. Check this server's internet access and try again, or use a license file." | 502 | Check internet access and the firewall, or use the license file route. |
activation_not_configured | "Online activation is not set up on this server. Use a license file instead." | 409 | Use the license file. |
activation_bad_response | "YuviRed sent an unexpected answer. Try again in a few minutes." | 502 | Retry later. |
activation_refused | "YuviRed did not accept this activation code." | 400 | Shown when the service refused without naming a reason. Check the code; request a new one. |
| (service fault) | "YuviRed could not activate this server right now. Try again in a few minutes." | 502 | Retry later. |
license_server_check_incomplete | "YuviRed could not finish checking this server's hardware. Restart the YuviRed service, then try again." | 409 | Restart the service, then retry. |
| other license refusals | license rejected: <reason> | 400 | See the reasons below. |
| permission | "Missing required permission: license.manage" | 403 | Sign in with the first (owner) account. |
Reasons after license rejected:
"empty license"; "unrecognized license format"; "malformed license encoding"; "malformed license payload"; "license signature verification failed"; "license is bound to a different appliance installation" (the license is for another server: request one for this installation ID); "this license has already expired"; "this YuviRed server takes a Lite, Pro or Enterprise license"; "a Lite license allows at most 10 computers"; "a Lite license allows at most 5 AI agents"; "a Lite license never expires, so it cannot carry an expiry date"; "a Pro or Enterprise license must have an expiry date"; "a plan license must be bound to one server (installation ID)"; "license serial ... has been revoked"; "this server has held a Pro or Enterprise license, so it does not take a free Lite license. Contact YuviRed to renew the paid license" (a server that was Pro or Enterprise cannot go back to free Lite).
License file errors
"the license file is empty"; "the license file is too large to be a YuviRed license" (limit 64 KB); "no YuviRed license was found in the file"; "the file holds more than one license". Console: "That file is too large to be a YuviRed license file."
Sent by the activation service
| Code | Message | HTTP | What to do |
|---|---|---|---|
invalid_code | "That activation code is not valid, was already used on another server, or has expired." | 400 | Check the code (valid 7 days, one server, one use). Request a new code. |
invalid_installation | "The server sent no valid installation ID." | 400 | Retry; contact support if it repeats. |
server_allowance_used | "Your company already has 2 YuviRed Lite servers. To add another server, contact YuviRed support and tell us why you need it." | 403 | Contact support. This is the per-company limit (see editions-and-limits.md). |
rate_limited | "Too many activation attempts. Try again in an hour." | 429 | Wait an hour. |
signer_unavailable | "Activation is temporarily unavailable. Try again later, or use a license file." | 503 | Retry or use a license file. |
too_large, bad_request | "The request is too large..." / "The request must be a JSON object." | 413 / 400 | Not expected from the console; contact support. |
When you ask for a Lite code on the website (https://yuvired.com), you may instead see: free_email_domain ("Use your work email address. Free email addresses cannot download YuviRed Lite..."), domain_not_allowed, email_allowance_used ("Two people at your company already use YuviRed Lite. To add another person, tell us why you need it..."), daily_limit_reached ("Your company has reached today's limit for YuviRed Lite downloads..."), invalid_verification ("That code is not right, or it has expired. Ask for a new one."), rate_limited_other ("Too many attempts. Try again in an hour."), email_unavailable. Each tells you to wait, use another address or contact support.
4. Endpoint states
Liveness (Endpoints page and Dashboard)
Derived by the server from the time of the computer's last check-in. Not stored.
| State | Rule | Meaning | What to do |
|---|---|---|---|
| Online | last check-in within 180 seconds | Reporting now. The agent checks in about every 60 seconds. | Nothing. |
| Stale | 181 to 600 seconds | A soft warning: a few check-ins missed. | Wait a few minutes. |
| Offline | more than 600 seconds, or never checked in | Not reporting. A rejected credential looks identical to a powered-off computer. | Check the computer is on and can reach the server; see endpoints.md. |
Freshness of AI activity
Live means the AI interaction was observed within 24 hours; Historical means older. This is separate from liveness.
Lifecycle
| Lifecycle | Holds a computer seat? | Meaning |
|---|---|---|
active | Yes | Enrolled and managed. |
quarantined | Yes | Temporarily isolated, still enrolled. |
decommissioned | No | Retired by an administrator. The computer is refused (HTTP 410) and cannot re-register with its old identity. |
archived | No | Retired. Same refusal. |
The server's own agent never uses a seat. A Windows Subsystem for Linux (WSL) distribution linked to its host computer shares the host's seat; a virtual machine or container with its own collector counts as its own computer.
Adoption requests
pending, approved, rejected, expired. Approving or rejecting a request already decided gives HTTP 409 "Request is already <status>".
AI agent (AMS) seat state
seated (counts against the AI agent limit), unseated (known only from a configuration or key file, no running process or connection seen, not counted), over_limit (detected above the limit; stays visible with its evidence, not counted).
AMS approval state
Unreviewed, Under review, Approved, Restricted, Unauthorized, Referred to AIDR. Amber badges mean awaiting a human decision.
5. Browser extension and prompt protection status
On Prompt Monitoring, each browser that has checked in shows a protection badge, a policy state and a version.
| Badge | Meaning | What to do |
|---|---|---|
| Protected (green) | Seen within 10 minutes, the user consented, the last policy pull worked, and the active policy is not Monitor Only. | Nothing. |
| Monitoring only (grey) | Same, but the active policy is Monitor Only: warnings and blocking are off. Prompts are still recorded. | Choose a stronger preset if you want warnings or blocks. |
| Stale (amber) | Not seen for more than 10 minutes. Only the absence of a report is known: "(no recent report; YuviRed cannot tell why)". | Check the browser is open and the computer reaches the server. |
| Protection unavailable (red) | The user has not consented, or the last policy pull failed (the reason is shown). | Fix the cause shown (consent, connection, certificate). |
| Policy state (shown as "policy applied", "policy pending", "policy stale" or "policy unknown") | Meaning |
|---|---|
applied | The browser runs the active policy revision. |
pending | The browser runs an older revision and will update. |
stale | Not fresh, so what it runs cannot be confirmed. |
unknown | No state was reported. |
A computer whose agent reports but whose browser has not yet appeared shows the amber label "No browser reporting yet" with the agent's own online or offline state. The card's count line reads "N protected, N monitoring only, N stale, N unavailable".
An update needed tag means the extension is older than the version on this server. On Lite, run a new Add Computer download on that computer, then restart the browser or choose Reload on the extension at chrome://extensions or edge://extensions. Extension lifecycle changes (Installed, Removed, Enabled, Disabled, Version change, Permission change, Manifest change) appear on the Endpoints page.
6. Alert, incident and action statuses
| Where | Values |
|---|---|
| Alert status | open, acknowledged, investigating, resolved, false_positive, suppressed (active ones: open, acknowledged, investigating) |
| Alert severity | critical, high, medium, low |
| Incident status | open, investigating, contained, resolved |
| Response (enforcement) action | pending (requested), approved, running, succeeded, failed, rejected, cancelled, rolled_back, expired (delivery deadline passed; nothing is delivered after it), recalled (an administrator stopped a running action) |
| Deployment campaign | draft, active, paused, completed, revoked, expired |
| Campaign delivery steps | package_delivered, agent_installed, service_running, enrolled, identity_established, native_host_registered, extension_installed, extension_healthy, policy_synced, first_checkin, fully_ready; exceptions pending_offline, failed |
| Artifact analysis | Pending, Running, Completed, Partial, Failed, Cancelled; provider status OK, Degraded, Down, Inactive |
7. First-run setup refusals
| Message (code) | HTTP | Meaning and action |
|---|---|---|
| "Full name is required" | 400 | Fill in the name. |
| "A valid email address is required" | 400 | Enter an address with an @ and a domain. |
| "Passwords do not match" | 400 | Retype both. |
| Password rule text (for example length 12, three character classes, common words, your own name) | 400 | Choose a stronger password; see roles-and-permissions.md. |
"You must accept the End User License Agreement and read the Monitoring and Data Notice" (eula_not_accepted) | 400 | Tick the acceptance box on the setup screen. For an unattended install, pass ACCEPT_EULA=1; without it the installer exits with code 5101. |
| "Setup has already been completed" | 409 | An administrator already exists. Sign in. |
| "That email address is already registered" | 409 | Use another address or sign in. |
| "Setup is only available from the computer YuviRed is installed on" | 403 | Open the setup page in a browser on the server computer itself. |
8. HTTP errors a person or an agent can meet
| HTTP | Where | Message | Meaning and action |
|---|---|---|---|
| 401 | Console | "Not authenticated"; "Invalid or expired token"; "User not found" | Sign in again (a session lasts 8 hours). |
| 401 | Sign-in | "Invalid credentials" | Wrong password, unknown or inactive user, or an expired temporary password. The three look the same on purpose. |
| 401 | MFA step | "Invalid or expired pre-auth token"; "Invalid code" | The 2-minute step ended; sign in again. Or the code was wrong. |
| 401 | Agent | "Invalid deployment token"; "Deployment token expired"; "X-Deploy-Token required"; "Not a campaign bootstrap credential" | The token or Add Computer download is wrong or old (an Add Computer download is valid for 24 hours). Make a new download. |
| 402 | Console | a license lock (section 2) | Activate the server. |
| 402 | Agent (enrolled computer) | a license stop | The agent logs it, backs off to 300 seconds, keeps its identity and resumes when the condition clears. |
| 403 | Console | "Missing required permission: <code>" | Your role lacks that permission; ask an administrator. |
| 403 | Console | password_change_required: "A password change is required before this account can be used. Change it via /auth/change-password." | Change your password. |
| 403 | Configuration | "Artifact Analysis configuration requires the artifact.manage permission." | Only an Admin can read or change the Artifact Analysis rows. |
| 400 | Configuration | "<key> is license state, not a configurable value..."; "<key> is the recorded acceptance of the End User License Agreement..."; "security.tls_enforcement must be one of: off, warn, enforce..."; "branding.privacy_contact must be at most 200 characters." and similar "must be" messages | The value is refused; the message names the rule. The first two are recorded in the audit log. |
| 404 | Configuration | "Unknown setting: <key>" | The key does not exist on this server version. |
| 403 | New computer enrolling | "license seat limit reached"; "license activation required"; "license revoked"; "license expired"; "license invalid"; "license server changed"; "server identity changed: an administrator must confirm it" | The computer is refused. See editions-and-limits.md. |
| 403 | Agent | "This credential is not authorized for that endpoint" | The credential does not match; the agent retries recovery with the credentials it holds. |
| 404 | Agent | "Endpoint not registered"; "Endpoint is not linked to a deployment campaign" | The computer is not enrolled (for example it was removed), or its installer reports progress for a campaign it does not belong to. Reinstall with a new Add Computer download. |
| 409 | Add Computer | "Only N computer seats are free."; "Every computer seat is in use. To free one, open Endpoints and remove a computer you no longer use. Removing it deletes that computer's history." | Free a seat or ask for fewer computers. |
| 409 | Add Computer | "Network mode is off, so other computers cannot reach this server..."; "The agent installer is not part of this server build."; "This server's certificate could not be read."; "This server's hardware identity changed. Confirm it before adding computers." | Fix the cause stated. |
| 409 | Configuration | "<key> is superseded by the Prompt Protection policy..." | Edit the policy under Configuration, Prompt Protection. |
| 409 | MFA | "MFA is already enabled; disable it first to re-enrol"; "MFA is not enabled"; "No enrolment in progress..." | Follow the message. |
| 409 | Campaign | "Campaign is '<status>'; no further progress reporting accepted"; "Cannot <action> a campaign in status '<status>'" | The campaign is not in a state that allows that action. |
| 410 | Agent | "This endpoint has been decommissioned by an administrator." | Retired computer; it stays refused. |
| 410 | Agent | "Campaign no longer exists" | Make a new Add Computer download. |
| 426 | Agent or extension | "Agent version X is no longer supported. Minimum required: Y..." | Update the agent (run a new Add Computer download). |
| 426 | Agent or extension | "Plaintext HTTP is not accepted for agent/extension endpoints..." | Point the agent at the HTTPS address; this appears only when Agent Connection Security is set to Require. |
| 429 | Sign-in, MFA | "Too many failed login attempts. Please wait and try again."; "Too many failed codes for this account. Retry in Ns." | Wait (8 failures per 5 minutes per address and account; 30 per hour per account). Signing in at the server itself is exempt from the per-account hour limit. |
| 429 | Agent | "Too many registration attempts; slow down"; "Too many rotation requests; slow down"; "Too many campaign report attempts; slow down" | Wait and retry. |
| 429 | Activation | "Too many activation attempts. Try again in an hour." | Wait an hour. |
9. License banners, buttons and toasts
| Text | Meaning |
|---|---|
| "License activated" | The license was accepted. |
| "Installation ID copied" / "Copy failed: select the installation ID and copy it by hand." | Result of the Copy button. |
| "The license was stored, but the console is still locked. Email support@yuvired.com." | The license is stored but does not unlock this server (for example it is for another installation ID). |
| "Activating sends YuviRed this server's installation ID, computer name, Windows version and YuviRed version." | The four facts the activation sends. After activation the server checks in once a day with six facts: format, installation ID, version, serial, computer count and AI agent count. No computer names, user names or prompts. |
| Update banner | A newer YuviRed exists. Nothing installs itself. |