Activation failed : Activation key has been used too many times

Questions
1

Describe the problem/error/question

During a longer setup and debugging process of my self-hosted n8n instance (Docker + reverse proxy + version update), I entered the free self-hosted activation key multiple times.

I was not aware that there is a limit on how often the activation key can be submitted. After several restarts and configuration changes, the activation is now blocked and the features remain disabled, even though the instance itself is working correctly again.

I understand that this limit is likely enforced server-side, as restoring from backups does not resolve the issue.

My question is:
Is there a way to reset or unlock the activation key for a self-hosted instance after too many activation attempts?

What is the error message (if any)?

Activation failed

Activation key has been used too many times

Please share your workflow

Not applicable – this issue is not related to a specific workflow.

Share the output returned by the last node

Activation failed

Activation key has been used too many times

Information on your n8n setup

  • n8n version: latest 2.6 .4

  • Database: SQLite (default)

  • n8n EXECUTIONS_PROCESS: default (own)

  • Running n8n via: Docker (docker-compose)

  • Operating system: Linux (VM)

1 Like
2

hello @Tewel

Why are you entering it multiple times? The license is stored in the database, so you don’t need to re-enter it.

I think better to request another license key if we are talking about the community version.

1 Like
3

Thanks for your reply.

Just to clarify:

During troubleshooting I also reset the local data directory at some point to ensure configuration changes were applied cleanly. That likely caused the stored license to be removed, which explains why I had to re-enter the activation key multiple times.

There was no intention to misuse the license — this was purely part of debugging the Docker/reverse proxy setup.

After fixing the proxy configuration, the instance is now stable. However, the activation attempt is now rejected, likely because I exceeded the submission limit during that debugging phase.

If requesting a new community license key is the recommended approach in this situation, I’m happy to do that. I just wanted to make sure I’m following the correct process.

Thanks again.

1 Like
4

I encountered a similar issue recently, due to troubleshooting I had to reinstall n8n multiple times, this caused the key to work briefly before being rejected (I don’t recall the exact error message), and I eventually had to use a key generated with an old instance to resolve it..

I would also like to know if it is possible to reset the key for the original email address on the current active instance, rather than having to use a new email account, or an old unused one..

2 Likes
5

There hasn’t been any official clarification yet.
I worked around the issue by setting up a new instance with a different email address.
At the moment, that appears to be the only viable solution.

6

Hi,

I have the same problem, I was experimenting with setting up my server VMs and docker containers (incl. n8n) using Ansible. During this journey i entered the key multiple times.

I was not even aware that there is a restriction on entering the lifetime license key, otherwise I would’ve been more careful.

Is there a possibility to get a new or restored license key?

Best regards,

Stefan

1 Like