You have two options:
| Cause | Explanation | |-------|-------------| | | 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. |
When setting up or migrating a self-hosted n8n instance, you may encounter the following error message: n8n activation key has already been used on this instance
| Aspect | Rating / Notes | |--------|----------------| | | Good – it directly states the key is already used. | | Ease of resolution | Medium – requires access to original instance or support. | | Prevention | Easy – just deactivate before moving. | | Support availability | Good – n8n team can reset keys upon request. | | Overall impact | Low – only blocks enterprise features, not basic automation. |
You generally do not need to enter the activation key string every time you restart n8n. If you see this error, stop trying to re-paste the key. Instead, navigate to the License tab in Settings and select the option to or Sync your license, ensuring that your n8n data is being stored persistently. You have two options: | Cause | Explanation
The core reason is that n8n ties its license key to a unique . This situation usually arises in one of three scenarios:
This message appears in (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. | | Manual key reuse | You entered
: