You deleted your database or recreated your Docker container without persisting the .n8n directory, leading n8n to think it’s a new instance even if it's the same server.
If you are setting up a self-hosted n8n instance or migrating a license to a new server, encountering the error can be a significant roadblock.
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. activation key has already been used on this instance n8n
Several practical scenarios give rise to this error. The most common is . A user might rebuild their n8n Docker container, migrate to a new server with the same hostname, or restore a backup to fresh hardware. From the software’s perspective, the underlying instance identifier may have changed or the previous activation token was not preserved. Consequently, when the user re-enters the same key, the licensing server recognizes the key as already bound to an existing record. Another scenario involves hardware or network changes , such as modifying the server’s MAC address or hostname, which can alter the instance fingerprint. Finally, simple user error—like attempting to activate two separate n8n deployments with one single-use key—will also trigger the message.
The licensing server still has a record of that key being tied to your specific instance ID from a previous attempt. You deleted your database or recreated your Docker
The key was actually accepted on your first try, but a UI glitch or a lack of refresh makes it look like it failed.
You need to send a request to the license endpoint of your new n8n instance. The database "remembers" the activation from Server A,
Running two containers pointing to the same data directory or trying to use the same key on a second, separate installation. Step 1: Verify Current Registration Status
Resolution typically requires administrative intervention. The user must verify that they are not genuinely running two instances. If not, they need to locate the original activation file (often stored in the database or .n8n folder) and restore it, or request a license reset from n8n’s customer support. This reveals a key lesson: activation keys are not just strings—they are stateful contracts between user and vendor. Treating them as disposable passwords leads to this digital impasse.