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
    ·
    edit-2
    40 minutes 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

  • clif@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    3 hours ago

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

  • Jul (they/she)@piefed.blahaj.zone
    link
    fedilink
    English
    arrow-up
    5
    ·
    3 hours ago

    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.

    • Lem453@lemmy.ca
      link
      fedilink
      English
      arrow-up
      5
      ·
      3 hours ago

      If you check the github discussion from the devs that patched the issue it doesn’t seem intentional to me (not an expert). That being said I assumed the same thing.

      My browser auto updated the extension at a very inopportune time and from some reason KDE connect from my phone to computer which is usually very reliable also wouldn’t connect. Was quite annoying until I realized I can just log into the vaultwarden website directly. I don’t think I’ve done that in years

    • Lem453@lemmy.ca
      link
      fedilink
      English
      arrow-up
      6
      ·
      3 hours 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
      9
      arrow-down
      22
      ·
      5 hours ago

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

      • hellmo_luciferrari@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        32 minutes ago

        Passbolt pales in comparison. The fact I can only get the android app from google play. No thanks. That is a deal breaker right there. I am working towards moving 100% off from google play.

        After quickly spinning up a container of it; it feels very unpolished and can’t say it will replace Bitwarden/Vaultwarden for me.

      • Patrick@ppb.social
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        2 hours 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.

      • cron@feddit.org
        link
        fedilink
        English
        arrow-up
        15
        ·
        4 hours 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.

      • SatyrSack@quokk.au
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        2
        ·
        2 hours ago

        Bitwarden has been in decline for a while. This is definitely not the first sign.

  • Darkassassin07@lemmy.ca
    link
    fedilink
    English
    arrow-up
    22
    ·
    6 hours 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! :)

    • myrmidex@belgae.social
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      3 hours ago

      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 😆

    • fozid@feddit.uk
      link
      fedilink
      English
      arrow-up
      5
      ·
      4 hours ago

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

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

    • dditty@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      6 hours ago

      Yeah I updated bitearden yesterday and my vault would not load any items. Glad this bug is already fixed!

    • Bazoogle@lemmy.world
      link
      fedilink
      English
      arrow-up
      15
      ·
      6 hours ago

      Per the vault warden release notes:

      We strongly advice to update as soon as possible.

      With the vulnerabilities being patched these days, it seems ill asvised to disable automatic updates for something as critical as a password manager.

      • irmadlad@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 hours ago

        it seems ill asvised to disable automatic updates

        I use the WatchTower fork for now, but I use it with the run once flag:

         volumes:
              - /var/run/docker.sock:/var/run/docker.sock
            command: --run-once --cleanup
        

        So, when an update is available, I’ll delay updating until I am rather comfortable that all the early adopters have worked out all the bugs for me. LOL Thanks guys! You’re an invaluable service.