Fingerprint issues after rebuilding docker container for n8n

Questions
1

Describe the problem/error/question

I have rebuilt the docker container for n8n on my self-hosted SSH on GCP, and now I cannot use the community features that are free to unlock with the activation key. My fingerprint from the logs is:
a564f6be88856da9690dc37c3bce40bd9570372075f528f9887da59838574333

What is the error message (if any)?

Activation failed
Failed to activate license: license activation failed: device fingerprint mismatch

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3
  • n8n version: 1.71.3
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): ?
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker on google cloud platform
  • Operating system: Ubuntu
4

I can’t find anywhere else in this forum to post this question. :frowning:

Does anyone have a contact for reaching out regarding getting a fingerprint matched to a community activation key? TIA

5

Welcome to the community @POZENyoga !

Tip for sharing information

Pasting your n8n workflow

Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.

```
<your workflow>
```

That implies to any JSON output you would like to share with us.

Make sure that you have removed any sensitive information from your workflow and include dummy or pinned data with it!

Here’s the answer to the same problem, Help with n8n community license, unable to activate after re-deploy - #2 by ihortom.

In short,

  1. Run CLI command n8n license:clear
  2. Restart n8n instance
  3. Re-enter the license key
6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.