-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Description
Steps To Reproduce
I followed the standard installation process in the documentation for a self-hosted installation, and there were no differences in any of the steps.
Whether using the passkey as an MFA key or a passwordless login key, a server error is displayed during saving.
However, using the yubikey app to view the credentials on the yubikey shows that bitwarden has successfully written the user credentials.
Expected Result
1
Actual Result
1
Screenshots or Videos
No response
Additional Context
No response
Build Version
Bitwarden server 2025.11.0
Environment
Self-Hosted
Environment Details
SERVER ENV
Centos7.9 on ESXI 8
Docker CE 26.1.4
Bitwarden server image 2025.11.0
CLIENT ENV
Windows 10 Pro 22H2 19045.6575
YubiKey 5 fw-5.7.4
Kensington K62330 fingerprint
To clarify, I enabled Windows Hello on Windows and used the k62330 for Windows login, but I did not use it as a passkey for the Bitwarden service.
Issue Tracking Info
- I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.