[GH-ISSUE #669] Cannot create Recovery Code #452

New issue

Closed

opened 2026-03-03 01:29:16 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 01:29:16 +03:00

Owner

Originally created by @paradeiser on GitHub (Oct 16, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/669

I have this issue, I discussed earlier with kspearrin at bitwarden/web
Might be an bitwarden_rs issue:
https://github.com/bitwarden/web/issues/421

I cannot create/view recovery codes if the first 2FA option (Auth-App, 6-digit code) is not selected.
If Duo and/or Mail is activated (working just fine) I still get the message:
"No 2FA activated. After you activate 2FA you can view code here…"

thank you,
pardeiser

Originally created by @paradeiser on GitHub (Oct 16, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/669 I have this issue, I discussed earlier with kspearrin at bitwarden/web Might be an bitwarden_rs issue: https://github.com/bitwarden/web/issues/421 I cannot create/view recovery codes if the first 2FA option (Auth-App, 6-digit code) is not selected. If Duo and/or Mail is activated (working just fine) I still get the message: "No 2FA activated. After you activate 2FA you can view code here…" thank you, pardeiser

kerem closed this issue

2026-03-03 01:29:17 +03:00

kerem commented

2026-03-03 01:29:17 +03:00

Author

Owner

@BlackDex commented on GitHub (Oct 16, 2019):

I see in the code that there is no recover code generated during the duo setup.
This should be fixed to do that.

This also goes for the e-mail 2FA. Since that also doesn't generate a recover token.

@BlackDex commented on GitHub (Oct 16, 2019): I see in the code that there is no recover code generated during the duo setup. This should be fixed to do that. This also goes for the e-mail 2FA. Since that also doesn't generate a recover token.

kerem commented

2026-03-03 01:29:18 +03:00

Author

Owner

@dani-garcia commented on GitHub (Nov 2, 2019):

This is fixed in the latest commit github.com/dani-garcia/bitwarden_rs@e449912f05. You should delete the email or duo 2fa and then reenable it again for the changes to apply

@dani-garcia commented on GitHub (Nov 2, 2019): This is fixed in the latest commit https://github.com/dani-garcia/bitwarden_rs/commit/e449912f05d63a3499609ae00184796dd7390bf0. You should delete the email or duo 2fa and then reenable it again for the changes to apply