Locally hosted servers: How to teach Bitwarden autofill plugin that HTTP port matters?
I tried searching for this, but either it's not been asked before or the search engine got thoroughly confused about what I was asking.
I have a synology NAS. I host lots of docker containers running on non standard ports. e.g. http://192.168.1.1:1234/ and http://192.168.1.1:4567. I'm getting close to 10 services on different ports on the same server: 192.168.1.1
I use the bitwarden chrome plugin. Whenever I got to any of my services and am prompted to log in with autofill, I get suggested EVERY username/password on the 192.168.1.1 server, regardless of what port its hosted on. The port is stored in the bitwarden vault, but it's ignored.
Is there any way to get bitwarden's chrome plugin to be smart about which port it should be autofilling and only suggest one option, even if that means autofill works less often for other sites?
EDIT: We got it! Editing each item that matches, clicking the gear icon next to the URL, then setting "Match Detection" to "Host" instead of "Default" does the trick. ("Host" captures domain and port, "Exact" is a perfect URL match which can get a bit fuzzy on some sites. "Default" just matches the domain, by the looks of it.)
Thanks everyone!