This error typically appears when you try to apply a license key to an instance that the n8n license server already considers "registered." Whether you are running the Community Edition or a paid plan, this guide will help you understand why this happens and how to resolve it.
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. n8n activation key has already been used on this instance
n8n ties license keys to (like a machine ID or installation hash) to prevent one key from being used on multiple servers simultaneously. This error typically appears when you try to
If you are using Docker, ensuring your .n8n folder is mapped to a persistent volume is critical. Without this, your Instance ID might change every time the container restarts, leading the license server to think you are trying to use the same key on multiple different machines. If you are using Docker, ensuring your
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 —