Promo Key Error: "Already Used" on Self-Hosted Docker n8n (v1.92.2) After Resets

Questions
, ,
1

Hi,

I’m having trouble with a lifetime community license key I received (starts with 52c5cd..., ends with ...6e55). I’m running n8n in Docker, self-hosted.

During the initial setup, I had some permission issues and had to reset the instance (delete volume, re-create container) a few times. The owner account is now created and n8n is running fine.

When I try to activate the key in Settings > Usage & Plan, I get errors like:

  • “Activation failed. Activation key has already been used in this instance”
  • “Activation failed. Activation key is in the wrong format”

The key format itself looks ok. I think the key might have been marked “used” during one of the failed setups.

Is there a way to reset this key for my current instance?

My n8n setup:

  • n8n Version: 1.92.2
  • Database: SQLite (default)
  • Running n8n via: Docker
  • Operating system: Ubuntu Server [Doplň svou verzi, např. 24.04 LTS]

Thanks for any help.

2

Welcome to the community! :grin:

Could you try the cli commands n8n licence:clear & n8n licence:info Docs

and try to activate the licence again

3

Hi BuddiesD,

Thanks for your suggestion to use n8n license:clear. Unfortunately, that didn’t solve my problem.
Here’s what I tried and the results:

I ran n8n license:clear and restarted n8n. After this, license:info confirmed there was no active license.

I then tried to activate my key in the n8n UI.

Unfortunately, it still failed with the error: “Activation key has already been used on this instance”.
After this failed attempt to use my key, checking license:info again shows that a “Registered Community” license (which is not my key) has reappeared. The deviceFingerprint remains the same as before.

I don’t see any of the premium features like Workflow History, folder creation, or advanced debugging that my key should unlock.

I’ll try contacting n8n support directly about resetting my key on the server side. Once I have a solution, I’ll share it here for others who might encounter a similar issue.

1 Like
4

You should be able to, make new instance and enter email again to get new license, they should email you then a new community license? I assume its the same permission you have etc and will enable them features.