Bitwarden and Letsencrypt Remote Access Issue

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Bitwarden and Letsencrypt Remote Access Issue

      Hi everyone I'm having a little trouble accessing bitwarden remotely through the use of duckdns and letsencrypt + reverse proxy, I hope someone can help me I'm still in the learning process.

      I developed bitwarden through docker as @TechnoDadLife explains in his tutorial

      Unfortunately the process let you with a local access through standard port, no https, so I decided to go the route duckdns+letsencrypt+reverse proxy (everything through docker) to access it remotely via https.

      Every container worked fine on its own:

      • I have my domain let's say iloveomv.duckdns.org
      • I created my subdomain inside letsencrypt docker, let's say bitwarden.iloveomv.duckdns.org
      • I open the right ports on my router and everything works fine I can see my page remotely with https answer back and the letsencrpy ssl certificate going through.



      Now the problem happens, I can't connect my bitwarden loal docker to the subdomain bitwarden.iloveomv.duckdns.org without getting the error 504 from nginx when I try to connect to it.



      Sure I suspect is an error on my part, tryng to config the bitwarden docker, so I went ahead and look at the info page of the docker itself -> bitwarden docker

      Here is the first problem as you can see, on the docker infopage itself, there is no variable to set https, it seems to operate just through http.


      Reading further there is a way to activate https trough ROCKET_TLS, and use this proxy config, for letsencrypt docker.


      So I tried this:

      • created a variable environment on the bitwarden docker as ROCKET_TLS, giving it physical access to the sharedfolder where fullchain.pem and privkey.pem produced by letsencrypt are stored
      • changed the due localhost parameter with the duckdns domain on the proxy config
      • added --network mynetwork flag to the bitwarden container to let it talk to letsencrypt container
      but none of it worked out. I'm still getting error 504 when I try to connect to bitwarden.iloveomv.duckdns.org


      Any idea what I'm doing wrong here?! can someone point me in the right direction?!

      Thank you very much in advance
    • Wek wrote:

      Hi everyone I'm having a little trouble accessing bitwarden remotely through the use of duckdns and letsencrypt + reverse proxy, I hope someone can help me I'm still in the learning process.

      I developed bitwarden through docker as @TechnoDadLife explains in his tutorial

      Unfortunately the process let you with a local access through standard port, no https, so I decided to go the route duckdns+letsencrypt+reverse proxy (everything through docker) to access it remotely via https.

      Every container worked fine on its own:

      • I have my domain let's say iloveomv.duckdns.org
      • I created my subdomain inside letsencrypt docker, let's say bitwarden.iloveomv.duckdns.org
      • I open the right ports on my router and everything works fine I can see my page remotely with https answer back and the letsencrpy ssl certificate going through.


      Now the problem happens, I can't connect my bitwarden loal docker to the subdomain bitwarden.iloveomv.duckdns.org without getting the error 504 from nginx when I try to connect to it.



      Sure I suspect is an error on my part, tryng to config the bitwarden docker, so I went ahead and look at the info page of the docker itself -> bitwarden docker

      Here is the first problem as you can see, on the docker infopage itself, there is no variable to set https, it seems to operate just through http.


      Reading further there is a way to activate https trough ROCKET_TLS, and use this proxy config, for letsencrypt docker.


      So I tried this:

      • created a variable environment on the bitwarden docker as ROCKET_TLS, giving it physical access to the sharedfolder where fullchain.pem and privkey.pem produced by letsencrypt are stored
      • changed the due localhost parameter with the duckdns domain on the proxy config
      • added --network mynetwork flag to the bitwarden container to let it talk to letsencrypt container
      but none of it worked out. I'm still getting error 504 when I try to connect to bitwarden.iloveomv.duckdns.org


      Any idea what I'm doing wrong here?! can someone point me in the right direction?!

      Thank you very much in advance
      Start with the parts first, does each part work by it self?

      1) After you installed Bitwarden, could you access it locally.

      2) After you installed LetsEncrypt and Duckdns, did you get the welcome to my server page for bitwarden.iloveomv.duckdns.org ? For most people, this is where they get messed up. Make sure everything works before you move on. Don't skip this step!

      3) Once that works then, connect Bitwarden and Letsencrypt. Any problems you have are because Bitwarden and Letsencrypt aren't communicating properly. This makes trouble shooting very easy.
      Build, Learn, Create.

      How to Videos for OMV

      Post any questions to the forum, so others can benefit from your curiosity. :thumbsup:
      No private support.
    • Hi @Wek

      I managed to make bitwarden works with let's Encrypt.
      Furthermore, my Bitwarden container is not installed on the same OMV, but it works like a charm (Remote/local access, FireFox plugin, iOS App)
      The most important part is to properly create and configure the "bitwarden.subdomain.conf" file, located in your AppData folder, under

      LetsEncrypt/Nginx/Proxy-confs

      here is a template in attachment

      You have to change the following lines:

      server_name bitwarden.*; --> replace bitwarden with your subdomain
      set $upstream_bitwarden bitwarden; --> replace bitwarden with your bitwarden container name
      proxy_pass 192.168.1.XXX:8080; --> replace the IP:port with the IP:port of the bitwarden container

      don't forget to restart the letsencrypt container
      Files

      The post was edited 5 times, last by emerenel ().

    • emerenel wrote:

      Hi @Wek

      I managed to make bitwarden works with let's Encrypt.
      Furthermore, my Bitwarden container is not installed on the same OMV, but it works like a charm (Remote/local access, FireFox plugin, iOS App)
      The most important part is to properly create and configure the "bitwarden.subdomain.conf" file, located in your AppData folder, under

      LetsEncrypt/Nginx/Proxy-confs

      here is a template in attachment

      You have to change the following lines:

      server_name bitwarden.*; --> replace bitwarden with your subdomain
      set $upstream_bitwarden bitwarden; --> replace bitwarden with your bitwarden container name
      proxy_pass 192.168.1.XXX:8080; --> replace the IP:port with the IP:port of the bitwarden container

      don't forget to restart the letsencrypt container
      Good job Emerenel!

      Can you post screen shots of your "bitwarden.subdomain.conf" file.

      That would make it easier to figure out and copy.

      You can add a screen shoot by clicking done here in your reply and adding the attachment.

      |
      |
      |
      |
      |
      \/
      Build, Learn, Create.

      How to Videos for OMV

      Post any questions to the forum, so others can benefit from your curiosity. :thumbsup:
      No private support.
    • Users Online 1

      1 Guest