Error: Credentials could not be decrypted. The reason is that probably a different "encryptionKey" got used to encrypt the data than now to decrypt it

Questions
1

Hi N8N team,

I fired up the platform today after a couple days of inactivity, and I get the following error for my credentials.

ERROR: Credentials could not be decrypted. The reason is that probably a different "encryptionKey" got used to encrypt the data than now to decrypt it.

Error: Credentials could not be decrypted. The reason is that probably a different "encryptionKey" got used to encrypt the data than now to decrypt it.
    at Credentials.getData (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/Credentials.js:41:19)
    at CredentialsHelper.getDecrypted (/usr/local/lib/node_modules/n8n/dist/src/CredentialsHelper.js:47:51)
    at getCredentials (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/NodeExecuteFunctions.js:187:66)
    at Object.getCredentials (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/NodeExecuteFunctions.js:378:24)
    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest.node.js:585:37)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/src/Workflow.js:492:37)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/WorkflowExecute.js:395:62

I thought it was only uProc but it turns out that this is happening with Gitlab and other credentials as well

2

This is what happens when I try to edit the credentials

image
image806×500 33.7 KB

3

I just want to be comprehensive so I’m not flagging something that may be on my side:

My connection dropping may also be the reason for some of this behaviour

image
image1762×1428 244 KB

4

We’re sending an email in a few minutes. Is actively being resolved.

5

Appreciate it Max. Go team!

6

Should all now be resolved once credentials have been recreated. Let me know if you have any questions!