Logging in fails with 403 after upgrading to v2.1.0 #4126
Closed
Description
Past Issues Searched
- I have searched open and closed issues to make sure that the bug has not yet been reported
Issue is a Bug Report
- This is a bug report and not a feature request, nor asking for self-hosted support
Using official Plausible Cloud hosting or self-hosting?
Self-hosting
Describe the bug
After upgrading from v2.0.0 I am having the same issue that was reported for v2.1.0-rc0: when trying to log in I get a 403 and no logs.
As already mentioned there by others, I can reproduce the problem by reverting back to v2.0.0 and then switching again to the v2.1.0 image. Postgres and Clickhouse images have been upgraded (respectively to 16-alpine
and 24.3.3.102-alpine
), the TOTP_VAULT_KEY
env var has been added, and SECRET_KEY_BASE
is untouched.
Expected behavior
Login should be possible.
Screenshots
Environment
- OS: Linux
- Browser: Chromium
- Browser Version: 125.0.6422.60
Metadata
Assignees
Labels
No labels