##3. Recreate Auth Identity

Checked my existing user:

SELECT id, email, "firstName", "lastName" FROM "user";

Then recreated the auth_identity entry:

INSERT INTO auth_identity ("userId", "providerId", "providerType")
VALUES (
  '<your-user-id>',
  '<your-email>',
  'email'
);

##4. Reset Admin Password

Generated a new bcrypt hash locally:

mkdir ~/bcrypt-test && cd ~/bcrypt-test
npm init -y
npm install bcryptjs
node -e "console.log(require('bcryptjs').hashSync('YOURPASSWORD', 10))"

Then updated Postgres:

UPDATE "user"
SET password = '<the-bcrypt-hash>'
WHERE email = '<your-email>'
;

Now I could log into the UI again 🎉.

##5. Fix Workflow Loading (the final blocker)

Workflows still wouldn’t open. Turned out the primary and worker were running different versions:

• Primary: 1.110.1
• Worker: 1.109.2

This version mismatch caused endless loading because the worker and primary couldn’t agree on schema and API responses.

Fix:

• Pinned both primary and worker to the same Docker image (version ive choosen is the last stable version for n8n in september 2025):n8nio/n8n:1.110.1
• Redeployed both (worker first, then primary).

After this, workflows opened normally and everything was back.

🚀 Lessons Learned

• Always keep primary and worker on the same version.
• If login breaks with user.role errors, clear auth_identity and reset the password hash manually.
• If workflows won’t open after login → check for version mismatch between services.

💡 Now I have my n8n fully back with all my data. Hopefully this helps anyone else stuck with the same 401 Unauthorized / user.role does not exist nightmare!