Hi - I need help with an activation key issue with the Community Edition.
Error message (“Activation key has already been used on this instance.”).
Your n8n account email address. - rdesai@aptbusinessservices.com
The activation key -
Running n8n in (e.g., Docker, local machine, self - hosted).
Hi @rdesai Welcome!
“Activation key has already been used on this instance” means the key was already redeemed against that instance, so it can’t be applied a second time. Check Settings > Usage and plan first, if it already shows Registered then the community licence is active and there is nothing left to do.
If it doesn’t show Registered, clear the stored licence and re-enter the key. On Docker:
docker exec -u node -it <your-n8n-container-name> n8n license:clear
Restart the container, then paste the key again in Settings > Usage and plan. On an npm install run n8n license:clear directly, no docker exec needed.
What the registered community edition actually unlocks:
Hi @rdesai welcome to the community
Good point is that, this is almost always fixable on your end. The “already been used on this instance” message usually means your instance is still registered with the license locally, rather than the key being genuinely exhausted.
First, confirm the state: go to Settings - Usage and Plan. If it shows Registered, that’s the situation we’re fixing.
Then clear the license and re-apply :
If you’re running n8n directly (npm/local):
n8n license:clear
…then restart n8n and re-enter your activation key.
If you’re running in Docker:
docker exec -u node -it <your-n8n-container-name> n8n license:clear
…then restart the container, go back to Settings - Usage and Plan, and then enter the key again.
If it still stuck or fails after that, the old instance identity is probably persisting. Double check that your persistent data folder (the .n8n directory / mounted volume) is actually the one you expect on Docker/LXC setups the app can be “new” while still mounting the old data where the instance ID lives. Starting with a genuinely clean data path should let it activate.
If you’ve confirmed the license is cleared and the data path is clean and it’s still rejected, then the key is likely bound on n8n’s side — in that case the n8n team can reset/re-issue it server side. Let us know how the steps above go and we can take it from there.
Note: no need to paste your full activation key publicly, best to keep that private.
Thank you so much Hammad. It workd
Thank you Anshul. I am all set
Mark my post as solution, Thanks.