The 2FA recovery is broken using the most recent docker image testing
It works fine with the latest docker image.
[2022-12-14 11:18:11.510][request][INFO] POST /identity/accounts/prelogin
[2022-12-14 11:18:11.511][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK
[2022-12-14 11:18:11.558][request][INFO] POST /api/two-factor/recover
[2022-12-14 11:18:11.558][auth][ERROR] Unauthorized Error: No access token provided
[2022-12-14 11:18:11.558][_][WARN] Request guard `Headers` failed: "No access token provided".
[2022-12-14 11:18:11.558][_][WARN] No 401 catcher registered. Using Rocket default.
[2022-12-14 11:18:11.558][response][INFO] (recover) POST /api/two-factor/recover => 401 Unauthorized
Originally created by @richardmeilinger on GitHub (Dec 14, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2985
The 2FA recovery is broken using the most recent docker image `testing`
It works fine with the `latest` docker image.
```
[2022-12-14 11:18:11.510][request][INFO] POST /identity/accounts/prelogin
[2022-12-14 11:18:11.511][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK
[2022-12-14 11:18:11.558][request][INFO] POST /api/two-factor/recover
[2022-12-14 11:18:11.558][auth][ERROR] Unauthorized Error: No access token provided
[2022-12-14 11:18:11.558][_][WARN] Request guard `Headers` failed: "No access token provided".
[2022-12-14 11:18:11.558][_][WARN] No 401 catcher registered. Using Rocket default.
[2022-12-14 11:18:11.558][response][INFO] (recover) POST /api/two-factor/recover => 401 Unauthorized
```
GiteaMirror
added the bug label 2026-07-17 06:04:33 -05:00
Looks like they changed the workflow there to. Before you first needed to login, and then you could enter the recovery token. Now they combined them.
Thanks for the report.
<!-- gh-comment-id:1351289062 -->
@BlackDex commented on GitHub (Dec 14, 2022):
Looks like they changed the workflow there to. Before you first needed to login, and then you could enter the recovery token. Now they combined them.
Thanks for the report.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @richardmeilinger on GitHub (Dec 14, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2985
The 2FA recovery is broken using the most recent docker image
testingIt works fine with the
latestdocker image.@BlackDex commented on GitHub (Dec 14, 2022):
Looks like they changed the workflow there to. Before you first needed to login, and then you could enter the recovery token. Now they combined them.
Thanks for the report.