License Activation Failed on Self-Hosted Docker: "Key already used"

Built with n8n
1

Hello n8n team and community,

I am having trouble activating my free community license on a new self-hosted installation.

My setup is:

  • n8n version: latest (from n8nio/n8n:latest Docker image)
  • OS: Windows 11 with WSL 2 and Docker Desktop

I requested the key via email and received a UUID-style key. Here is what happened:

  1. My first attempt to activate the key resulted in an “Invalid format” error.
  2. After trying again, the error now consistently says: “Activation failed. Activation key has already been used on this instance.”

It seems the key was partially registered but the process failed, so now I am stuck. I cannot re-use the key.

Could you please help me resolve this? Thank you!

2

Hey Naja,
I ran into this as well. Have you gotten this resolved?

3

same here, I reinstall my vps now I cant use the license

4

This is a frustrating one but it’s fixable without waiting for support.

What’s happening: n8n’s license activation system ties the key to the first machine ID that activates it. If your n8n instance restarted with a different machine ID (happens with Docker if you didn’t persist the .n8n folder), the key thinks it was already used on a different machine.

How to fix it:

  1. Stop your n8n container
  2. Delete (or rename) the ~/.n8n directory inside the container / your mounted volume – specifically look for config or any file storing the instance ID
  3. Restart n8n – it’ll generate a fresh instance ID
  4. Try activating the key again

The key part: make sure your Docker setup has a persistent volume for .n8n data so this doesn’t happen again:

volumes:
  - ~/.n8n:/home/node/.n8n

If the key still shows “already used” after that, go to the original activation email and look for a “manage license” or “reset” link – n8n does provide a way to reset activation. If there’s no link, reply to that email explaining you did a clean reinstall. Their support team resets these pretty quickly.

The “invalid format” error on your first attempt is also a clue – it probably didn’t actually activate successfully the first time, but the system flagged the key as used anyway. That’s a known edge case they’ve had reports of before.