failed to falidate DUO credentials #455

New Issue

Closed

opened 2026-02-04 20:38:03 +03:00 by OVERLORD · 9 comments

OVERLORD commented 2026-02-04 20:38:03 +03:00

Owner

Copy Link

Originally created by @Trigun on GitHub (Oct 18, 2019).

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). Hi, when trying to config the duo 2fa it keeps saying: failed to falidate duo credentials. I did a complete new install.

OVERLORD closed this issue 2026-02-04 20:38:13 +03:00

OVERLORD commented 2026-02-04 20:38:17 +03:00

Author

Owner

Copy Link

@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.

OVERLORD commented 2026-02-04 20:38:24 +03:00

Author

Owner

Copy Link

@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!

OVERLORD commented 2026-02-04 20:38:28 +03:00

Author

Owner

Copy Link

@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.

OVERLORD commented 2026-02-04 20:38:36 +03:00

Author

Owner

Copy Link

@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!

OVERLORD commented 2026-02-04 20:38:45 +03:00

Author

Owner

Copy Link

@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.

OVERLORD commented 2026-02-04 20:38:57 +03:00

Author

Owner

Copy Link

@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.

OVERLORD commented 2026-02-04 20:39:00 +03:00

Author

Owner

Copy Link

@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

OVERLORD commented 2026-02-04 20:39:04 +03:00

Author

Owner

Copy Link

@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.

OVERLORD commented 2026-02-04 20:39:10 +03:00

Author

Owner

Copy Link

@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 :)

OVERLORD referenced this issue 2026-02-05 04:54:09 +03:00

[PR #455] [MERGED] Add new endpoint for retrieving all users #2710

OVERLORD referenced this issue 2026-02-05 04:54:10 +03:00

[PR #456] [CLOSED] Add get invites endpoint #2711

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

cached-config-operations

test_dylint

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 Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

OVERLORD

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#455