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.
12 Comments
saffroncity@lemmy.world · 4 pts · 2y
You may want to look at setting the match detection. Setting the match detection to "host" should match on specified port numbers. https://bitwarden.com/help/uri-match-detection/#host
sabreW4K3@lazysoci.al · 3 pts · 2y
Tried that, it's not working ðŸ˜
Edit: it's working! 🎉
walden@sub.wetshaving.social · 4 pts · 2y
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.
sabreW4K3@lazysoci.al · 1 pts · 2y
Talking about the autofill. Though I'm a big fan of VaultWarden too.
walden@sub.wetshaving.social · 2 pts · 2y
Ohhh that makes sense.
IrateAnteater@sh.itjust.works · 2 pts · 2y
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.
testEmailVerified@lemmy.world · 2 pts · 2y
You can also just set it in the hosts file
sabreW4K3@lazysoci.al · 1 pts · 2y
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 · 0 pts · 2y
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 pts · 2y
It doesn't work.
I'm not
Kangie@lemmy.srcfiles.zip · 2 pts · 2y
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 pts · 2y
Host is working now, so it must've been an issue on my end. Thank you very much.