starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Bitwarden CLI (version 1.22.0) login to the Vaultwarden server fails even with correct credentials #1237

New Issue
Closed
opened 2026-02-05 00:21:14 +03:00 by OVERLORD · 21 comments
OVERLORD commented 2026-02-05 00:21:14 +03:00
Owner
Copy Link

Originally created by @lgp171188 on GitHub (Mar 20, 2022).

Subject of the issue

Bitwarden CLI (version 1.22.0 - the latest on Arch Linux) login to the Vaultwarden server fails even with correct credentials

Deployment environment

Your environment (Generated via diagnostics page)

  • Vaultwarden version: v1.24.0
  • Web-vault version: v2.25.1
  • Running within Docker: true (Base: Debian)
  • Environment settings overridden: false
  • Uses a reverse proxy: true
  • IP Header check: true (X-Real-IP)
  • Internet access: true
  • Internet access via a proxy: false
  • DNS Check: true
  • Time Check: true
  • Domain Configuration Check: false
  • HTTPS Check: false
  • Database type: MySQL
  • Database version: 10.5.15-MariaDB-log
  • Clients used: Bitwarden CLI version 1.22.0
  • Reverse proxy and version: Nginx (latest from lscr.io/linuxserver/swag)
  • Other relevant information:

Config (Generated via diagnostics page)

Show Running Config

Environment settings which are overridden:

{
  "_duo_akey": null,
  "_enable_duo": false,
  "_enable_email_2fa": true,
  "_enable_smtp": true,
  "_enable_yubico": true,
  "_ip_header_enabled": true,
  "admin_ratelimit_max_burst": 3,
  "admin_ratelimit_seconds": 300,
  "admin_token": "***",
  "allowed_iframe_ancestors": "",
  "attachments_folder": "data/attachments",
  "authenticator_disable_time_drift": false,
  "data_folder": "data",
  "database_max_conns": 10,
  "database_url": "*****://***********:*************@*******/***********",
  "db_connection_retries": 15,
  "disable_2fa_remember": false,
  "disable_admin_token": false,
  "disable_icon_download": false,
  "domain": "****://*********",
  "domain_origin": "****://*********",
  "domain_path": "",
  "domain_set": false,
  "duo_host": null,
  "duo_ikey": null,
  "duo_skey": null,
  "email_attempts_limit": 3,
  "email_expiration_time": 600,
  "email_token_size": 6,
  "emergency_access_allowed": true,
  "emergency_notification_reminder_schedule": "0 5 * * * *",
  "emergency_request_timeout_schedule": "0 5 * * * *",
  "enable_db_wal": true,
  "extended_logging": true,
  "helo_name": null,
  "hibp_api_key": null,
  "icon_blacklist_non_global_ips": true,
  "icon_blacklist_regex": null,
  "icon_cache_folder": "data/icon_cache",
  "icon_cache_negttl": 259200,
  "icon_cache_ttl": 2592000,
  "icon_download_timeout": 10,
  "icon_redirect_code": 302,
  "icon_service": "internal",
  "incomplete_2fa_schedule": "30 * * * * *",
  "incomplete_2fa_time_limit": 3,
  "invitation_org_name": "Vaultwarden",
  "invitations_allowed": false,
  "ip_header": "X-Real-IP",
  "job_poll_interval_ms": 30000,
  "log_file": null,
  "log_level": "Info",
  "log_timestamp_format": "%Y-%m-%d %H:%M:%S.%3f",
  "login_ratelimit_max_burst": 10,
  "login_ratelimit_seconds": 60,
  "org_attachment_limit": null,
  "org_creation_users": "",
  "password_iterations": 100000,
  "reload_templates": false,
  "require_device_email": false,
  "rsa_key_filename": "data/rsa_key",
  "send_purge_schedule": "0 5 * * * *",
  "sends_allowed": true,
  "sends_folder": "data/sends",
  "show_password_hint": false,
  "signups_allowed": false,
  "signups_domains_whitelist": "",
  "signups_verify": false,
  "signups_verify_resend_limit": 6,
  "signups_verify_resend_time": 3600,
  "smtp_accept_invalid_certs": false,
  "smtp_accept_invalid_hostnames": false,
  "smtp_auth_mechanism": null,
  "smtp_debug": false,
  "smtp_explicit_tls": false,
  "smtp_from": "*********@***.**",
  "smtp_from_name": "Vaultwarden",
  "smtp_host": "**********",
  "smtp_password": null,
  "smtp_port": 8025,
  "smtp_ssl": false,
  "smtp_timeout": 15,
  "smtp_username": null,
  "templates_folder": "data/templates",
  "trash_auto_delete_days": null,
  "trash_purge_schedule": "0 5 0 * * *",
  "use_syslog": false,
  "user_attachment_limit": null,
  "web_vault_enabled": true,
  "web_vault_folder": "web-vault/",
  "websocket_address": "0.0.0.0",
  "websocket_enabled": true,
  "websocket_port": 3012,
  "yubico_client_id": null,
  "yubico_secret_key": null,
  "yubico_server": null
}
  • vaultwarden version: 1.24.0

  • Install method: Official docker image using docker-compose

  • Clients used:
    Bitwarden CLI 1.22.0

  • Reverse proxy and version:
    Nginx (the latest version from lscr.io/linuxserver.io/swag)

  • MySQL/MariaDB or PostgreSQL version: MariaDB 10.5.15 (lscr.io/linuxserver/mariadb docker container)

  • Other relevant details:

Steps to reproduce

  • Start the latest version of vaultwarden using docker-compose.
  • Log in to an existing account in the web UI. Verify that it works.
  • Install the Bitwarden CLI version 1.22.0 (the latest version on Arch Linux). Try logging in using the same credentials after running bw login.
  • The login attempt fails and an error that says Username or password is incorrect. Try again is printed.

Expected behaviour

The login should succeed with the same credentials that work for the web vault login.

Actual behaviour

The login errors out.

Troubleshooting data

Relevant log lines related to this issue from the Docker container logs.

The logs for the CLI login failure

vaultwarden                           | [2022-03-20 08:35:22.365][request][INFO] POST /identity/accounts/prelogin
vaultwarden                           | [2022-03-20 08:35:22.365][response][INFO] 404 Not Found
vaultwarden                           | [2022-03-20 08:35:22.862][request][INFO] POST /identity/connect/token
vaultwarden                           | [2022-03-20 08:35:22.902][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: <A.B.C.D>. Username: <email address placeholder>
vaultwarden                           | [2022-03-20 08:35:22.902][response][INFO] POST /identity/connect/token (login) => 400 Bad Request

The logs for the web vault successful login with the same credentials.

vaultwarden                           | [2022-03-20 08:36:57.604][request][INFO] POST /api/accounts/prelogin
vaultwarden                           | [2022-03-20 08:36:57.606][response][INFO] POST /api/accounts/prelogin (prelogin) => 200 OK
vaultwarden                           | [2022-03-20 08:36:57.795][request][INFO] POST /identity/connect/token
vaultwarden                           | [2022-03-20 08:36:57.911][vaultwarden::api::identity][INFO] User<email placeholder> logged in successfully. IP: <A.B.C.D>
vaultwarden                           | [2022-03-20 08:36:57.912][response][INFO] POST /identity/connect/token (login) => 200 OK
vaultwarden                           | [2022-03-20 08:36:58.136][request][INFO] POST /identity/connect/token
vaultwarden                           | [2022-03-20 08:36:58.136][request][INFO] POST /identity/connect/token
vaultwarden                           | [2022-03-20 08:36:58.150][response][INFO] POST /identity/connect/token (login) => 200 OK
vaultwarden                           | [2022-03-20 08:36:58.150][response][INFO] POST /identity/connect/token (login) => 200 OK
Originally created by @lgp171188 on GitHub (Mar 20, 2022). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue Bitwarden CLI (version 1.22.0 - the latest on Arch Linux) login to the Vaultwarden server fails even with correct credentials ### Deployment environment ### Your environment (Generated via diagnostics page) * Vaultwarden version: v1.24.0 * Web-vault version: v2.25.1 * Running within Docker: true (Base: Debian) * Environment settings overridden: false * Uses a reverse proxy: true * IP Header check: true (X-Real-IP) * Internet access: true * Internet access via a proxy: false * DNS Check: true * Time Check: true * Domain Configuration Check: false * HTTPS Check: false * Database type: MySQL * Database version: 10.5.15-MariaDB-log * Clients used: Bitwarden CLI version 1.22.0 * Reverse proxy and version: Nginx (latest from lscr.io/linuxserver/swag) * Other relevant information: ### Config (Generated via diagnostics page) <details><summary>Show Running Config</summary> **Environment settings which are overridden:** ```json { "_duo_akey": null, "_enable_duo": false, "_enable_email_2fa": true, "_enable_smtp": true, "_enable_yubico": true, "_ip_header_enabled": true, "admin_ratelimit_max_burst": 3, "admin_ratelimit_seconds": 300, "admin_token": "***", "allowed_iframe_ancestors": "", "attachments_folder": "data/attachments", "authenticator_disable_time_drift": false, "data_folder": "data", "database_max_conns": 10, "database_url": "*****://***********:*************@*******/***********", "db_connection_retries": 15, "disable_2fa_remember": false, "disable_admin_token": false, "disable_icon_download": false, "domain": "****://*********", "domain_origin": "****://*********", "domain_path": "", "domain_set": false, "duo_host": null, "duo_ikey": null, "duo_skey": null, "email_attempts_limit": 3, "email_expiration_time": 600, "email_token_size": 6, "emergency_access_allowed": true, "emergency_notification_reminder_schedule": "0 5 * * * *", "emergency_request_timeout_schedule": "0 5 * * * *", "enable_db_wal": true, "extended_logging": true, "helo_name": null, "hibp_api_key": null, "icon_blacklist_non_global_ips": true, "icon_blacklist_regex": null, "icon_cache_folder": "data/icon_cache", "icon_cache_negttl": 259200, "icon_cache_ttl": 2592000, "icon_download_timeout": 10, "icon_redirect_code": 302, "icon_service": "internal", "incomplete_2fa_schedule": "30 * * * * *", "incomplete_2fa_time_limit": 3, "invitation_org_name": "Vaultwarden", "invitations_allowed": false, "ip_header": "X-Real-IP", "job_poll_interval_ms": 30000, "log_file": null, "log_level": "Info", "log_timestamp_format": "%Y-%m-%d %H:%M:%S.%3f", "login_ratelimit_max_burst": 10, "login_ratelimit_seconds": 60, "org_attachment_limit": null, "org_creation_users": "", "password_iterations": 100000, "reload_templates": false, "require_device_email": false, "rsa_key_filename": "data/rsa_key", "send_purge_schedule": "0 5 * * * *", "sends_allowed": true, "sends_folder": "data/sends", "show_password_hint": false, "signups_allowed": false, "signups_domains_whitelist": "", "signups_verify": false, "signups_verify_resend_limit": 6, "signups_verify_resend_time": 3600, "smtp_accept_invalid_certs": false, "smtp_accept_invalid_hostnames": false, "smtp_auth_mechanism": null, "smtp_debug": false, "smtp_explicit_tls": false, "smtp_from": "*********@***.**", "smtp_from_name": "Vaultwarden", "smtp_host": "**********", "smtp_password": null, "smtp_port": 8025, "smtp_ssl": false, "smtp_timeout": 15, "smtp_username": null, "templates_folder": "data/templates", "trash_auto_delete_days": null, "trash_purge_schedule": "0 5 0 * * *", "use_syslog": false, "user_attachment_limit": null, "web_vault_enabled": true, "web_vault_folder": "web-vault/", "websocket_address": "0.0.0.0", "websocket_enabled": true, "websocket_port": 3012, "yubico_client_id": null, "yubico_secret_key": null, "yubico_server": null } ``` </details> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 1.24.0 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Official docker image using `docker-compose` * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> Bitwarden CLI 1.22.0 * Reverse proxy and version: Nginx (the latest version from lscr.io/linuxserver.io/swag) * MySQL/MariaDB or PostgreSQL version: MariaDB 10.5.15 (lscr.io/linuxserver/mariadb docker container) * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> * Start the latest version of `vaultwarden` using `docker-compose`. * Log in to an existing account in the web UI. Verify that it works. * Install the Bitwarden CLI version `1.22.0` (the latest version on Arch Linux). Try logging in using the same credentials after running `bw login`. * The login attempt fails and an error that says `Username or password is incorrect. Try again` is printed. ### Expected behaviour The login should succeed with the same credentials that work for the web vault login. ### Actual behaviour The login errors out. ### Troubleshooting data Relevant log lines related to this issue from the Docker container logs. The logs for the CLI login failure ``` vaultwarden | [2022-03-20 08:35:22.365][request][INFO] POST /identity/accounts/prelogin vaultwarden | [2022-03-20 08:35:22.365][response][INFO] 404 Not Found vaultwarden | [2022-03-20 08:35:22.862][request][INFO] POST /identity/connect/token vaultwarden | [2022-03-20 08:35:22.902][vaultwarden::api::identity][ERROR] Username or password is incorrect. Try again. IP: <A.B.C.D>. Username: <email address placeholder> vaultwarden | [2022-03-20 08:35:22.902][response][INFO] POST /identity/connect/token (login) => 400 Bad Request ``` The logs for the web vault successful login with the same credentials. ``` vaultwarden | [2022-03-20 08:36:57.604][request][INFO] POST /api/accounts/prelogin vaultwarden | [2022-03-20 08:36:57.606][response][INFO] POST /api/accounts/prelogin (prelogin) => 200 OK vaultwarden | [2022-03-20 08:36:57.795][request][INFO] POST /identity/connect/token vaultwarden | [2022-03-20 08:36:57.911][vaultwarden::api::identity][INFO] User<email placeholder> logged in successfully. IP: <A.B.C.D> vaultwarden | [2022-03-20 08:36:57.912][response][INFO] POST /identity/connect/token (login) => 200 OK vaultwarden | [2022-03-20 08:36:58.136][request][INFO] POST /identity/connect/token vaultwarden | [2022-03-20 08:36:58.136][request][INFO] POST /identity/connect/token vaultwarden | [2022-03-20 08:36:58.150][response][INFO] POST /identity/connect/token (login) => 200 OK vaultwarden | [2022-03-20 08:36:58.150][response][INFO] POST /identity/connect/token (login) => 200 OK ```
OVERLORD added the enhancementbugfuture Vault labels 2026-02-05 00:21:14 +03:00
OVERLORD commented 2026-02-05 00:21:23 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Mar 20, 2022):

I had the same thing when i tried to login with an expired token.
When i did a logout first and a re-login it all seemed to work fine.
A bw sync works too.

Please try to do a full logout and login and see what happens.

@BlackDex commented on GitHub (Mar 20, 2022): I had the same thing when i tried to login with an expired token. When i did a logout first and a re-login it all seemed to work fine. A `bw sync` works too. Please try to do a full logout and login and see what happens.
OVERLORD commented 2026-02-05 00:21:27 +03:00
Author
Owner
Copy Link

@lgp171188 commented on GitHub (Mar 20, 2022):

@BlackDex, the issue started happening only after the CLI version upgrade (I think) and I did a full logout to get a fresh token (which I needed to use in another tool that I use). Now when I run bw logout, it says that I am already logged out. Due to this issue, I am unable to log in or run any command like bw sync which requires the user to be logged in. Hence the report.

I am trying to login with my email address and account password. I am not using any other alternative authentication mechanisms.

@lgp171188 commented on GitHub (Mar 20, 2022): @BlackDex, the issue started happening only after the CLI version upgrade (I think) and I did a full logout to get a fresh token (which I needed to use in another tool that I use). Now when I run `bw logout`, it says that I am already logged out. Due to this issue, I am unable to log in or run any command like `bw sync` which requires the user to be logged in. Hence the report. I am trying to login with my email address and account password. I am not using any other alternative authentication mechanisms.
OVERLORD commented 2026-02-05 00:21:33 +03:00
Author
Owner
Copy Link

@lgp171188 commented on GitHub (Mar 20, 2022):

I am able to log in with the API key method but the username/password method still errors out. The API key method doesn't give me a session key to use with other applications. :(

@lgp171188 commented on GitHub (Mar 20, 2022): I am able to log in with the API key method but the username/password method still errors out. The API key method doesn't give me a session key to use with other applications. :(
OVERLORD commented 2026-02-05 00:21:40 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Mar 20, 2022):

Strange it works for me without any issues.

@BlackDex commented on GitHub (Mar 20, 2022): Strange it works for me without any issues.
OVERLORD commented 2026-02-05 00:21:45 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Mar 20, 2022):

Could you test this on vault.bitwarden.com for example and see if it fails there too?
And if not, what happens if you reconfigure it for your server again?

@BlackDex commented on GitHub (Mar 20, 2022): Could you test this on `vault.bitwarden.com` for example and see if it fails there too? And if not, what happens if you reconfigure it for your server again?
OVERLORD commented 2026-02-05 00:21:51 +03:00
Author
Owner
Copy Link

@lgp171188 commented on GitHub (Mar 20, 2022):

@BlackDex, I do not have an account on the official Bitwarden instance. So I will create one, test this out and then try switching back to my self-hosted instance. Will report the findings once I finish this.

@lgp171188 commented on GitHub (Mar 20, 2022): @BlackDex, I do not have an account on the official Bitwarden instance. So I will create one, test this out and then try switching back to my self-hosted instance. Will report the findings once I finish this.
OVERLORD commented 2026-02-05 00:21:53 +03:00
Author
Owner
Copy Link

@lgp171188 commented on GitHub (Mar 20, 2022):

I tried this and here's what happened.

  • When I tried to log in to vault.bitwarden.com from the CLI with my email and password, it also prompted me for the API secret and logged me in only after that. Just to confirm that this was not a one-time/first-time thing, I logged out and logged in again. I still saw the same prompt for the API secret.
  • Then I switched to my self-hosted instance and tried logging in with my email and password. I get the same error reported in this issue.

If it will help debug this further, I can share the details of my self-hosted instance where you can try creating an account and try reproducing the issue.

@lgp171188 commented on GitHub (Mar 20, 2022): I tried this and here's what happened. * When I tried to log in to vault.bitwarden.com from the CLI with my email and password, it also prompted me for the API secret and logged me in only after that. Just to confirm that this was not a one-time/first-time thing, I logged out and logged in again. I still saw the same prompt for the API secret. * Then I switched to my self-hosted instance and tried logging in with my email and password. I get the same error reported in this issue. If it will help debug this further, I can share the details of my self-hosted instance where you can try creating an account and try reproducing the issue.
OVERLORD commented 2026-02-05 00:22:00 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Mar 20, 2022):

I'm afraid this is an issue with the the Arch Linux version.
I just tested it my self (I also use Arch Linux) and it breaks for me.
I had the snap version installed which works fine.
Also, if i download the zip file from here: https://github.com/bitwarden/cli/releases/tag/v1.22.0 that one works fine too.

If I build the PKG my self, it also breaks. This either is because Arch is using a newer version of NPM, or it is not using the correct jslib commit which uses a different API endpoint.

Because if this, i will see if i can add this, but that still means the bitwarden-cli build by Arch is different then the one build by Bitwarden them selfs.

Small edit:
I have this fixed now in a local build.

@BlackDex commented on GitHub (Mar 20, 2022): I'm afraid this is an issue with the the Arch Linux version. I just tested it my self (I also use Arch Linux) and it breaks for me. I had the snap version installed which works fine. Also, if i download the zip file from here: https://github.com/bitwarden/cli/releases/tag/v1.22.0 that one works fine too. If I build the PKG my self, it also breaks. This either is because Arch is using a newer version of NPM, or it is not using the correct jslib commit which uses a different API endpoint. Because if this, i will see if i can add this, but that still means the bitwarden-cli build by Arch is different then the one build by Bitwarden them selfs. Small edit: I have this fixed now in a local build.
OVERLORD commented 2026-02-05 00:22:08 +03:00
Author
Owner
Copy Link

@lgp171188 commented on GitHub (Mar 20, 2022):

@BlackDex, thank you for taking the time to investigate this and finding out the issue and coming up with the fix. Based on your feedback, is reporting a bug on the Arch Linux package the best next step?

@lgp171188 commented on GitHub (Mar 20, 2022): @BlackDex, thank you for taking the time to investigate this and finding out the issue and coming up with the fix. Based on your feedback, is reporting a bug on the Arch Linux package the best next step?
OVERLORD commented 2026-02-05 00:22:16 +03:00
Author
Owner
Copy Link

@lgp171188 commented on GitHub (Mar 20, 2022):

I have reported a bug against the Arch Linux package - https://bugs.archlinux.org/task/74175

@lgp171188 commented on GitHub (Mar 20, 2022): I have reported a bug against the Arch Linux package - https://bugs.archlinux.org/task/74175
OVERLORD commented 2026-02-05 00:22:18 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Mar 20, 2022):

I have reported a bug against the Arch Linux package - https://bugs.archlinux.org/task/74175

Great. I just looked at the commits of jslib and it looks like it is a change that is for the future. And looking at the PKGBUILD file, it seems to always pull the latest jslib in instead of using the commit-hash linked to the tagged cli version.

@BlackDex commented on GitHub (Mar 20, 2022): > I have reported a bug against the Arch Linux package - https://bugs.archlinux.org/task/74175 Great. I just looked at the commits of jslib and it looks like it is a change that is for the future. And looking at the PKGBUILD file, it seems to always pull the latest jslib in instead of using the commit-hash linked to the tagged cli version.
OVERLORD commented 2026-02-05 00:22:20 +03:00
Author
Owner
Copy Link

@kpcyrd commented on GitHub (Mar 22, 2022):

The jslib dependency is set to the right commit when the submodule is setup, cloning the bitwarden-cli repo and following the setup instructions doesn't work either, maybe it's a problem with the node version?

@kpcyrd commented on GitHub (Mar 22, 2022): The jslib dependency is set to the right commit when the submodule is setup, cloning the bitwarden-cli repo and following the setup instructions doesn't work either, maybe it's a problem with the node version?
OVERLORD commented 2026-02-05 00:22:26 +03:00
Author
Owner
Copy Link

@ph0 commented on GitHub (Mar 22, 2022):

I am not sure if this is the same issue.
I am running © 2022, Bitwarden Inc. (Powered by Vaultwarden)
Version 2.25.1

Earlier today I logged in and my logins were not showing because there was a notification asking me to click the button to update encryption.

I updated, was logged out, and now when I try to login I get an error

"An error has occurred.
Could not send login notification email. Please contact your administrator."

@ph0 commented on GitHub (Mar 22, 2022): I am not sure if this is the same issue. I am running [© 2022, Bitwarden Inc. (Powered by Vaultwarden) Version 2.25.1 ](url) Earlier today I logged in and my logins were not showing because there was a notification asking me to click the button to update encryption. I updated, was logged out, and now when I try to login I get an error "An error has occurred. Could not send login notification email. Please contact your administrator."
OVERLORD commented 2026-02-05 00:22:29 +03:00
Author
Owner
Copy Link

@ph0 commented on GitHub (Mar 22, 2022):

Okay it suddenly works again. I must note it was broken in this way for at least 14 hours. Cheers to whoever fixed this.

@ph0 commented on GitHub (Mar 22, 2022): Okay it suddenly works again. I must note it was broken in this way for at least 14 hours. Cheers to whoever fixed this.
OVERLORD commented 2026-02-05 00:22:31 +03:00
Author
Owner
Copy Link

@alex19EP commented on GitHub (Mar 22, 2022):

hello, Arch Linux package maintainer here.

I don't quite understand the cause of the problem yet. I tried using the same version of nodejs as the official bitwarden-cli, but that didn't work. I am sure that the correct commit in jslib is used during the build. if someone has more information - I will be grateful.

@alex19EP commented on GitHub (Mar 22, 2022): hello, Arch Linux package maintainer here. I don't quite understand the cause of the problem yet. I tried using the same version of nodejs as the official bitwarden-cli, but that didn't work. I am sure that the correct commit in jslib is used during the build. if someone has more information - I will be grateful.
OVERLORD commented 2026-02-05 00:22:32 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Mar 22, 2022):

@alex19EP I'm not sure what the issue could be.
But the snap version and the Github Actions build version do seem to work and not use the new endpoint.
So maybe they did something strange during the build of the cli there.

I only wonder why you have the jslib as an extra download in the PKGBUILD.
Because this should do the trick just fine:

source=(bitwarden-cli::git+https://github.com/bitwarden/cli.git#tag=v${pkgver})
sha512sums=('SKIP')

prepare() {
	cd bitwarden-cli
	# Link jslib
	git submodule update --init
}
@BlackDex commented on GitHub (Mar 22, 2022): @alex19EP I'm not sure what the issue could be. But the snap version and the Github Actions build version do seem to work and not use the new endpoint. So maybe they did something strange during the build of the cli there. I only wonder why you have the jslib as an extra download in the PKGBUILD. Because this should do the trick just fine: ```bash source=(bitwarden-cli::git+https://github.com/bitwarden/cli.git#tag=v${pkgver}) sha512sums=('SKIP') prepare() { cd bitwarden-cli # Link jslib git submodule update --init } ```
OVERLORD commented 2026-02-05 00:22:34 +03:00
Author
Owner
Copy Link

@alex19EP commented on GitHub (Mar 22, 2022):

I only wonder why you have the jslib as an extra download in the PKGBUILD.

o you can have a look at https://wiki.archlinux.org/title/VCS_package_guidelines#Git_submodules

@alex19EP commented on GitHub (Mar 22, 2022): > I only wonder why you have the jslib as an extra download in the PKGBUILD. o you can have a look at https://wiki.archlinux.org/title/VCS_package_guidelines#Git_submodules
OVERLORD commented 2026-02-05 00:22:36 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Mar 22, 2022):

I only wonder why you have the jslib as an extra download in the PKGBUILD.

o you can have a look at https://wiki.archlinux.org/title/VCS_package_guidelines#Git_submodules

Ah, that explains :)

@BlackDex commented on GitHub (Mar 22, 2022): > > I only wonder why you have the jslib as an extra download in the PKGBUILD. > > o you can have a look at https://wiki.archlinux.org/title/VCS_package_guidelines#Git_submodules Ah, that explains :)
OVERLORD commented 2026-02-05 00:22:37 +03:00
Author
Owner
Copy Link

@ph0 commented on GitHub (May 8, 2022):

I am not sure if this is the same issue. I am running © 2022, Bitwarden Inc. (Powered by Vaultwarden) Version 2.25.1

Earlier today I logged in and my logins were not showing because there was a notification asking me to click the button to update encryption.

I updated, was logged out, and now when I try to login I get an error

"An error has occurred. Could not send login notification email. Please contact your administrator."

I am still getting this same issue.

Nobody replied last time so I genuinely doubt anyone will now.

I really want to login, backup my database, delete vaultwarden, and find another password manager.

@ph0 commented on GitHub (May 8, 2022): > I am not sure if this is the same issue. I am running [© 2022, Bitwarden Inc. (Powered by Vaultwarden) Version 2.25.1 ](url) > > Earlier today I logged in and my logins were not showing because there was a notification asking me to click the button to update encryption. > > I updated, was logged out, and now when I try to login I get an error > > "An error has occurred. Could not send login notification email. Please contact your administrator." I am still getting this same issue. Nobody replied last time so I genuinely doubt anyone will now. I really want to login, backup my database, delete vaultwarden, and find another password manager.
OVERLORD commented 2026-02-05 00:22:39 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (May 8, 2022):

I am not sure if this is the same issue. I am running © 2022, Bitwarden Inc. (Powered by Vaultwarden) Version 2.25.1
Earlier today I logged in and my logins were not showing because there was a notification asking me to click the button to update encryption.
I updated, was logged out, and now when I try to login I get an error
"An error has occurred. Could not send login notification email. Please contact your administrator."

I am still getting this same issue.

Nobody replied last time so I genuinely doubt anyone will now.

I really want to login, backup my database, delete vaultwarden, and find another password manager.

I have never seen a request to update the encryption ever. So I'm not sure where you are seeing this.

Also, in a later post you mentioned it was fixed again, so what would you have expected to be answered??

@BlackDex commented on GitHub (May 8, 2022): > > I am not sure if this is the same issue. I am running [© 2022, Bitwarden Inc. (Powered by Vaultwarden) Version 2.25.1 ](url) > > Earlier today I logged in and my logins were not showing because there was a notification asking me to click the button to update encryption. > > I updated, was logged out, and now when I try to login I get an error > > "An error has occurred. Could not send login notification email. Please contact your administrator." > > I am still getting this same issue. > > Nobody replied last time so I genuinely doubt anyone will now. > > I really want to login, backup my database, delete vaultwarden, and find another password manager. I have never seen a request to update the encryption ever. So I'm not sure where you are seeing this. Also, in a later post you mentioned it was fixed again, so what would you have expected to be answered??
OVERLORD commented 2026-02-05 00:22:41 +03:00
Author
Owner
Copy Link

@joelmccracken commented on GitHub (Sep 17, 2024):

I just want to mention that I roughly had this issue myself last night, and pulled out much of what little hair I had left. It seems that its some kind of a version problem; I was trying to log in with

[1] joelmccracken@glamdring> which bw                                                                                                              ~
/Users/joelmccracken/.nix-profile/bin/bw
joelmccracken@glamdring> bw --version                                                                                                              ~
2022.10.0

and no matter what I did, I kept getting the master password failure. I know that this version has worked in the past, tho I haven't run it in some time, but given I was able to log in with the password via the web interface, I decided to install another version of the cli and try it. I did, this time via homebrew, and it worked.

I suspect something about the official client and the pw remote host funcitonality changed, because, well, it used to work, and now it doesn't. But, I can't prove it. I did see somewhere that there was some node package version that might be the cause, which I guess might impact it, although generally folks feel that nix dependency locking is as about as precise as one can get.

@joelmccracken commented on GitHub (Sep 17, 2024): I just want to mention that I roughly had this issue myself last night, and pulled out much of what little hair I had left. It seems that its some kind of a version problem; I was trying to log in with ``` [1] joelmccracken@glamdring> which bw ~ /Users/joelmccracken/.nix-profile/bin/bw joelmccracken@glamdring> bw --version ~ 2022.10.0 ``` and no matter what I did, I kept getting the master password failure. I know that this version has worked in the past, tho I haven't run it in some time, but given I was able to log in with the password via the web interface, I decided to install another version of the cli and try it. I did, this time via homebrew, and it worked. I suspect something about the official client and the pw remote host funcitonality changed, because, well, it used to work, and now it doesn't. But, I can't prove it. I did see somewhere that there was some node package version that might be the cause, which I guess might impact it, although generally folks feel that nix dependency locking is as about as precise as one can get.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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 bug enhancement future Vault
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1237
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?