If you got the automatic updates on the bitwarden clients, they will show an empty vault if you are selfhosting vaultwarden.

It seems to be an accidental bug in the bitwarden clients that are assuming that they're talking with official servers

It's fixed with the latest release of the vaultwarden server that was published a few minutes ago

top 50 comments

sorted by: hot top controversial new old
[–] 6 points 1 day ago

Just did the update of vaultwarden. Had to log out and log back again in bitwarden on my browser. On the phone it seems to just have worked. Thank you for the PSA :)

  • source
  • [–] 39 points 2 days ago (1 child)

    Thanks so much for the PSA. I'm currently on vacation without any chance to update Vaultwarden but need access to it via the Bitwarden client. Just disabled the auto update in time. I wish I could vote this twice.

  • source
  • hideshow 2 child comments
  • [–] 87 points 2 days ago* (1 child)

    I found this comment on what happened by dani-garcia, one of the main devs:

    The short version is that around 8-ish years ago, Bitwarden changed the way the vault items were structured, and Vaultwarden added some backwards compatibility fields to ensure both old and new versions of the clients worked.

    These backwards compatibility fields were supposed to be a temporary measure, but for at least the next three years the clients still required them, until we eventually forgot to keep track of them. At some point between 2021 and today, the clients stopped requiring these backwards compatibility fields, but Vaultwarden was still sending them.

    This wasn't a problem until Bitwarden decided to use the backwards compatibility fields in a completely different way, which caused the clients to crash.

    Found here: https://github.com/dani-garcia/vaultwarden/discussions/7473

  • source
  • hideshow 2 child comments
  • [–] 43 points 2 days ago (1 child)

    There’s a reason you don’t do things like that…

    Apparently nobody in that software team has heard about Knight Capital. They reused a flag and that coupled with a deployment failure that only lasted ~45 minutes caused an over 400 million dollar loss nearly bankrupting the entire company. Ultimately they ended up combining with another company.

    The immediate cause of the incident was a deployment failure that left one of eight servers running outdated code, creating an inconsistency in how the system interpreted incoming instructions. The new software reused a flag associated with a legacy function known as “Power Peg,” which had been disabled but not removed from the codebase, and on the unpatched server this flag activated obsolete logic that continuously generated child orders in response to parent orders that the system did not correctly recognize as already filled.

    More details

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 126 points 2 days ago (9 children)

    Do not update any bitwarden client until you can update vaultwarden

  • source
  • hideshow 10 child comments
  • [–] 29 points 2 days ago

    If anyone's Firefox auto updated like mine you can uninstall the extension, go to the Bitwarden extension page on the Firefox website and manually install the old version. Only needed if you can't update vaultwarden right away.

  • source
  • parent
  • load more comments (8 replies)
    [–] 40 points 2 days ago (2 children)

    I've been leery about bitwarden client updates since the posts awhile back about the new(ish) PE/VC c suite person.

    I'm not saying those are related in any way other than the fact that I intentionally haven't updated my clients to the latest yet and for once it worked out for me :)

  • source
  • hideshow 4 child comments
  • [–] 49 points 2 days ago (3 children)

    I do love docker + a front end like dockge.

    Saw this post, switched to my browser, clicked three buttons; vaultwarden is now updated. Didn't even move my lazy ass off the couch. (I'm on my phone)

    Thanks for the PSA! :)

  • source
  • hideshow 6 child comments
  • [–] 17 points 2 days ago (1 child)

    I love podman quadlets, I didn't do anything and it updated itself 😁

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 2 days ago (1 child)

    I run watchtower on a cron schedule. It had already fired for today, so it wouldn't have run again until tomorrow. I could have waited, but manual is just as easy.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 2 days ago (1 child)

    Be aware that watchtowerr is not updated anymore and due to the nature of having access to the socket is a security risk.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 11 points 2 days ago* (1 child)

    I can recommend Arcane as a front end. I switched over all my services this last week from multiple dockges to a single arcane (+agents). It's looking pretty sweet now. Cleans up a lot of bookmarks too 😆

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 2 days ago*

    Noticed that as well with our selfhosted instance at work and wondered what the deal was.
    Guess I now know why.

  • source
  • Wow! Thanks for the PSA!

  • source
  • [–] 3 points 1 day ago

    Thanks for the PSA, I got hit before any of this was live

  • source
  • [–] 16 points 2 days ago (2 children)

    Ps. I notice your msn avatar. I'm busy with https://retromessenger.com/. Coming soon for free!

  • source
  • hideshow 4 child comments
  • [–] [S] 3 points 2 days ago (1 child)

    Very nice, I even considered using escargot to patch the old clients but then realized it's not a great idea security wise

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 days ago

    Yeah escargot just doesn't do it for me. I want to keep using the existing chat network I use daily. But just giving back the MSN vibes.

    I created it using gtk4. So it's cross platform as well. Meaning Linux native. Which I also wanted.

  • source
  • parent
  • [–] 13 points 2 days ago

    Thank you for the PSA good friend!

  • source
  • [–] 11 points 2 days ago (7 children)

    Thanks, probably saved me a lot of headache on my laptop browsers. Fortunately, I don't use the official Bitwarden client on android partly because this seems to keep happening.

  • source
  • hideshow 8 child comments
  • [–] 1 point 2 days ago (1 child)

    I've been using the bitwarden android app for about a year and a half with zero issue 🤷

  • source
  • parent
  • hideshow 2 child comments
  • This would be the 3rd time since I've been using it that it has broken compatibility with Vaultwarden, but Vaultwarden always fixes it pretty quickly. But usually browser plugins end up updating before I get around to updating Vaultwarden.

  • source
  • parent
  • load more comments (6 replies)
    [–] 8 points 2 days ago (1 child)

    Was wondering why it suddenly was stuck loading, thanks!

  • source
  • hideshow 2 child comments
  • [–] 4 points 2 days ago (1 child)

    The packaged Debian version did not get updated yet.

  • source
  • hideshow 2 child comments
  • [–] 5 points 2 days ago (1 child)

    Thank you for this. I thought I was going insane. Time to turn auto updates off

  • source
  • hideshow 2 child comments
  • load more comments
    view more: next ›