*
TO THE BRILLIANT MINDS IN THE COMMUNITY - PLEASE. ASSIST WITH THIS ISSUE. IF THERE IS SOMEONE WITH THE ANSWER TO THIS PROBLEM. I WOULD HIGHLY APPRECIATE THE HELP - *
*Title: Activation Key / Session Conflict Error *
Body: I am trying to activate my community license key on my self-hosted n8n instance, but I keep running into an issue where it behaves as if it’s already active or bound to another session/environment.
Hi Terence, this error is almost always about how activation keys work: a community key is bound to one instance at the moment you activate it. If your n8n was reinstalled, the database was reset, or (with Docker) the container/volume was recreated, your setup counts as a new instance — so the key looks “already active somewhere else.”
Two ways out, depending on your case:
1) Same instance as before (just glitched):
n8n license:info # see what's currently stored
n8n license:clear # remove the stale license data
Then restart n8n and re-enter the key under Settings → Usage and plan (on recent versions).
2) The instance was recreated (reinstall / new container / fresh DB):
Clearing won’t help because the key is consumed by the old instance. The fastest fix is simply to request a new free community key (same form/email you used the first time) and activate that one. Keys are free, so reissuing is the intended path.
To prevent this next time: keep your data folder (~/.n8n, or the Docker volume) persistent across upgrades — the license lives there with your workflows.
If neither works, tell me how you’re running n8n (npm or Docker) and whether you recently reinstalled or moved it, and I’ll help you narrow it down.