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 —
Now the key is free to use on another instance. n8n activation key has already been used on this instance
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. Docker Compose configuration to ensure your instance ID
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. Jul 16, 2025 — Now the key is
:
:
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.