However I receive an I/O error when starting Bitwarden (this is most likely because the certificate folder is not mounted). Here are some of the things I have tried Learn to deploy a CLOUDFLARE tunnel on your SYNOLOGY, and the steps you need to take to config the access to your home network.Watch the video with the NEW m. Can hit my VaultWarden setup both internally and over the internet. Open File Station, navigate to the docker folder and create a subfolder named bitwarden. Before we get started, we need a directory where Bitwarden can add all of its files. Download and install Docker from the Synology Package Center. Need to use a different port than 443 but that's not a big deal. Self-host Bitwarden on Synology NAS Instructions 1. I have my synology nas mounted on my laptop, so roughly once a month I export my bitwarden password directly to the cryptomator vault. NAS reverse proxy securing connection with Lets Encrypt cert. What I would suggest is: 1 Make a encrypted export from bitwarden 2 Create a cryptomator vault in the NAS / Cloud 3 Move encrypted bitwarden file to vault. I wanted to setup 2FA and so tried to login to the vault however I get the message that “This browser requires HTTPS to use the web vault, Check the bitwarden_rs wiki for details on how to enable it.” And so I set about reading up on everything I could find, however as I am new to all of this it is extremely difficult to make progress. VaultWarden hosted via Docker on my Synology NAS.
I have Bitwarden running in a Docker (which I downloaded, not self composed) and it has been working great, both locally and remotely. I've posted on the Bitwarden_rs forums however I've had no reply and so I thought this forum may be able to help me out as my issue(s) would appear to be non-Bitwarden specific. I have read countless topics on this issue but can not find the cause of my problems. I’ve been on this task all weekend however I'm no further along. If more information is needed, I will be able to provide it.I really need your help as I feel like I’m banging my head against a brick wall. When I now open the page the normal homepage appears which is located in the directory "web" of the disk station and the error message is gone.Ĭould it be that the reverse proxy for http is not needed. I have removed the entry for the http reverse proxy (from step 2). When I try to access the page I get the error message ""400 Bad Request - Request Header Or Cookie Too Large". Accessing via opens the Vaultwarden login page. There are no other reverse proxy settings. I also created the two reverse proxy https and http according to the instructions. I was also able to install Vaultwarden exactly according to silverj's instructions without any problems and everything works.
I am using a DS1019+ with DSM 6.2.4 and the webstation 2.1.10 with the backend nginx and php 7.3.
0 kommentar(er)
