Activation Key Has Already Been Used On This Instance N8n

Once the request returns a success message, restart your n8n instance.

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. activation key has already been used on this instance n8n

In conclusion, the error "Activation key has already been used on this instance" is a sentinel of modern license management. It protects n8n from unauthorized reuse while occasionally trapping legitimate users in a logical loop. Understanding its cause—rooted in instance identity and activation state—turns a frustrating message into a manageable data point. For developers and operations teams, the error serves as a reminder that in self-hosted software, even automation tools require careful stewardship of their own activation metadata. Once the request returns a success message, restart

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 not, they need to locate the original

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.

To understand the fix, you first need to understand how n8n handles licensing: