spantaleev/vaultwarden-docker-ansible-deploy

🐳 Vaultwarden (a self-hosted password manager) server setup using Ansible and Docker

Vaultwarden server setup using Ansible and Docker

---

WARNING: this playbook has been made obsolete by the MASH playbook, which also supports installing the Vaultwarden service. There's a migration guide in the changelog.

---

This Ansible playbook can help you set up your own Vaultwarden server (unofficial Bitwarden compatible server) instance:

• on your own Debian/CentOS/RedHat server

• with all services (Vaultwarden, PostgreSQL, Traefik, etc.) running in Docker containers

• powered by the official vaultwarden/server container image

• interoperates nicely with related Ansible playbooks or other services using Traefik for reverse-proxying

SSL certificates are automatically managed by a Traefik reverse-proxy.

Various components (Postgres, Traefik, etc.) can be disabled and replaced with your own other implementations (see configuring the playbook).

Features

Using this playbook, you can get the following services configured on your server:

• a Vaultwarden server - a Bitwarden-API-compatible server storing your passwords and providing a web interface

• (optional) a PostgreSQL database for Vaultwarden

• (optional) free Let's Encrypt SSL certificate, which secures the connection to the Vaultwarden server

• (optional) backups

Basically, this playbook aims to get you up-and-running with all the basic necessities around Vaultwarden.

Installation

To configure and install Vaultwarden on your own server, follow the README in the docs/ directory.

Changes

This playbook evolves over time, sometimes with backward-incompatible changes.

When updating the playbook, refer to the changelog to catch up with what's new.

Support

• Matrix room: #vaultwarden-docker-ansible-deploy:devture.com

• GitHub issues: spantaleev/vaultwarden-docker-ansible-deploy/issues

Related

You may also be interested in these other playbooks:

• gitea-docker-ansible-deploy - for deploying a Gitea git version-control server

• matrix-docker-ansible-deploy - for deploying a fully-featured Matrix homeserver

• nextcloud-docker-ansible-deploy - for deploying a Nextcloud server

• peertube-docker-ansible-deploy - for deploying a PeerTube video-platform server

vaultwarden-docker-ansible-deploy's Issues

Non working notifications when path prefix defined

If 'devture_vaultwarden_path_prefix' variable defined (as /some-prefix, without trailing slash), the rule

devture_vaultwarden_container_labels_traefik_rule_websocket: 'Host(`{{ devture_vaultwarden_server_fqn }}`) && Path(`{{ devture_vaultwarden_path_prefix | quote }}notifications/hub`)'

in the 'roles/custom/devture_vaultwarden/defaults/main.yml' creates path without / delimiter, so label file for traefik has such line:

traefik.http.routers.vaultwarden-vaultwarden-websocket.rule=Host(`vaultwarden.domain.com`) && Path(`/some-prefixnotifications/hub`)

which not works then.

###########################################################
'/notifications/hub' should be proxied to the websocket server or notifications won't work.
Go to the Wiki for more info, or disable WebSockets setting WEBSOCKET_ENABLED=false.
###########################################################################################

I don't know correct workaround if 'devture_vaultwarden_path_prefix' is '/' so there is no pull request.