Is there any way to configure this so that BitwardenRS gets SSL on the LAN but can't be reached from the WAN?ĭid anyone already try to setup a full local selfhosted bitwarden (without any Let's Encrypt) and make it working with Android ? I don't want bitwarden exposed to the internet, despite the fact I am also using the reverse proxy to handle internet traffic to other dockers. Proxy_pass $upstream_proto://$upstream_app:$upstream_port Ģ. # enable the next two lines for ldap auth #auth_basic_user_file /config/nginx/.htpasswd # enable the next two lines for http auth # enable for ldap auth, fill in ldap details in nf # set the environment variable WEBSOCKET_ENABLED=true on your bitwarden container # make sure your bitwarden container is named "bitwarden" # make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url I get a 502 bad gateway using the subdomain to try and hit the bitwardenrs docker on 8086. This container image also includes an SQLite database which works well for one or two users.I'm trying to use this with SWAG/nginx and there are 2 problems I'm having trouble solving:ġ. In order to locate which container to run I checked their Github Wiki and found that I need the bitwardenrs/server:raspberry image which is armv7hf compatible. If you do not have Docker installed on your Raspberry Pi you can view the steps to get it up and running here. You can check out my Bitwarden review here. Luckily I found Bitwarden_rs which is not as resource intensive as the official image and is perfect for small self-hosted environments. The official Bitwarden image only supports the amd64 architecture and I needed a container that I could run on my Raspberry Pi 4 cluster. Bitwarden is an open-source password manager that can be self-hosted at home to keep your passwords and other private data secure.
0 kommentar(er)
