Login: 400 Bad request

[dhenry123]

Hi, From 1.5.0, impossible to update to 1.5.1, on login, i got a response 400 bad request, tried to upgrade 1.5.0=>1.5.2 the same. Platform is arm64 with binary package. The ingest process works

Best regards

[nitisht]

What is the user here? Are you logging in as admin?

[dhenry123]

yes and also tried changing env var (P_USERNAME && P_PASSWORD) at start, and i loosed my reports when i rolled back to 1.5.0 (not really a problem for my case).

[nikhilsinhaparseable]

can you please open the network tab and check the API request and error response when you try login

[balaji-jr]

In addition to that,

1. Can you also post the failed /login network request URL as well (to verify the redirect URL which has been sent as query params)
2. Or you can try removing the env vars completely and logging in with the default username and password admin & admin
3. Would it be possible to check the .parseable.json where all the users' details have been saved? Could you verify that the user you are trying to log in exists? (In case if you are trying with a user created by you in the UI)

[dhenry123]

i load the login page, set admin/admin (appears in the logs server) and click on the login button, ui send only one request https://[mydomain/api/v1/o/login?redirect=https://[mydomain] response is 400 Bad Request

I m behind a reverse proxy in charge to proceed httpS which works well with 1.5.0

[dhenry123]

i ve just restarted the process after removing all data including .users .parseable, server start normally but impossible to log in with admin/admin as displayed in the log server i tried to use sso same response

[wendellrocha]

I'm experiencing the same issue. I'm behind an Nginx Proxy Manager instance using Cloudflare tunnels to expose it to the internet.

Accessing by the IP, over HTTP works.

[balaji-jr]

Ty. @wendellrocha This helps. We will fix this shortly.