[NOTE] Update to the latest version before reporting an issue #830

New issue

Open

opened 2026-02-20 08:05:27 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-20 08:05:27 -05:00

Owner

Originally created by @BlackDex on GitHub (Oct 11, 2020).

Hello all,

Vaultwarden is an actively development project. Sometimes there are a lot of updates, and sometimes a bit less.
That could mean you might have an older version of Vaultwarden running or, you are using latest which might not have all recent fixes and patches.

Because of all these changes, most issues (not all) are probably because you do not have the Vaultwarden server updated to the latest version available which has these fixes in place.

The current latest version is:
Commits since latest release:

Please make sure you have either the latest version running and checked all Closed issues or testing before reporting an issue.
Also, check the commits done since the latest release which are in testing, it could be that a bug you run into is already fixed, but they are not yet released as a new version .

If after updating to the latest version and checking the commits done since the latest release of Vaultwarden and you still encounter these same issue, please go ahead and post a new topic on the Discussions or here at the issues page.

Thanks for all your support.

New docker multi database support for Debian and Alpine

Only one image: `vaultwarden/server`

It contains support for SQLite, MySQL and PostgreSQL all in one! Supports AMD64, ARMv6, ARMv7 and ARMv8 (Aarch64), and all architectures support all database backends!.

Note: The old bitwarden_rs are no longer available!

Which tag to use:

vaultwarden/server:latest: Tracks the latest released version (i.e., tagged with a version number). Recommended for most users, and generally the most stable.
vaultwarden/server:testing: Tracks the latest commits to the source repository. Recommended for users who want early access to the newest features or enhancements. Generally pretty stable, but occasional issues are unavoidable.
vaultwarden/server:x.y.z: Represents a specific released version. Prefer to use latest to keep up-to-date.

Alpine base

vaultwarden/server:alpine, vaultwarden/server:testing-alpine, vaultwarden/server:x.y.z-alpine: Functionally the same as the above images, but based on Alpine instead of Debian, which results in a smaller image and sometimes less security issues in the base image.

Originally created by @BlackDex on GitHub (Oct 11, 2020). Hello all, Vaultwarden is an actively development project. Sometimes there are a lot of updates, and sometimes a bit less. That could mean you might have an older version of Vaultwarden running or, you are using `latest` which might not have all recent fixes and patches. Because of all these changes, most issues (not all) are probably because you do not have the Vaultwarden server updated to the latest version available which has these fixes in place. The current latest version is: [![GitHub Release](https://img.shields.io/github/release/dani-garcia/vaultwarden.svg)](https://github.com/dani-garcia/vaultwarden/releases/latest) Commits since latest release: ![GitHub commits since tagged version](https://img.shields.io/github/commits-since/dani-garcia/vaultwarden/latest/main) Please make sure you have either the `latest` version running and checked all Closed issues or `testing` before reporting an issue. Also, check the commits done since the `latest` release which are in `testing`, it could be that a bug you run into is already fixed, but they are not yet released as a new version ![GitHub commits since tagged version](https://img.shields.io/github/commits-since/dani-garcia/vaultwarden/latest/main). If after updating to the latest version and checking the commits done since the latest release of Vaultwarden and you still encounter these same issue, please go ahead and post a new topic on the [Discussions](https://github.com/dani-garcia/vaultwarden/discussions) or here at the issues page. Thanks for all your support. # New docker multi database support for Debian and Alpine ### Only one image: `vaultwarden/server` It contains support for SQLite, MySQL and PostgreSQL all in one! Supports AMD64, ARMv6, ARMv7 and ARMv8 (Aarch64), and all architectures support all database backends!. **Note**: The old `bitwarden_rs` are no longer available! ### Which tag to use: - `vaultwarden/server:latest`: Tracks the latest released version (i.e., tagged with a version number). Recommended for most users, and generally the most stable. - `vaultwarden/server:testing`: Tracks the latest commits to the source repository. Recommended for users who want early access to the newest features or enhancements. Generally pretty stable, but occasional issues are unavoidable. - `vaultwarden/server:x.y.z`: Represents a specific released version. Prefer to use latest to keep up-to-date. #### Alpine base - `vaultwarden/server:alpine`, `vaultwarden/server:testing-alpine`, `vaultwarden/server:x.y.z-alpine`: Functionally the same as the above images, but based on Alpine instead of Debian, which results in a smaller image and sometimes less security issues in the base image.