After restarting my n8n instance, some credentials stopped working even though I didn’t change anything.
Is there something about how credentials are stored that I’m missing
1 Like
I remember facing an issue like this
which credential exactly stopped working ?
It’s most likely going to be caused by the encryption key
If N8N_ENCRYPTION_KEY changes, n8n can’t properly decrypt stored credentials anymore.
can be fixed by setting a static encryption key and making it consistent across all deployments
3 Likes
Welcome to the n8n community @Okunomo_Marvellous
And yes, there’s a reason your credentials may fail after a restart and it all comes down to one piece of information: the encryption key. The credentials stored in the database are encrypted. If n8n can’t find the encryption key on restart to decrypt them, your credentials will no longer function.
yeah encryption key is the culprit usually. make sure N8N_ENCRYPTION_KEY is set the same way on restart, or use a persistent key in your env file. if you’re using docker and the key keeps changing, that’s probably why
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.