Removed the dockers and cleaned up all the files. Still not sure why, but it must have been something regarding authentication with the database, no doubt. In MariaDB, no rows were created and even with root credentials BitWarden didn't create any.
Mariadb however, did really make the database and user connected to it, confirmed the environmental's to make sure the logins matched. It was just stuck on the create account page and the button didn't work.ĭouble-checked the logs within Docker but the MariaDB kept saying the user couldn't authenticate itself. Ran the code, everything got set up annddd. looked like that one uses the MariaDB fork from Jammy. The easiest way I usually use is simply grab a Mariushosting script and adjust it to my data/needs. Issues I ran against might not happen at everyone, even with the same type of hardwareĪs BitWarden unified doesn't come included with a database, unlike Vaultwarden, an SQL database was needed. but I much prefer testing everything out myself first :P A few times along the story I could, and probably should have, contacted BitWarden support to see how much they could help. Comparing a good few of my experiences to how I experienced the setup of Vaultwarden (which was a 1 minute job any monkey can do) No experience with inner workings of SQL databases or queries Do have extremely basic docker knowledge as I have a few applications hosted on my Synology, but not much more Device used: Synology 720+ with 18b ram and Docker installed Decided to write down some of my experiences while setting up Bitwarden Unified on my Synology NAS.
0 kommentar(er)
