Unable to sign in N8N

[Ripan_Chowdhury]

I’m unable to login in, I cleared the cookies and browser data. then I’m not able to enter in the n8n dashboard using my credentials. may be I have forgotten. I tried removing the basic auth from environmental variables. using Heroku cli. But still the login page is showing. I have to 2 problems. How to get access first of all. Because I was working, and I’m unable to do that. And it’s business related so, it’s creating a huge problem for me.

2nd How to keep the login system active and change the credentials and then again start using that.

Please someone help me fast or ASAP. Your help is highly required.

I tried restarting my app from Heroku after setting the N8N_BASIC_AUTH_ACTIVE : false
and heroku config:unset N8N_BASIC_AUTH_USER --app app-name
heroku config:unset N8N_BASIC_AUTH_PASSWORD --app app-name

It’s still sowing me the sign in page.

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[Ripan_Chowdhury]

I’m on community free edition.
Have deployed heroku using One click deploy from n8n doc.

[aya]

Hi @Ripan_Chowdhury, have you tried resetting your admin login/password with n8n user-management:reset? You can find more info in our docs: CLI commands | n8n Docs

[Ripan_Chowdhury]

Thanks for replying. I have some doubt, but my n8n app is hosted on Heroku, may be it’s for local development, which will not work here. Does it work here?
Apart from this tell me one thing I tried removing the auth user using this

heroku config:set N8N_BASIC_AUTH_ACTIVE=false --app your-app-name
but after restarting the n8n login page is still as it was previously despite opening it fresh closing the tab. And I tried even changing the username and password using this

heroku config:set N8N_BASIC_AUTH_ACTIVE=true N8N_BASIC_AUTH_USER=new_username N8N_BASIC_AUTH_PASSWORD=new_password --app your-app-name

and even updated the PostgreSQL database using the PostgreSQL cli, using this UPDATE ‘user’ SET email = ‘[email protected]’, password = ‘new_password’ WHERE id = ‘my-id’;

All of them got successful but and each time I restarted as well my app from CLI but the n8n page is still the same, trying to login using the new credential but showing wrong username or Caps lock on. Please someone can check what’s happening in the back of n8n, or tell me what’s the issue.

[Ripan_Chowdhury]

I ran this command and this heroku run “n8n user-management:reset” --app appname , and this is the response. Successfully reset the database to default user state. It didn’t provide me any new credential, and the login page is still the same.

Setting N8N_BASIC_AUTH_ACTIVE, N8N_BASIC_AUTH_USER, N8N_BASIC_AUTH_PASSWORD and restarting ⬢ myapp… done, v19
N8N_BASIC_AUTH_ACTIVE: true
N8N_BASIC_AUTH_PASSWORD: ‘mypassword’
N8N_BASIC_AUTH_USER: ‘cho*************@gmail.com’

see this. and still the login page.

[aya]

Hi @Ripan_Chowdhury, if you managed to do n8n user-management:reset, you should see a Sign up page where you can create a new user account instead of signing in. Have you tried restarting the n8n instance and hard refreshing the page?

[Ripan_Chowdhury]

The Heroku team gave me this feedback. “From what I can see, this appears to be more of an app-related code error. I reviewed the logs from the Papertrail addon and found the following information.”

and this is the error what is happening but not sure, whether this is what is causing problem. I’m not entirely sure if these logs are directly related to your issue, as I don’t have the exact timestamps of when you encountered the problem. However, there has been a validation error followed by an Axios Error, which seems to occur due to a missing header. Could you please check if this might be the cause and see if you can address it?

Nov 26 10:26:08Z {myapp} app/web.1 ValidationError: The 'X-Forwarded-For' header is set but the Express 'trust proxy' setting is false (default). This could indicate a misconfiguration which would prevent express-rate-limit from accurately identifying users. See https://express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/ for more information.

And these are my current environmental variables, I tried changing these things.
DB_POSTGRESDB_SSL_ENABLED: true
DB_POSTGRESDB_SSL_REJECT_UNAUTHORIZED: false
GENERIC_TIMEZONE: Asia/Kolkata
N8N_BASIC_AUTH_ACTIVE: true
N8N_BASIC_AUTH_PASSWORD: mypassword
N8N_BASIC_AUTH_USER: myuser
N8N_DIAGNOSTICS_ENABLED: false
N8N_ENCRYPTION_KEY: anythingforyou
N8N_EXPRESSION_TRUST_PROXY: true
PAPERTRAIL_API_TOKEN: my_token
WEBHOOK_TUNNEL_URL: https://myapp.herokuapp.com
WEBHOOK_URL: my.url

[luoshenxy]

After debugging, log in and the previous instance is still there

[Ripan_Chowdhury]

I used the one click deploy, when I’m cloning the repository, an empty repository is getting cloned. And the code node --trace-deprecation is not working. I tried.
node --trace-deprecation 'node' is not recognized as an internal or external command, operable program or batch file.

[Jon]

So the first thing to do is remove the n8n_basic_x env options as we have not used those in over a year.

To resolve the express warning you will need to add N8N_PROXY_HOPS and set the value to 1 assuming you are only going through one reverse proxy.

Once that is done you will need to connect to the n8n instance and run the user management reset command provided previously this when ran in your running instance will reset the user management feature and let you create the owner account again.

The other option would be the set the user management smtp env options and use the forgot password link.

One thing to be aware of is if you have been manually playing with the database you may cause other issues so it could be best to use the cli to export your workflows then deploy n8n again and import them.

[Ripan_Chowdhury]

DATABASE_URL:                          postgres://{urldata}
DB_POSTGRESDB_SSL_ENABLED:             true
DB_POSTGRESDB_SSL_REJECT_UNAUTHORIZED: false
GENERIC_TIMEZONE:                      {timezone}
N8N_ENCRYPTION_KEY:                    imagine-me-to-something-else
N8N_PROXY_HOPS:                        1
PAPERTRAIL_API_TOKEN:                  {my_token}
SMTP_FROM:                             [email protected]
SMTP_HOST:                             smtp.gmail.com
SMTP_PASS:                             {mykey}
SMTP_PORT:                             465
SMTP_SSL:                              true
SMTP_USER:                             [email protected]
WEBHOOK_URL:                           https://www.mydomain.org.in

If this setting is the only thing needed for SMTP setting I have tried both the Ports. Each time restarting the app. Even after that nothing is happening. Showing me the same message. I cleared the n8n instance cache, every time.

And the user management restart as well, nothing is happening even after showing successfully done message. the sign in page remained the same. I tried making the diagnostic data set to false.

heroku config:set N8N_DIAGNOSTICS_ENABLED=false --app your-app-name

and also

heroku config:set N8N_USER_MANAGEMENT_DISABLED=true --app your-app-name

But the sign in page is still the same. No change is happening neither email setup is working or the sign up page is coming.

I tried downloading the workflows using

curl -o workflows.json https://<your-heroku-app-name>.herokuapp.com/workflows.json

but it gave me an error file in workflows.json.
Heroku | Application Error
iframe src=“//www.herokucdn.com/error-pages/no-such-app.html” . If I clone the codes in github will I be able to download or save my workflows? Does N8N team do have access of the end, so can check what’s happening in the back.