Repository navigation
v2.9.4 UI Login results in Status Code 400: Bad Redirect #1729
Description
/about output:
{
"version": "v2.9.3",
"uiVersion": "v2.9.3",
"commit": "c54b762",
"deploymentId": "01KBNFVYPZ46Y5EKD93MQ9GFVN",
"updateAvailable": false,
"latestVersion": null,
"llmActive": false,
"llmProvider": null,
"oidcActive": false,
"license": {
"name": "AGPL-3.0-only",
"version": "v1",
"plan": "OSS",
"deploymentInfo": "Managed"
},
"mode": "Distributed (Query)",
"staging": "/parseable/staging",
"hotTier": "Enabled, Path: /parseable/hot-tier",
"grpcPort": 8001,
"store": {
"type": "S3 bucket",
"path": "https://REDACTED"
},
"analytics": {
"clarityTag": null
}
}Description:
Updating app to v2.9.4 results in login to the UI being broken:
Error Code 400 Bad Redirect
Activity
nitisht commentedon Jul 17, 2026
Thanks for reporting @smparekh , we will get back on this shortly
praveen5959 commentedon Jul 17, 2026
Hi @smparekh ,
It'd help to look at your exact deployment config, browser network logs around the login redirect and any relevant server logs to narrow this down faster.
You can join our Slack so we can debug this together in real time?
smparekh commentedon Jul 17, 2026
We had to rollback to 2.9.3 so dont have a 2.9.4 instance available to test against.
I inspected the network logs at that time and it showed just that generic 400, Bad Redirect error when trying to log in. The direct url was the base url of the app.
nitisht commentedon Jul 18, 2026
Do you have OAuth set up here? If so, who is the provider?
nitisht commentedon Jul 21, 2026
Hi @smparekh we'd like to understand how we can repro this one and address it. Would you pls join us on slack so we can iterate quickly?
We're at http://logg.ing/community
nitisht commentedon Jul 30, 2026
gentle nudge on this one pls.