![]() Openssl req -new -sha256 -key tower.key -subj "/C=FR/ST=FR/O=MyNas/CN=tower" -extensions v3_req -out tower.csr Openssl req -x509 -new -nodes -key towerrootCA.key -sha256 -extensions v3_ca -config conf.file -days 365 -out towerrootCA.crt Openssl genrsa -des3 -out towerrootCA.key 4096 Here is how I generate my stuff : # > CA Key The only thing I can't have working is the bitwarden Android App which throw me a "Trust anchor for certification path not found" error even though i've imported the CA certificate. I have bitwarde docker running on my Unraid, reachable on all web browser through (including Web browsers on my phone) thanks to a self signed certificate with self CA. 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. I'm trying to use this with SWAG/nginx and there are 2 problems I'm having trouble solving:ġ. ![]()
0 Comments
Leave a Reply. |