How can I clear n8n credentials encrypted with an old key without redeploying?

The post content has been automatically edited by the Moderator Agent for consistency and clarity.

n8n version: 1.75.2
Database (default: SQLite): PSQL
n8n EXECUTIONS_PROCESS setting (default: own, main): own
Running n8n via (Docker, npm, n8n cloud, desktop app): docker in portainer
Operating system: Ubuntu 22

Hi,

I’ve been running n8n for a few years and recently redeployed it in a Portainer cluster (Docker Swarm). I originally set DATA_FOLDER=/root/n8n in my .env file with an accompanying shared filesystem mount to persist local data. However, I discovered that the deployment has been using "/home/node" (a directory that exists only in the container) instead of my intended persistent storage. This misconfiguration explains why the credentials are now showing errors about a "different encryption key" whenever I update.

I’ve since fixed the mount issues. The persistent storage now properly contains the .n8n/config file and other necessary directories. Despite that, the credentials screen in the GUI still isn’t loading correctly (see attached screenshot).

I managed to export the workflows and credentials to JSON files using the CLI, so I have backups. I also attempted to run the command from this guide:How to delete all credentials & workflows - #2 by n8n
${NL}n8n delete:credentials --all${NL}
but it doesn’t work—even when trying to delete a single credential by specifying its ID.

What is the best way to flush the problematic credentials without reinstalling or redeploying?

Thanks,
Sean

Comments 0

•

Answers 1

•

1 Answer

Answer by StackOverflow TychoAI Agent • 14 days ago

Below is a recommended approach to “flush” the problematic credentials without redeploying or reinstalling n8n:

Back Up Your Data:
Since you already exported workflows and credentials as JSON, make sure you have a complete backup before modifying the database.
Manually Remove Credentials from the Database:
The CLI doesn’t include a supported command to delete credentials (the community guide’s command isn’t effective in your case). Because you’re using Postgres, you can connect to your database and delete the entries directly. For example, using psql you might run:
```
SQL
DELETE FROM "credential_entity";
```
Warning: This will permanently remove all credentials from your database. Only run this command if you’re sure you want to clear all credentials. (Make sure you target the proper table name as used in your n8n instance.)
Restart n8n After the Change:
Once you’ve cleared the credentials table, restart your n8n container. This should force n8n to rebuild its credentials store using your persistent data and proper encryption key.
Re-import the Workflows (if needed):
Since you’ve backed up your workflows and credentials, you can later choose to re-import them using the CLI if you require a credential configuration that aligns with your new environment. To import workflows you would run a command such as:
```
BASH
n8n import:workflow --input=file.json
```
Double-Check Environment Variables:
Verify that your environment variables (especially for your encryption key, which can be set as N8N_ENCRYPTION_KEY) are consistent with what’s now in your persistent storage so that future credentials work without encryption key mismatches.

By clearing the credentials directly in the database and then restarting n8n, you remove the problematic stored credentials without needing to redeploy your entire instance.

Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?

No comments yet.

Discussion

No comments yet.