#n8n password lost

31 messages · Page 1 of 1 (latest)

empty copper
#

I lost the password of my n8n instance in my project, and I wanted to know if its possible to reset it with some process.

steep skyBOT
#

Project ID: 268f41cb-9148-4ede-9886-ed409e9116d5

empty copper
#

268f41cb-9148-4ede-9886-ed409e9116d5

amber aspen
#

I'm not familiar with the n8n template, but from my experience with other databases on Railway, there may be an environment variable containing your password. DO NOT CHANGE IT - but it will have your current password

empty copper
#

It doesn't look like the case, no.
I presume the variables you mean would be in this variables section of the n8n primary service. Checking here only has encryption keys and passwords for my PostgreSQL service, but not the password for n8n itself

amber aspen
#

Would using the Railway CLI to SSH into your service and running that command be an effective solution?

empty copper
#

Huh, don't know, but it sounds promising!

Lemme check rq

empty copper
#

Well, I think I did everything correctly:
Installed the Railway CLI
Logged in the CLI into my railway account
Linked the railway CLI instance to the n8n service in my project, using the project ID
Used the command ssh to connect to the n8n service interactive shell
Used the n8n user-management:reset command you found

And... well, it says it did something, but when I tried to enter the n8n service through Railway (like usual, through the browser), its still asking for a email and password which I do not have

#

I feel like im just missing something obvious here, sorry, haha

amber aspen
#

does the forgot password button not work?

#

Unfortunately I’m not going to be much help here, I’m not familiar with n8n. I would suggest asking elsewhere or googling your issue first

empty copper
#

ah, no, It says to "contact an admin" since there's no email recovey or things like that

empty copper
tropic sleet
#

The worker or the other one?

empty copper
#

the primary, not the worker

tropic sleet
#

try on the worker

#

(just guessing here)

empty copper
#

worth a try, sure

tropic sleet
#

also try redeploying these two services

#

after running that command

#

as a last effort (if you're desperate) I would try accessing the DB and seeing if there's any user related table and deleting the data there

#

but that could brick everything

empty copper
#

Alriiight, redeploying was the last step, yeah

tropic sleet
#

nice!

empty copper
#

alright alright, thanks!

#

fixed the issue, and I got to use CLI, which is always fun

ok now how do I mark this as resolved again...

tropic sleet
#

I will mark this as solved, don't worry about it

#

!s