N8n Activation Key Has Already Been Used On This Instance -

Docker Compose configuration to ensure your instance ID remains persistent across restarts? AI can make mistakes, so double-check responses Copy Creating a public link... You can now share this thread with others Good response Bad response 6 sites "Activation key has already been used on this instance ... Jul 16, 2025 —

I understand you’re looking for a review or troubleshooting guide regarding the error message: “n8n activation key has already been used on this instance.” Below is a full, structured review of what this error means, why it occurs, and how to resolve it.

1. What Does This Error Mean? This message appears in n8n (a workflow automation tool) when you try to activate a paid license key (e.g., for n8n’s enterprise features) on a specific server instance, but that same key has already been activated on another instance. n8n ties license keys to instance identifiers (like a machine ID or installation hash) to prevent one key from being used on multiple servers simultaneously.

2. Common Causes | Cause | Explanation | |-------|-------------| | Reinstalling n8n | You reinstalled n8n on the same machine, but the instance ID changed. | | Cloning or moving instances | You copied your n8n setup to a new server without deactivating the key first. | | Multiple containers/processes | Running two separate n8n containers with the same license key on the same host. | | Manual key reuse | You entered the same key into a different installation. | | Corrupt database | The license activation record was lost or corrupted, forcing a reactivation. | n8n activation key has already been used on this instance

3. Official n8n Behavior

Per‑instance binding – The license key is locked to the first instance it’s activated on. No automatic deactivation – You must explicitly deactivate the key from the original instance before using it elsewhere. Enterprise feature check – If the key is already used, n8n will fall back to the Community Edition (no enterprise features).

4. How to Fix It (Step by Step) ✅ Step 1: Identify where the key is currently active Docker Compose configuration to ensure your instance ID

Check all n8n instances (prod, staging, backup) where you may have entered the key. Look for the original installation where activation first succeeded.

✅ Step 2: Deactivate the key from the original instance If you still have access to that instance:

Log into n8n as an owner. Go to Settings → License . Click Deactivate license . Confirm deactivation. Jul 16, 2025 — I understand you’re looking

Now the key is free to use on another instance. ✅ Step 3: Reactivate on your desired instance

Go to Settings → License on the new instance. Enter the same activation key. Click Activate .