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

  • SmoothLiquidation@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    27 days ago

    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

    • Lem453@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      27 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.

    • Marthirial@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      27 days ago

      Switching to Passbolt right now. I have the feeling this is the beginning of the enshitification of Bitwarden.

      • cron@feddit.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        27 days ago

        Such bugs have already appeared in the past. It’s only logical that this happens from time to time, as the creators of bitwarden don’t test the compatobility with 3rd party servers.

        What is important is that they’re not deliberately blocking vaultwarden.

      • Patrick@ppb.social
        link
        fedilink
        arrow-up
        1
        ·
        27 days ago

        @Marthirial @Wispy2891 They are quickly moving towards enshitification, but this was likely just a planned patch and not intentional shot across the bow. As someone mentioned, they aren’t required to check 3rd party software. But it does suck when it happens.

  • Darkassassin07@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    27 days ago

    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! :)

    • fozid@feddit.uk
      link
      fedilink
      English
      arrow-up
      1
      ·
      27 days ago

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

      • Darkassassin07@lemmy.ca
        link
        fedilink
        English
        arrow-up
        0
        ·
        27 days ago

        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.

        • Appoxo@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          27 days ago

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