Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs
AGPL-3.0 License
Published by dani-garcia over 3 years ago
⚠️ Reminder: If you are still using the bitwardenrs/server*
Docker images, you need to migrate to the new vaultwarden
image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images are deprecated and will stop being updated after 1.23.0.
show_password_hint
by default, it still can be enabled in the admin panel or with environment variables.Published by dani-garcia over 3 years ago
⚠️ Reminder: If you are still using the bitwardenrs/server*
Docker images, you need to migrate to the new vaultwarden
image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images are deprecated and will stop being updated after 1.23.0.
Published by dani-garcia over 3 years ago
⚠️ Reminder: If you are still using the bitwardenrs/server*
Docker images, you need to migrate to the new vaultwarden
image. Check https://github.com/dani-garcia/vaultwarden/discussions/1642 for an explanation. The old images are deprecated and will stop being updated after 1.23.0.
sends_allowed
option to disable Send functionality.Published by dani-garcia over 3 years ago
Update 20201-04-30: This release has been pushed again to fix an issue with the Docker builds building an older revision of the project.
Due to user confusion and to avoid any possible trademark/brand issues with the official server, this project is going to be renamed to vaultwarden. This rename might mean you will need to make some changes to your setup.
If you are using any of the docker images, you will have to migrate to the new image under the vaultwarden organization:
vaultwarden/server
The new image is equivalent to the old one except for the name, so the upgrade is as simple as removing the old container and creating a new one with the new image, making sure the rest of parameters are the same. For example, if you used the default docker run
command mentioned in the readme, and upgrade would be done like this:
# Stop and remove the old container
docker stop bitwarden
docker rm bitwarden
# Start new container with the data mounted, make sure the path is the same as the previous one
docker run -d --name vaultwarden -v /bw-data/:/data/ -p 80:80 vaultwarden/server:latest
Note that the old images aren't gone yet, just deprecated. They will keep being updated for another two releases after this one to avoid breakage, but it's recommended to migrate to the new image as soon as possible.
If you are still using the old database specific images (server-mysql and server-postgresql), they are also deprecated since the main server image supports all three databases at the same time, more info on release 1.17.0.
If you are using the startup scripts mounted inside the container (/etc/bitwarden_rs.sh
and /etc/bitwarden_rs.d/*
), they will now load with the vaultwarden name first and the bitwarden_rs name as a fallback for compatibility, but it's recommended to rename them as well.
If you are using the git repository, we've used this opportunity to rename the master
branch to main
, so make sure to have that in mind. The rest of the process is the same and GitHub will redirect the old remote URL to the new one, simply note that the binary generated by cargo is now named vaultwarden
instead of bitwarden_rs
.
TRASH_AUTO_DELETE_DAYS
to a positive value to enable this functionalityTRASH_PURGE_SCHEDULE
Published by dani-garcia over 3 years ago
Published by dani-garcia over 3 years ago
Published by dani-garcia almost 4 years ago
<CONFIG_NAME>_FILE
to point to it.
/etc/bitwarden_rs/token
, you can use ADMIN_TOKEN_FILE=/etc/bitwarden_rs/token
and it will read the file and set the token to it's contents.SMTP_DEBUG
, and added options to ignore certificate issues.Published by dani-garcia about 4 years ago
bitwardenrs/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 separate images for MySQL and PostgreSQL will be kept updated for the time being, but it's recommended to migrate when possible.
bitwardenrs/server:latest
: Tracks the latest released version (i.e., tagged with a version number). Recommended for most users, and generally the most stable.bitwardenrs/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.bitwardenrs/server:x.y.z
: Represents a specific released version. Prefer to use latest to keep up-to-date.bitwardenrs/server:arm32v6
, bitwardenrs/server:testing-arm32v6
, bitwardenrs/server:x.y.z-arm32v6
bitwardenrs/server:alpine
, bitwardenrs/server:testing-alpine
, bitwardenrs/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. Only supported for SQLite and the AMD64 and ARMv7 architectures.
cargo build --features sqlite,mysql,postgresql
or any combination of them.DB_CONNECTION_RETRIES
option.DOMAIN
is not configured, or configured incorrectly.vendored_openssl
feature, to statically link OpenSSL, disabled by default.Published by dani-garcia about 4 years ago
arm32v6
tag, because docker fails to select that image in ARMv6 devices.Published by dani-garcia over 4 years ago
This release is also using docker multiarch images, check the Wiki page or the 1.16.0 release notes for info on how to migrate to it.
Published by dani-garcia over 4 years ago
The docker images have been modified to make use of the multiarch support, which means there's no need to use architecture specific tags anymore, and those will not be updated in the future.
Make sure you update your images correctly following the table at the end!
Published by dani-garcia over 4 years ago
Published by dani-garcia over 4 years ago
IMPORTANT: This is a required update when using newer clients, otherwise the delete functionality won't work
Published by dani-garcia over 4 years ago
BWRS_VERSION
env variable during cargo build
.Published by dani-garcia over 4 years ago
Published by dani-garcia over 4 years ago
DOMAIN
variable: DOMAIN=https://example.com/custom-path
USER_ATTACHMENT_LIMIT
or ORG_ATTACHMENT_LIMIT
to a value in kilobytes to apply it.y/n
, True/False
, 1/0
as config options that are booleans.Unique constraint violation
when using Two Factor and Postgres.Published by dani-garcia almost 5 years ago
LOG_LEVEL
value of debug
or trace
.IP_HEADER
, by default it's X-Client-IP
for backwards compat reasons.Published by dani-garcia almost 5 years ago
SIGNUPS_VERIFY=true
, default is false. There are also options to change the options for verification mail resending, check the .env.template
file.Published by dani-garcia almost 5 years ago
AUTHENTICATOR_DISABLE_TIME_DRIFT=true
.SIGNUPS_DOMAINS_WHITELIST=domain.com,example.org
).