BitWarden is my password manager of choice, I use it a lot. But one thing I find frustrating and honestly, nonsensical, is why it doesn’t support ports out of the box? I have a bunch of services on different ports and would hope BitWarden would recognise that, but it doesn’t? It’s not a huge thing as I can always search, but it’s one of those little niggly things.

  • walden@sub.wetshaving.social
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 months ago

    I use Vaultwarden in Docker and I was able to change the port very easily. I’m not familiar with BitWarden’s own stack, but I can definitely recommend Vaultwarden.

    • sabreW4K3OP
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      8 months ago

      Tried that, it’s not working 😭

      Edit: it’s working! 🎉

  • IrateAnteater@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    8 months ago

    In addition to setting the host uri detection, you could put all your services behind a reverse proxy. Bitwarden would then easily detect the subdomain.

    • sabreW4K3OP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      8 months ago

      Reading one of the bugs on it, that was the route someone else took

      Edit: got it working with hosts. Thank you!

  • Kangie@lemmy.srcfiles.zip
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    8 months ago

    What? Bitwarden doesn’t give a shit about non standard ports on services you’re accessing. They’re a valid part of the URI string.

    Try changing your match detection settings in the add-on.

    If you’re talking about bitwarden not supporting being run from container on a non standard port, we’ll, you’re doing it wrong. Expose whatever port on the container then Add a proper reverse proxy / edge router like traefik, then set up some DNS and Let’s encrypt and only use 80 and 443 for all of your services.

    • sabreW4K3OP
      link
      fedilink
      English
      arrow-up
      2
      ·
      8 months ago

      They’re a valid part of the URI string.

      Try changing your match detection settings in the add-on.

      It doesn’t work.

      If you’re talking about bitwarden not supporting being run from container on a non standard port, we’ll, you’re doing it wrong.

      I’m not

      • Kangie@lemmy.srcfiles.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        8 months ago

        It should work with ‘host’ match detection. If it isn’t working check your URIs.

        Or do the sane thing and run everything on a different DNS and share 80/443.

        • sabreW4K3OP
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 months ago

          Host is working now, so it must’ve been an issue on my end. Thank you very much.