starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00
Code Issues 39 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #420] 2FA Failing when Opening Web Vault #244

New issue
Closed
opened 2026-03-03 01:27:10 +03:00 by kerem · 8 comments
kerem commented 2026-03-03 01:27:10 +03:00
Owner
Copy link

Originally created by @kmwoley on GitHub (Feb 28, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/420

Setup:
Running the latest docker image (version 2.8.0 reported by the web ui)
I have my account successfully setup using 2FA with a Yubikey NFC 5.

Previously:
I've successfully logged in using 2FA on both mobile (iPhone) and via the webvault. I believe the error has started after I've updated to the most recent docker image.

Error:
Now, when I attempt to log in I get "An error has occurred. An unexpected error has occurred." error in the UI, and the error logs show the errors below).

[2019-02-28 08:04:57][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8:
[2019-02-28 08:04:57][_][INFO] Matched: POST /api/accounts/prelogin (prelogin)
[2019-02-28 08:04:57][_][INFO] Outcome: Success
[2019-02-28 08:04:57][_][INFO] Response succeeded.
[2019-02-28 08:04:57][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8:
[2019-02-28 08:04:57][_][INFO] Matched: POST /identity/connect/token (login)
[2019-02-28 08:04:57][bitwarden_rs::error][ERROR] JsonError. {"TwoFactorProviders":[3],"TwoFactorProviders2":{"3":{"Nfc":true}},"error":"invalid_grant","error_description":"Two factor required."}
[2019-02-28 08:04:57][_][INFO] Outcome: Success
[2019-02-28 08:04:57][_][INFO] Response succeeded.
[2019-02-28 08:05:06][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8:
[2019-02-28 08:05:06][_][INFO] Matched: POST /identity/connect/token (login)
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }', src/libcore/result.rs:997:5
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }', src/libcore/result.rs:997:5
thread 'main' panicked at 'internal error: entered unreachable code: the call to `handle_threads` should block on success', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rocket-0.4.0/src/rocket.rs:725:13
Originally created by @kmwoley on GitHub (Feb 28, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/420 Setup: Running the latest docker image (version 2.8.0 reported by the web ui) I have my account successfully setup using 2FA with a Yubikey NFC 5. Previously: I've successfully logged in using 2FA on both mobile (iPhone) and via the webvault. I believe the error has started after I've updated to the most recent docker image. Error: Now, when I attempt to log in I get "An error has occurred. An unexpected error has occurred." error in the UI, and the error logs show the errors below). ``` [2019-02-28 08:04:57][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8: [2019-02-28 08:04:57][_][INFO] Matched: POST /api/accounts/prelogin (prelogin) [2019-02-28 08:04:57][_][INFO] Outcome: Success [2019-02-28 08:04:57][_][INFO] Response succeeded. [2019-02-28 08:04:57][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8: [2019-02-28 08:04:57][_][INFO] Matched: POST /identity/connect/token (login) [2019-02-28 08:04:57][bitwarden_rs::error][ERROR] JsonError. {"TwoFactorProviders":[3],"TwoFactorProviders2":{"3":{"Nfc":true}},"error":"invalid_grant","error_description":"Two factor required."} [2019-02-28 08:04:57][_][INFO] Outcome: Success [2019-02-28 08:04:57][_][INFO] Response succeeded. [2019-02-28 08:05:06][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8: [2019-02-28 08:05:06][_][INFO] Matched: POST /identity/connect/token (login) thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }', src/libcore/result.rs:997:5 thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }', src/libcore/result.rs:997:5 thread 'main' panicked at 'internal error: entered unreachable code: the call to `handle_threads` should block on success', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rocket-0.4.0/src/rocket.rs:725:13 ```
kerem closed this issue 2026-03-03 01:27:10 +03:00
kerem commented 2026-03-03 01:27:11 +03:00
Author
Owner
Copy link

@kmwoley commented on GitHub (Feb 28, 2019):

Something deeper is going on; I attempted to restart the docker container and it will no-longer start with the following (similar) error:

[2019-02-28 08:05:06][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8:
[2019-02-28 08:05:06][_][INFO] Matched: POST /identity/connect/token (login)
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }', src/libcore/result.rs:997:5
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }', src/libcore/result.rs:997:5
thread 'main' panicked at 'internal error: entered unreachable code: the call to `handle_threads` should block on success', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rocket-0.4.0/src/rocket.rs:725:13
<!-- gh-comment-id:468335016 --> @kmwoley commented on GitHub (Feb 28, 2019): Something deeper is going on; I attempted to restart the docker container and it will no-longer start with the following (similar) error: ``` [2019-02-28 08:05:06][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8: [2019-02-28 08:05:06][_][INFO] Matched: POST /identity/connect/token (login) thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }', src/libcore/result.rs:997:5 thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }', src/libcore/result.rs:997:5 thread 'main' panicked at 'internal error: entered unreachable code: the call to `handle_threads` should block on success', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/rocket-0.4.0/src/rocket.rs:725:13 ```
kerem commented 2026-03-03 01:27:11 +03:00
Author
Owner
Copy link

@dani-garcia commented on GitHub (Feb 28, 2019):

This error seems to be coming from the Rocket web server, when attempting to start. It shouldn't be because any change we made, I don't think.

Did you make any changes to the docker container networking? Maybe you are trying to bind the port to one that's already bound to another container or something like that? Or maybe you have multiple instances of bitwarden_rs running?

<!-- gh-comment-id:468338684 --> @dani-garcia commented on GitHub (Feb 28, 2019): This error seems to be coming from the Rocket web server, when attempting to start. It shouldn't be because any change we made, I don't think. Did you make any changes to the docker container networking? Maybe you are trying to bind the port to one that's already bound to another container or something like that? Or maybe you have multiple instances of bitwarden_rs running?
kerem commented 2026-03-03 01:27:11 +03:00
Author
Owner
Copy link

@mprasil commented on GitHub (Mar 1, 2019):

Do you use --net host or something similar in your docker run by any chance @kmwoley? Normally the application runs in its own network namespace, so already used port is kinda strange.

<!-- gh-comment-id:468622945 --> @mprasil commented on GitHub (Mar 1, 2019): Do you use `--net host` or something similar in your docker run by any chance @kmwoley? Normally the application runs in its own network namespace, so already used port is kinda strange.
kerem commented 2026-03-03 01:27:12 +03:00
Author
Owner
Copy link

@kmwoley commented on GitHub (Mar 1, 2019):

I suspect this is due to my docker network config, too. I found a change in
my host OS that may be causing it. Let’s close out this issue as I also
think it’s not a bitwarden_rs isssue. I’ll reopen/comment on it if I can
prove otherwise. Thanks!

On Fri, Mar 1, 2019 at 2:41 AM mprasil notifications@github.com wrote:

Do you use --net host or something similar in your docker run by any
chance @kmwoley https://github.com/kmwoley? Normally the application
runs in its own network namespace, so already used port is kinda strange.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/dani-garcia/bitwarden_rs/issues/420#issuecomment-468622945,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF1jeOQbSnXADYrlaBE90JFgc13QeuVVks5vSQPpgaJpZM4bXLf-
.

<!-- gh-comment-id:468677998 --> @kmwoley commented on GitHub (Mar 1, 2019): I suspect this is due to my docker network config, too. I found a change in my host OS that may be causing it. Let’s close out this issue as I also think it’s not a bitwarden_rs isssue. I’ll reopen/comment on it if I can prove otherwise. Thanks! On Fri, Mar 1, 2019 at 2:41 AM mprasil <notifications@github.com> wrote: > Do you use --net host or something similar in your docker run by any > chance @kmwoley <https://github.com/kmwoley>? Normally the application > runs in its own network namespace, so already used port is kinda strange. > > — > You are receiving this because you were mentioned. > > > Reply to this email directly, view it on GitHub > <https://github.com/dani-garcia/bitwarden_rs/issues/420#issuecomment-468622945>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AF1jeOQbSnXADYrlaBE90JFgc13QeuVVks5vSQPpgaJpZM4bXLf-> > . >
kerem commented 2026-03-03 01:27:12 +03:00
Author
Owner
Copy link

@kmwoley commented on GitHub (Mar 3, 2019):

Confirmed. This had nothing to do with bitwarden_rs. Sorry for the noise.

<!-- gh-comment-id:468972974 --> @kmwoley commented on GitHub (Mar 3, 2019): Confirmed. This had nothing to do with bitwarden_rs. Sorry for the noise.
kerem commented 2026-03-03 01:27:12 +03:00
Author
Owner
Copy link

@bronco21016 commented on GitHub (Jun 24, 2019):

Sorry to bring this back. How did you solve it? I’m getting the exact same error messages when trying to setup a Yubikey on Bitwarden_RS pulled from Archlinux AUR.

<!-- gh-comment-id:505150917 --> @bronco21016 commented on GitHub (Jun 24, 2019): Sorry to bring this back. How did you solve it? I’m getting the exact same error messages when trying to setup a Yubikey on Bitwarden_RS pulled from Archlinux AUR.
kerem commented 2026-03-03 01:27:12 +03:00
Author
Owner
Copy link

@kmwoley commented on GitHub (Jun 25, 2019):

@bronco21016 IIRC, my host OS had made a bad upgrade to Docker that screwed up MACVLAN. Networking was the source of my issue. I rolled back my OS version and solved it, reported it to the OS maintainers, and it got fixed.

<!-- gh-comment-id:505476335 --> @kmwoley commented on GitHub (Jun 25, 2019): @bronco21016 IIRC, my host OS had made a bad upgrade to Docker that screwed up MACVLAN. Networking was the source of my issue. I rolled back my OS version and solved it, reported it to the OS maintainers, and it got fixed.
kerem commented 2026-03-03 01:27:12 +03:00
Author
Owner
Copy link

@bronco21016 commented on GitHub (Jun 25, 2019):

@kmwoley It seems I’m having a network issue as well but can’t quite trace it down. Shouldn’t be related to Docker though as I’m not using Docker. Seems more related to my Apache reverse proxy. Oh well. I’ll post something separate to see if I can get some help. Thanks again!

<!-- gh-comment-id:505509937 --> @bronco21016 commented on GitHub (Jun 25, 2019): @kmwoley It seems I’m having a network issue as well but can’t quite trace it down. Shouldn’t be related to Docker though as I’m not using Docker. Seems more related to my Apache reverse proxy. Oh well. I’ll post something separate to see if I can get some help. Thanks again!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
revert-7033-patch-1
cached-config-operations
test_dylint
1.35.8
1.35.7
1.35.6
1.35.5
1.35.4
1.35.3
1.35.2
1.35.1
1.35.0
1.34.3
1.34.2
1.34.1
1.34.0
1.33.2
1.33.1
1.33.0
1.32.7
1.32.6
1.32.5
1.32.4
1.32.3
1.32.2
1.32.1
1.32.0
1.31.0
1.30.5
1.30.4
1.30.3
1.30.2
1.30.1
1.30.0
1.29.2
1.29.1
1.29.0
1.28.1
1.28.0
1.27.0
1.26.0
1.25.2
1.25.1
1.25.0
1.24.0
1.23.1
1.23.0
1.22.2
1.22.1
1.22.0
1.21.0
1.20.0
1.19.0
1.18.0
1.17.0
1.16.3
1.16.2
1.16.1
1.16.0
1.15.1
1.15.0
1.14.2
1.14.1
1.14
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.0
1.6.1
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
0.13.0
0.12.0
0.11.0
0.10.0
0.9.0
Labels
Clear labels   
SSO

   
Third party

   
better for forum

   
bug

   
bug

   
documentation

   
duplicate

   
enhancement

   
future Vault

   
future Vault

   
future Vault

   
good first issue

   
help wanted

   
low priority

   
notes

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
troubleshooting

   
wontfix
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#244
No description provided.