I have a n8n that I have backup to redeploy to an other domain (to organize a testing platform) but the licence key is now invalid with this message:
Failed to activate license: license activation failed: device fingerprint mismatch Failed to activate license: license activation failed: device fingerprint mismatch
I also have in the logs:
[license SDK] cert is invalid because device fingerprint does not match
I tried to regenerate a new one, but it’s not working.
Purpose of the backup is not to recreate the workflows and credentials I have set already so…
On the other instance, I never changed it until now, and all seems alright.
Hello,
Still having this issue but now on the production instance…
Does that have any effects on webhooks or anything ? (but saturating the logs)
I’m trying to set a webhook on my cloud version, all is working fine, but on my instances it doesn’t work, that’s why I’m asking…
Thanks !
I have activated my first instance, but I don’t have it anymore. Is there a way to have it back somewhere ?
Then I made a backup of the Postgres database, to redpeploy a staging instance (using the same encryption key of the instance) N8N_ENCRYPTION_KEY in my env.
So I can use the credentials previously entered as the workflows created.
But on the staging instance, I don’t have the licence key activated.
If Im trying to generate a new API key I have :
Failed to activate license: license activation failed: device fingerprint mismatch
Failed to activate license: license activation failed: device fingerprint mismatch
I also see that my new credentials, but also my workflows created on the new instance are now tagged to my name, and not “Personal” as it used to be.
That leads to an impossibility of sharing or using the credentials , and surely problems while executing sub workflows that does not belong to personnal to be executed.
Is it possible to have a backup of my initial aPI key ? (to try to inject it again and see if it works) or how can I have a new API key generated and functional ?
Hey @NiKoolass , is it registered community license do you use or Startup license?
The fingerprint mismatch issue only comes up on instances that already have a license activated which is bound to a different instance. It appears that something happens during a deployment that the device fingerprint changed.
You can see more details about your n8n instance license by running the CLI command (see CLI commands | n8n Docs for details)
n8n license:info
Depending on your license entitlements (!), the solution could be to clear the license and enter it again.
Hello,
Sorry for the late reply, it’s the community licence (the free first for limited time as I see)
It brings some features, but it’s not the startup licence.
Typically this could be resolved by clearing the current license and re-entering it again assuming the activation window is still open. If expired, you can request a new registered community license.
