mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #5986] Unable to set YubiKey OTPs #2296
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2296
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @JYLN on GitHub (Jun 24, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5986
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Config:
Vaultwarden Build Version
v1.34.1
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Cloudflare Tunnel
Host/Server Operating System
NAS/SAN
Operating System Version
Synology DSM 7.2.2-72806 Update 3
Clients
Web Vault
Client Version
v2025.5.0
Steps To Reproduce
Expected Result
Yubikey OTP to save successfully without error
Actual Result
Receives a 'Invalid Yubikey OTP provided' error
Logs
Screenshots or Videos
No response
Additional Context
The Cloudflare tunnel setup is new, the vault used to just run on an NGINX Reverse Proxy container within my NAS but I recently switched to the Cloudflare tunnel because I am managing multiple other resources for my domain within Cloudflare. I used to have 2 Yubikey OTPs saved to my account but had to reset my Yubikeys recently. Upon resetting, I haven't been able to save any OTPs within Vaultwarden. I have regenerated my Client ID and Secret twice. I have attempted the using the normal secret and adding a
=based on another issue I found within the Github repo. I have explicitly set the server URL and unset the server URL for YubiKey. When testing the API within Postman and random nonce data, I am getting anOKresponse. Also, I have validated multiple OTPs on Yubikey's demo website. I did recently fix the IP header match, but that hasn't helped resolve my issue. I'm not entirely sure what I'm missing here. Thank you for any help in advance.@tsvico commented on GitHub (Jun 26, 2025):
Check your YUBICO_CLIENT_ID and YUBICO_SECRET_KEY. I had the same error as you before. When I reconfigured YUBICO_CLIENT_ID and YUBICO_SECRET_KEY, the error changed to
I can't solve the current problem
@tsvico commented on GitHub (Jun 26, 2025):
I passed the test at https://demo.yubico.com/otp/verify and my debug log is
If you have any ideas or solutions, please contact me
@BlackDex commented on GitHub (Jun 26, 2025):
It looks like the library handling the request thinks it is a bad reqwest for some reason.
Ill have to check and see why
@BlackDex commented on GitHub (Jun 26, 2025):
Hmm, the library it self seems to work just fine as-is. Have to check further
@BlackDex commented on GitHub (Jun 26, 2025):
Found the issue and fixed it.