mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #1758] Unable to connect to vaultwarden via Bitwarden CLI #1048
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#1048
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 @blasphemite on GitHub (Jun 8, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1758
Subject of the issue
I'm not sure if this error originates from Bitwarden CLI or from a misconfiguration of Vaultwarden.
I created a Vaultwarden instance and tried to log in via Bitwarden CLI, but I receive the error:
request to https://vault.domain.example/api/accounts/prelogin failed, reason: unable to verify the first certificateVaultwarden itself shouldn't be dealing with the SSL; I use Caddy as a reverse proxy in front of Vaultwarden. On Caddy, I'm serving a wildcard certificate signed by a custom Root CA. This CA is successfully added to the cert store on the Ubuntu host I'm using for Bitwarden CLI.
Again, I'm not sure if this error originates from Bitwarden CLI or from a misconfiguration of Vaultwarden.
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Steps to reproduce
I started Vaultwarden simply with the configuration above.
I used the bitwarden-cli binary provided on their website, configured it to my selfhosted instance, and attempted to log in, at which point I received the error.
Expected behaviour
I expected to either pass or fail the authentication based on credentials I provided.
Actual behaviour
I receive the error when logging in, irrespective of whether or not the credentials I provide are legitimate. I can enter a gibberish standard email address and a random password and I get the same error as when I enter my true email address and real password,
Troubleshooting data