github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-05-22 16:14:20 -05:00
Code Issues 307 Packages Projects Releases 83 Wiki Activity

Cannot create Recovery Code #4090

New Issue
Closed
opened 2026-03-07 19:28:09 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-03-07 19:28:09 -06:00
Owner
Copy Link

Originally created by @paradeiser on GitHub (Oct 16, 2019).

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). 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
GiteaMirror commented 2026-03-07 19:28:10 -06:00
Author
Owner
Copy Link

@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.
GiteaMirror commented 2026-03-07 19:28:10 -06:00
Author
Owner
Copy Link

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

This is fixed in the latest commit 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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#4090
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?