-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Request guard KnownDevice
failed: "X-Request-Email value failed to decode as base64url"
#3394
Comments
If I sniff the traffic on the unencrypted side, INSIDE Apache...
Where is is indeed arguably not valid base64 UNTIL you add the |
fixed 3 days ago. see 62cebeb |
Wait... has that made it into |
it should be in the testing image |
Is there such a thing as an |
Found
... and asks for master password, and syncs fine 😀 Splendiiiiid, will stick on Many thanks @tessus ! Duplicates #3375 - apologies! 🙈 |
You are welcome |
Would vote for a full release though. I assume almost 2/3rds of Android users and 2/3rds of browser plugin users are broken right now? Some may not know it until they next need to log in? |
@dani-garcia I think it would make sense to make a hot fix release (once #3390 has been merged). |
We want to wait for more issues to be reported on other items. We already had one other besides this one. Both are fixed. But yea, a .1 release is probably a good thing |
Subject of the issue
Request guard
KnownDevice
failed: "X-Request-Email value failed to decode as base64url".Web vault works fine (2023.3.0)
Android app (2023.3.2 - latest?) gives "we were unable to process your request, please try again or contact us".
Firefox addon (2023.3.0 - latest? but also 2023.2.1 before that) gives whirly wait-spinner thing.
... but only for ONE USER. Six other users work fine. Log says:
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
It's not "running under docker" as such, but it IS running the docker image - vaultwarden/server:alpine - 2023.3.0 - under runc. Essentially exactly the same as running under Podman. A lot like docker but with less bloat.
Clients used: Web vault works fine (2023.3.0)
Android app (2023.3.2 - latest?) gives "we were unable to process your request, please try again or contact us".
Firefox addon (2023.3.0 - latest? but also 2023.2.1 before that)
Reverse proxy and version: Apache
Other relevant details:
Steps to reproduce
Honestly not sure what's so "special" about this one particular user 😐
Expected behaviour
Log in?
Actual behaviour
Above error on android. Whirly wait-pointer on firefox plugin.
Troubleshooting data
The text was updated successfully, but these errors were encountered: