#auth_basic_user_file /config/nginx/.A password manager is a tool that helps you securely store and manage your passwords and other sensitive information, such as credit card numbers and bank account details. # enable the next two lines for http auth Proxy_pass $upstream_proto://$upstream_app:$upstream_port # enable the next two lines for ldap auth # enable for ldap auth, fill in ldap details in nf # make sure your bitwarden container is named 'bitwarden' Is the usage of official containers the best way for me or should I stick to the RS?Ĭode # make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url I lack the documentation (environment, ports, volumes, etc) of each of the required bitwarden containers and their connection.Ĭan someone show me a direction or where to start? So I guess I need to configurate my letsencrypt to match both services, bitwaren and nextcloud with and and therefore I can't use the installer script. As far as I know, the installer script of bitwarden installs a separate letsencrypt-container which I already have.

I use letsencrypt with reverse proxy and nextcloud (subdomain-configuration) and I might need to integrate bitwarden in the existing setup. On the other hand there are the official containers, which separate each service part. Keeping all my passowords in mind bothers me quite a while, so in the process of merging OMV4->OMV5 and all native services into docker I discovered the quite charming tool bitwarden.Īfter a short research if figured out that many users use the bitwardenrs/server container.

Docker bitwarden server