Hey there! We've found the following might help you get unblocked faster:

• 🧵 SMTP blocked for n8n password recovery impacting our students

• 🧵 n8n Cluster Worker Not Dequeuing Jobs from Redis (Webhook Triggers Stuck)

• 🧵 Request for Assistance with Access Issues and Login Problems on n8n Server

If you find the answer from one of these, please let us know by solving the thread!

Hey, the quickest way is just to reset all user credentials by running n8n user-management:reset within your primary service and redeploy it afterwards, more on that can be found at https://docs.n8n.io/hosting/cli-commands/#user-management. You will have to use the Railway CLI to SSH into your service to run the command (redeploying can be done in the dashboard).

Can someone give me a simple step-by-step guide to resolve this password issue? Someone who can look inside the project

I need specialized support because I lost the password for an n8n project and can't access it again. I'm not a programmer; I only work with n8n automations and flows.

I updated n8n and lost the credentials without being able to update them, so I had to revert to the previous version for the flows to continue working. The n8n flows continued to run with their correct credentials, but the password was lost.

I tried using SMTP variables:

| Variable | Value |

| ---------------- | ------------------------------------------ |

| N8N_EMAIL_MODE | smtp |

| N8N_SMTP_HOST | smtp.gmail.com |

| N8N_SMTP_PORT | 465 |

| N8N_SMTP_USER | lucasflores2021@gmail.com |

| N8N_SMTP_PASS | (the app password from step 3, without spaces) |

| N8N_SMTP_SSL | true

Unsuccessful, as it continues to give an SMTP error when resending the access password via email.

I can't get specialized support to recover the password, even if I have to pay by the hour, because I can't afford to lose another project. If I lose this project again, I'll have to switch to another platform.

Hey, I would suggest to post to the n8n forum if you require specialized support for n8n. Have you followed the n8n docs regarding SMTP for this use case https://docs.n8n.io/hosting/configuration/user-management-self-hosted/#step-one-smtp? I still would recommend to just SSH into your service and run the command, which is far quicker to do then setting up SMTP, especially when you are the only person using your own hosted n8n instance.

Project Luciano-mundogif linked successfully!

C:\Users\lucas>railway ssh

✓ Connected to interactive shell

/home/node # n8n user-management:reset

Error tracking disabled because this release is older than 6 weeks.

Error resetting database. See log messages for details.

column User.role does not exist

/home/node #

C:\Users\lucas>

I got this error now. It's telling me to update the n8n version, but I'd like to access the same version

Hey, did you redeploy your n8n service?

yes, I currently have these variables

DB_POSTGRESDB_DATABASE="${{Postgres.POSTGRES_DB}}"

DB_POSTGRESDB_HOST="${{Postgres.PGHOST}}"

DB_POSTGRESDB_PASSWORD="${{Postgres.POSTGRES_PASSWORD}}"

DB_POSTGRESDB_PORT="${{Postgres.PGPORT}}"

DB_POSTGRESDB_USER="${{Postgres.POSTGRES_USER}}"

DB_TYPE="postgresdb"

ENABLE_ALPINE_PRIVATE_NETWORKING="true"

EXECUTIONS_MODE="queue"

N8N_EDITOR_BASE_URL="https://${{RAILWAY_PUBLIC_DOMAIN}}"

N8N_EMAIL_MODE="smtp"

N8N_ENCRYPTION_KEY="I*d6TKcJL8*694BG-AJ8eSpo5lSH575R"

N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS="true"

N8N_LISTEN_ADDRESS="::"

N8N_RUNNERS_ENABLED="true"

N8N_SMTP_HOST="smtp.gmail.com"

N8N_SMTP_PASS="senhasmtp"

N8N_SMTP_PORT="465"

N8N_SMTP_SSL="true"

N8N_SMTP_USER="lucasflores2021@gmail.com"

N8N_USER_MANAGEMENT_DISABLED="true"

NODE_OPTIONS="--max_old_space_size=8192"

OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS="true"

PORT="5678"

QUEUE_BULL_REDIS_DUALSTACK="true"

QUEUE_BULL_REDIS_HOST="${{Redis.REDISHOST}}"

QUEUE_BULL_REDIS_PASSWORD="${{Redis.REDIS_PASSWORD}}"

QUEUE_BULL_REDIS_PORT="${{Redis.REDISPORT}}"

QUEUE_BULL_REDIS_USERNAME="${{Redis.REDISUSER}}"

WEBHOOK_URL="https://${{RAILWAY_PUBLIC_DOMAIN}}"

Have you tried to redeploy all of your n8n instances, including the worker and run the command again? Seems like n8n user-management:reset didn't go through since the database doesn't have a User.role column, redeploying them may apply some migrations. You may also follow the n8n forum, which has a thread dedicated to it.

Our team programmer solved it. They aligned the worker and the instance in v n8nio/n8n:1.110.1

https://community.n8n.io/t/column-numbers-role-does-not-exist/185513/6