If you are moving n8n from Server A to Server B and using the same database, you will likely see this error. The database "remembers" the activation from Server A, but Server B has a different machine fingerprint.
Once the request returns a success message, restart your n8n instance. activation key has already been used on this instance n8n
The cleanest way to resolve this without breaking your database is to inform the n8n API that you intend to re-register. If you are moving n8n from Server A
If you are spinning up and tearing down instances frequently (e.g., for testing workflows locally) and reusing the same license key, n8n's licensing server might rate-limit your activations. The cleanest way to resolve this without breaking
At its core, this error signals a fundamental mismatch between a software license and its intended host. An activation key in n8n functions as a unique digital credential. When a user purchases a license for self-hosted n8n, the key is designed to bind to a single —identified typically by a combination of the server’s hostname, IP address, or a unique installation ID. The phrase "has already been used on this instance" is paradoxical but precise. It indicates that the key’s cryptographic signature or stored activation record shows prior successful activation on the exact same system. The system refuses to activate again because it detects that the license is already active, preventing duplication or misuse.
The error message "Activation key has already been used on this instance" in n8n indicates that the activation key provided for the instance has been previously used. This report aims to provide an overview of the issue, possible causes, and recommended actions.
The n8n license server tracks activations based on a unique or "fingerprint" generated when you first install n8n. Common causes for this error include: