starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00

[GH-ISSUE #675] failed to falidate DUO credentials #454

New issue

Closed

opened 2026-03-03 01:29:18 +03:00 by kerem · 9 comments

kerem commented

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

Owner

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

Hi, when trying to config the duo 2fa it keeps saying: failed to falidate duo credentials.
I did a complete new install.

Originally created by @Trigun on GitHub (Oct 18, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/675 Hi, when trying to config the duo 2fa it keeps saying: failed to falidate duo credentials. I did a complete new install.

kerem closed this issue

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

kerem commented

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

Author

Owner

@MartB commented on GitHub (Oct 20, 2019):

Did you set up the duo api credentials inside the configuration?

=> DUO_IKEY etc.

@MartB commented on GitHub (Oct 20, 2019): Did you set up the duo api credentials inside the configuration? => DUO_IKEY etc.

kerem commented

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

Author

Owner

@Trigun commented on GitHub (Oct 21, 2019):

yes, I setup:
The integration key
The Secret key
API -hostname

also, I had it working before but for some reason(maybe due to an update) I keep having the same error.

Thx for your help!

@Trigun commented on GitHub (Oct 21, 2019): yes, I setup: The integration key The Secret key API -hostname also, I had it working before but for some reason(maybe due to an update) I keep having the same error. Thx for your help!

kerem commented

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

Author

Owner

@Firestorrrm commented on GitHub (Oct 22, 2019):

Encountering the same error after a fresh install...

bitwarden_1  | [2019-10-22 19:37:08][bitwarden_rs::error][ERROR] Failed to validate Duo credentials.
bitwarden_1  | [CAUSE] Error(
bitwarden_1  |     Io(
bitwarden_1  |         Custom {
bitwarden_1  |             kind: TimedOut,
bitwarden_1  |             error: "timed out",
bitwarden_1  |         },
bitwarden_1  |     ),
bitwarden_1  |     "https://api-xxxxxx.duosecurity.com/auth/v2/check",
bitwarden_1  | )

Using the raspberry pi image.

@Firestorrrm commented on GitHub (Oct 22, 2019): Encountering the same error after a fresh install... ``` bitwarden_1 | [2019-10-22 19:37:08][bitwarden_rs::error][ERROR] Failed to validate Duo credentials. bitwarden_1 | [CAUSE] Error( bitwarden_1 | Io( bitwarden_1 | Custom { bitwarden_1 | kind: TimedOut, bitwarden_1 | error: "timed out", bitwarden_1 | }, bitwarden_1 | ), bitwarden_1 | "https://api-xxxxxx.duosecurity.com/auth/v2/check", bitwarden_1 | ) ``` Using the raspberry pi image.

kerem commented

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

Author

Owner

@Trigun commented on GitHub (Oct 23, 2019):

Apperantly the authenticator app also doesn't work.

hopefully it will be fixed soon as 2FA is crucial for a tool like this.

thnx!

@Trigun commented on GitHub (Oct 23, 2019): Apperantly the authenticator app also doesn't work. hopefully it will be fixed soon as 2FA is crucial for a tool like this. thnx!

kerem commented

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

Author

Owner

@shauder commented on GitHub (Oct 23, 2019):

Duo is working fine for me. Do you have it setup through the admin page or did you set it up at the user level?

I have mine just configured for my user since I am using my own personal duo and others can use theirs.

EDIT: I was on 1.9.1-8be2ed62 and I upgraded to 1.11.0-5ac66b05 and Duo is still working for me.

@shauder commented on GitHub (Oct 23, 2019): Duo is working fine for me. Do you have it setup through the admin page or did you set it up at the user level? I have mine just configured for my user since I am using my own personal duo and others can use theirs. EDIT: I was on 1.9.1-8be2ed62 and I upgraded to 1.11.0-5ac66b05 and Duo is still working for me.

kerem commented

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

Author

Owner

@Trigun commented on GitHub (Oct 28, 2019):

Duo is working fine for me. Do you have it setup through the admin page or did you set it up at the user level?

I have mine just configured for my user since I am using my own personal duo and others can use theirs.

EDIT: I was on 1.9.1-8be2ed62 and I upgraded to 1.11.0-5ac66b05 and Duo is still working for me.

With an upgrade it should work but with a new install it doesn't work. not sure why as I've tried older versions as well. not sure where it goes wrong.

@Trigun commented on GitHub (Oct 28, 2019): > Duo is working fine for me. Do you have it setup through the admin page or did you set it up at the user level? > > I have mine just configured for my user since I am using my own personal duo and others can use theirs. > > EDIT: I was on 1.9.1-8be2ed62 and I upgraded to 1.11.0-5ac66b05 and Duo is still working for me. With an upgrade it should work but with a new install it doesn't work. not sure why as I've tried older versions as well. not sure where it goes wrong.

kerem commented

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

Author

Owner

@Trigun commented on GitHub (Nov 7, 2019):

issue is solved! to solve it check if the time is in sync with(for example) with your logfile output.
If not, just do a hwclock tot sytem sync and it will work once you try to setup the 2fa

@Trigun commented on GitHub (Nov 7, 2019): issue is solved! to solve it check if the time is in sync with(for example) with your logfile output. If not, just do a hwclock tot sytem sync and it will work once you try to setup the 2fa

kerem commented

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

Author

Owner

@shauder commented on GitHub (Nov 7, 2019):

This is a common problem with any 2FA solutions.

@shauder commented on GitHub (Nov 7, 2019): This is a common problem with any 2FA solutions.

kerem commented

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

Author

Owner

@Trigun commented on GitHub (Nov 8, 2019):

This is a common problem with any 2FA solutions.

I know, but for some reason I never checked the time assuming once its set correclty is should always work. glad its fixed now :)

@Trigun commented on GitHub (Nov 8, 2019): > This is a common problem with any 2FA solutions. I know, but for some reason I never checked the time assuming once its set correclty is should always work. glad its fixed now :)