Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Unable to login via http header #555

Open
1 task done
M1scer opened this issue Jan 20, 2025 · 0 comments
Open
1 task done

[Bug]: Unable to login via http header #555

M1scer opened this issue Jan 20, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@M1scer
Copy link

M1scer commented Jan 20, 2025

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

If you want to log in via the Auth header, this is not possible. When opening the database, you will still be asked for a password that has never been set.
This behavior only occurs since version 25.01.

There is a discussion about this on Discord:
https://discord.com/channels/937901803608096828/1326262567605375038

What error did you receive?

Logfile:

Checking if there are any migrations to run for direction "up"...
Migrations: DONE
Listening on :::5006...
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.
    at _Validations.<anonymous> (file:///app/node_modules/express-rate-limit/dist/index.mjs:154:15)
    at _Validations.wrap (file:///app/node_modules/express-rate-limit/dist/index.mjs:287:18)
    at _Validations.xForwardedForHeader (file:///app/node_modules/express-rate-limit/dist/index.mjs:152:10)
    at Object.keyGenerator (file:///app/node_modules/express-rate-limit/dist/index.mjs:516:19)
    at file:///app/node_modules/express-rate-limit/dist/index.mjs:569:32
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///app/node_modules/express-rate-limit/dist/index.mjs:550:5 {
  code: 'ERR_ERL_UNEXPECTED_X_FORWARDED_FOR',
  help: 'https://express-rate-limit.github.io/ERR_ERL_UNEXPECTED_X_FORWARDED_FOR/';
}
2025-01-07T18:34:47.566Z info: GET 200 /account/needs-bootstrap
2025-01-07T18:34:47.638Z info: GET 304 /account/needs-bootstrap
2025-01-07T18:34:47.743Z info: GET 304 /account/needs-bootstrap
2025-01-07T18:48:38.448Z info: GET 200 /account/needs-bootstrap
2025-01-07T18:48:38.453Z info: GET 200 /account/needs-bootstrap
2025-01-07T18:49:12.336Z info: GET 200 /account/needs-bootstrap
2025-01-07T18:49:12.338Z info: GET 200 /account/needs-bootstrap

Screenshot:

Image

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox, Chrome, Microsoft Edge

Operating System

Windows 11

@M1scer M1scer added the bug Something isn't working label Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant