[NOTE] ⚠️ Client fails to connect or login ⚠️ #950

New Issue

OVERLORD · 2025-10-09T16:58:12+03:00

OVERLORD commented

2025-10-09 16:58:12 +03:00

Originally created by @BlackDex on GitHub.

New versions

If you are currently unable to login with any client after you either have the clients updated or Vaultwarden it self please check you are running the latest version of Vaultwarden!

Bitwarden has released new client versions which are not compatible with Vaultwarden version bellow 1.27.0.
Since version 1.27.0 Vaultwarden supports these new clients and has many bugs fixed and features added.

See the release notes here Release v1.27.0 (2022-12-24).

If you are running the testing tagged releases of Vaultwarden, the version should be 1.26.0-10dadfca, which is exactly the same as the released 1.27.0.

Please do not report any client connection bugs or issues before you have fully updated your environment to the latest version.
To check which version you are running right now you can best login into the Admin Interface.
To access the Admin Interface you need to go to https://your.domain.tld/admin and after login click on the Diagnostics tab.
This will show you the current version you have running.

If you can't access the admin interface you can also check the web-vault version on the web client.
It should look something like this.

An other way to check the version of Vaultwarden is via the cli, either via docker or container-less install.

# If you have installed Vaultwarden via a package manager like pacman, deb or yum.
vaultwarden --version

# If you have it running via docker or podman
# Replace vaultwarden-container-name with the actual name of your vaultwarden container, check `docker ps`
docker exec vaultwarden-container-name /vaultwarden --version

Other common issues

There are some other common issues where people are reporting 2FA/MFA not working.
Most of the time this is either incorrect date/time, this can be checked in the Admin Interface at the Diagnostics page.
Or, the reverse proxy has some added security settings enabled which replace or adds the already present correct security headers, or prevent PUT or DELETE requests.

This causes issues like unable to login, update ciphers, upload attachments and other strange issues.
Please also check the logs of your reverse proxy before posting any issue!

Originally created by @BlackDex on GitHub. # New versions If you are currently unable to login with any client after you either have the clients updated or Vaultwarden it self please check you are running the latest version of Vaultwarden! Bitwarden has released new client versions which are not compatible with Vaultwarden version bellow 1.27.0. Since version 1.27.0 Vaultwarden supports these new clients and has many bugs fixed and features added. See the release notes here [Release v1.27.0 (2022-12-24)](https://github.com/dani-garcia/vaultwarden/discussions/3037). If you are running the `testing` tagged releases of Vaultwarden, the version should be `1.26.0-10dadfca`, which is exactly the same as the released `1.27.0`. Please **do not report** any client connection bugs or issues before you have fully updated your environment to the latest version. To check which version you are running right now you can best login into the **Admin Interface**. To access the **Admin Interface** you need to go to `https://your.domain.tld/admin` and after login click on the `Diagnostics` tab. This will show you the current version you have running. If you can't access the admin interface you can also check the web-vault version on the web client. It should look something like this. ![image](https://user-images.githubusercontent.com/610450/210139662-1d44e1d5-433b-479c-bf51-3689cd8ca22e.png) An other way to check the version of Vaultwarden is via the cli, either via docker or container-less install. ```bash # If you have installed Vaultwarden via a package manager like pacman, deb or yum. vaultwarden --version # If you have it running via docker or podman # Replace vaultwarden-container-name with the actual name of your vaultwarden container, check `docker ps` docker exec vaultwarden-container-name /vaultwarden --version ``` # Other common issues There are some other common issues where people are reporting 2FA/MFA not working. Most of the time this is either incorrect date/time, this can be checked in the **Admin Interface** at the **Diagnostics** page. Or, the reverse proxy has some added security settings enabled which replace or adds the already present correct security headers, or prevent `PUT` or `DELETE` requests. This causes issues like unable to login, update ciphers, upload attachments and other strange issues. Please also check the logs of your reverse proxy before posting any issue!

OVERLORD closed this issue

2025-10-09 16:58:12 +03:00

OVERLORD commented

2025-10-09 16:58:14 +03:00

@BlackDex commented on GitHub:

This issue is old and outdated.

@BlackDex commented on GitHub: This issue is old and outdated.

OVERLORD referenced this issue

2025-10-09 17:10:53 +03:00

Vaultwarden starts timing out after some time without a restart #1306

OVERLORD referenced this issue

2025-10-09 17:10:54 +03:00