Activation problems
Key rejected, seat conflicts, offline files that won't take — the failure modes and their fixes.
Activation failures are deliberately specific — the Status readout names
the exact refusal. Find yours below.
Three causes, in frequency order: a typo (keys are
NOP-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX — 36 characters after the
prefix, so the dashboard's copy button beats retyping), a key for a different plugin (keys are plugin-scoped), or a
revoked key after a refund. The dashboard shows each
key's plugin and state.
The seat is active elsewhere — possibly a dead machine that never got the chance to deactivate. Free it from the dashboard (Seats → Deactivate); the change is immediate, no support ticket needed.
The seat.license was issued for different hardware. Regenerate the
machine.request on the machine as it is now and reissue — this hits
people who swapped a GPU, and farm operators who cloned an image with a
request file baked in.
Offline licenses carry a signed timestamp. Air-gapped machines drift; more than 48 hours breaks validation. Set the clock (GPS/NTP appliance on show networks), regenerate, reissue.
The machine can't reach the licensing endpoint. Corporate TLS
inspection is the usual culprit — ask IT to exempt
licensing.nativeops.tools, or use
offline activation,
which exists for exactly this network.
None of it matching? Contact support with the Info DAT diagnostics dump (right-click the operator → Copy Diagnostics) — it includes the last ten status transitions, which is usually the answer.