Container still ran, just couldn’t login. Maybe there was more little things, can’t remember.Īnd I’d like to just note that switching the tag to :latest didn’t work on my old container, not sure what the issue there was. I didn’t have to do anything other than basic setup on the new container, just put in an admin token, put my hostname, setup email under the admin page, and sent myself an invite. So I added the vaultwarden container from the app repo (my old was was still named bitwarden for some reason) to my dockers.Īnd just exported my old users vault as json and imported it in the new server under my user account.Įverything seems fine so far. I couldn’t login to my vault no matter what, guess the newer bitwarden clients are incompatible. Have you been able to upgrade the vaultwarden docker meanwhile to 1.25.0 or higher and if yes, how did you do that? I get the same output in the log as gizmer (on page 20). I/O error while setting tls.Have the same issue as you guys, I have to use version 1.24.0 and it's not possible to upgrade to a higher version. Logger failed to initialize: attempted to set a logger after the logging system was already initialized running the bitwarden_rs server without https) the it works just fine.Įrror when running sudo docker-compose up -d

When I remove the enviroment variable ROCKET_TLS (i.e. I've been at this for a while and still no luck. I've double and triple checked the location of my ssl certificates and that they match up. Which is the same error I get when I incorrectly name the ssl certificates upon running it with Docker. I'm trying to run it using docker compose and keep getting the error below. Currently I'm successfully running bitwarden_rs on Docker.

Bitwarden_rs docker