![]() ![]() I implemented all this when 1Password informed me that in order to continue using their service, my vault would have to be hosted on their server and I would have to pay them every month for the privilege. When I'm out and about and need to sync with the NAS from my laptop or mobile device, I activate the VPN and do the sync. I have an L2TP VPN configured with a shared-secret and user passwords that are ridiculously long and complex. When I am at home, my devices with Bitwarden all sync to the Vautwarden instance on the NAS without issue. Also, I wish updating to a new version of Vaultwarden was a little more straightforward. The only part that was a slight hassle was buying a cert, creating an FQDN and making the DNS entries to get an SSL connection to the NAS. I run it as a Docker instance on my home Synology NAS. I'm sure someone will be happy to explain to me how foolish my implementation is, but I'm comfortable with it from a security perspective. If more information is needed, I will be able to provide it.I self-host Vaultwarden. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |