a month ago
I have an n8n instance unable to accept logins due to encryption key mismatch. All credentials were encrypted with an old/missing N8N_ENCRYPTION_KEY. I've set a new key, but the old encrypted data can't decrypt.
The problem: I have 5 active workflows I cannot afford to lose:
What I need: Can you selectively clear the user and auth_credential tables in the n8n Postgres database WITHOUT deleting workflow data? This would let n8n reinitialize without losing my workflows.
Project details:
Project: n8n - GGS (ID: cca1092d-b213-4714-a11f-e698b895cae7)
Environment: production
n8n service: n8n
Postgres service: Postgres
Database: n8n
Pinned Solution
a month ago
You can clear the auth tables via the Database tab in your Postgres service. However, you'll probably need to recreate your credentials and relink them to the workflow nodes in the database manually.
3 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Your workflows are stored separately from authentication data, so in principle it's possible to reset the authentication layer without deleting workflows—but only if the workflow tables are left untouched.
Before making any changes:
Back up the PostgreSQL database.
Verify which n8n version is running.
Confirm that only the authentication tables (user, auth_identity, auth_provider_sync_history, auth_credential, etc., depending on the version) will be cleared.
Do not modify the workflow_entity, execution_entity, credentials_entity, or other workflow-related tables unless absolutely necessary.
After clearing the authentication tables, restart n8n so it can recreate the admin account. Note that any stored credentials encrypted with the old N8N_ENCRYPTION_KEY cannot be recovered without the original key and will need to be recreated.
The safest approach is to reset authentication while preserving the workflow data and database backup in case a rollback is needed.
a month ago
PostgresSQL Backed up today
n8n version is 2.30.7
The Railway Help Agent is saying that only Railway Support can do this task
I have an n8n instance unable to accept logins due to encryption key mismatch. All credentials were encrypted with an old/missing N8N_ENCRYPTION_KEY. I've set a new key, but the old encrypted data can't decrypt.
The problem: I have 5 active workflows I cannot afford to lose:
WF1 — AI Front Desk: Call Handler (ID: lbDRox5RDztHGSEE)
WF2 — AI Front Desk: Check Availability (ID: 3QGGu8lsqcr7LaOu)
WF2b — AI Front Desk: Book Appointment (ID: wru6bBRko4jbF7LH)
WF3 — AI Front Desk: Notifications (ID: hA8qvMZmcvBnNzU9)
WF5 — AI Front Desk: Missed Call Recovery (ID: u7kxj3xfm3ogfJS7)
What I need: Can you selectively clear the user and auth_credential tables in the n8n Postgres database WITHOUT deleting workflow data? This would let n8n reinitialize without losing my workflows.
Project details:
Project: n8n - GGS (ID: cca1092d-b213-4714-a11f-e698b895cae7)
Environment: production
n8n service: n8n
Postgres service: Postgres
Database: n8n
rohitpuri1-ai
PostgresSQL Backed up today n8n version is 2.30.7 The Railway Help Agent is saying that only Railway Support can do this task I have an n8n instance unable to accept logins due to encryption key mismatch. All credentials were encrypted with an old/missing N8N_ENCRYPTION_KEY. I've set a new key, but the old encrypted data can't decrypt. The problem: I have 5 active workflows I cannot afford to lose: WF1 — AI Front Desk: Call Handler (ID: lbDRox5RDztHGSEE) WF2 — AI Front Desk: Check Availability (ID: 3QGGu8lsqcr7LaOu) WF2b — AI Front Desk: Book Appointment (ID: wru6bBRko4jbF7LH) WF3 — AI Front Desk: Notifications (ID: hA8qvMZmcvBnNzU9) WF5 — AI Front Desk: Missed Call Recovery (ID: u7kxj3xfm3ogfJS7) **What I need: Can you selectively clear the user and auth_credential tables in the n8n Postgres database WITHOUT deleting workflow data? This would let n8n reinitialize without losing my workflows.** Project details: Project: n8n - GGS (ID: cca1092d-b213-4714-a11f-e698b895cae7) Environment: production n8n service: n8n Postgres service: Postgres Database: n8n
a month ago
You can clear the auth tables via the Database tab in your Postgres service. However, you'll probably need to recreate your credentials and relink them to the workflow nodes in the database manually.
Status changed to Solved 0x5b62656e5d • about 1 month ago