Well the reason is that this image mprasil is a bit more lightweight compared to a full blown installation and for personal use is more then enough. Also when I say personal I mean multi user solution that covers 95% of BW features.I haven't played with Docker at all and am still reading through trying to understand how it all works, but I am curious as to why you are using this mprasil image instead of working straight from the docker/bitwarden instructions shown here: Installing and deploying | Bitwarden Help & Support ?
Well the reason is that this image mprasil is a bit more lightweight compared to a full blown installation and for personal use is more then enough. Also when I say personal I mean multi user solution that covers 95% of BW features.
The reason is that you have one account for none hosted BW and another one for your local hosted BW. They don't talk to each other. So make sure that all your clients are running towards your local installation (or using the public name of your local BW in case you decide to expose it to the web).Sooo… before going through and messing with Docker, I had downloaded bitwarden app on my phone and PC just to play with the app and see if I liked it. In order to do so, I had to create an account. I ended working through the docker/mprasil tutorial and got BW up and running on my NAS. At the end of the setup, it asked for login info, but it would not accept the login info I had previously created; I ended up creating a new account using the same email but a different password for the NAS-hosted BW. The original account and password are still active on my phone and I can see a couple of test logins on the phone app, but these logins do not show up on the NAS-hosted BW when I visit the NAS:BW port IP address.
It appears as though the NAS-hosted BW does not talk to the online BW accounts? It appears to me as though I have 2 separate BW accounts using the same email that do not talk to each other. Is this possible? Can I point the BW apps to the NAS-hosted password vault?
Well that depends what kind of cert you have an what unique names its hosting. If you are already using that none wild card cert for something and it has no SAN values bind to it, you will not be able to use it for more then 1 destination/service.I think wwampy asked this question earlier, but I didn't see that it got answered (maybe I missed it). I already have an LE certificate and a myname.synology.me ddns. Do I need to create a new ddns somehow for bitwarden, or will the synology.me one work?