Bitwarden

763 readers

110 users here now

Discuss the Paswordmanager Bitwarden.

founded 1 year ago

MODERATORS

wuffa@discuss.tchncs.de

BitWarden's "Lack" Of Self Hosted Site Support (lazysoci.al)

submitted 7 months ago by sabreW4K3@lazysoci.al to c/bitwarden@discuss.tchncs.de

12 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] Kangie@lemmy.srcfiles.zip 0 points 7 months ago* (last edited 7 months ago) (1 children)

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.

[–] sabreW4K3@lazysoci.al 2 points 7 months ago (1 children)

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 2 points 7 months ago (1 children)

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.

[–] sabreW4K3@lazysoci.al 1 points 7 months ago

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