I have in issue logging in to my local home server using a hostname when two URIs are present for that login. If I have both hostname and IP saved as URIs Bitwarden does not autofill the username - only the password. Interestingly, if I go into Bitwarden extension and manually click on the login it fills in both username and password. See screenshot. Am I doing something wrong?
I tried changing the match detection options for both URIs but no change. Before anyone asks I do have a need to use both hostname and IP at different times and would love to have a single entry for both (as the username/password will always be the same for both). Am I missing something here or is this a bug?
I tried to add a full URL to the IP one but that didn’t make any difference (I have actually saved the URIs and opened edit again for you to see the full URL :). The behaviour is the same whether I go to the URL with the hostname or the IP address - password autofills but not the username.
These are my autofill settings as requested. Note, I have tried all domain matching options but that didn’t help. The only thing that helps so far is removed the URI with the IP address.
For the URI2 field, (which has the IP address stored), what happens if you click the icon next to the IP address, and then change the value in the dropdown menu to “Host”?
Nothing changes - same issue. I tried various combinations of match detection for both, i.e. default-default; basedomain-default; host-default; basedomain-basedomain; basedomain-host (your suggestion); host-host.
And just to be crystal clear the hostname lifeboat.local is actually for the same machine as the IP address 192.168.1.3. And the issue persists whether I go to the hostname adress or the IP address in the browser.
I find it really peculiar that it autofills the password and not the username (and also it fills in both if I delete the IP address). To me that suggests that the issue isn’t so much detection (I mean, it does know to fill in the password) but something somewhere gets confused about the username… What’s even weirder is that it does autofill the username if I go to the extension and click on the entry there. That to me suggests that manually triggering autofill and automatic autofill are somehow different processes. I would naturally expect it to never fill in the username if there was an issue with detection of the username fields or something similar.
I think you mentioned somewhere that you had a second (non-admin) account for this same site. To reduce the number of moving parts in this puzzle, could you disable the other login item, either by temporarily deleting it (you can recover it from the Trash folder within 30 days), or by editing it to set the URI matching the “Never” for every URI stored in the item (and for good measure, also set the item’s setting for “Auto-fill on page load if set up in Options” to “Do not auto-fill”).
In fact, please use the following two search expressions to make sure that you have found every login item that may be interacting with this site (then delete/disable all such items except for the admin account that we are troubleshooting):
>login.uris:*192.168.1.3*
>login.uris:*lifeboat.local*
Then check the admin account again, with and without the IP address as URI2.
I’m afraid there’s no second account for this server, I haven’t said that anywhere. This is the only account. I have used the two suggested terms and this admin account is the only one that comes up.
It just occured to me that I had another server running different software which also has two URI’s in Bitwarden - one with a hostname; another with an IP address. This one seems to work fine. After some trial and error I discovered that this other server uses HTTP to login (as opposed to HTTPS which the Lifeboat server in question uses).
I went to the same lifeboat.local server using HTTP and autofill works. Now it’s not a solution to my issue since I do need to use HTTPS for this server however maybe it shines some light on what the issue could be? I’m afraid the second server does not support HTTPS so I can’t replicate the problem on that server.
At this point I’m tempte to think it’s a bug. I could post a bug report however it doesn’t sound like this would be a particularly important issue to be solved.
Yea, I would suggest posting a bug report using the New Issue button on GitHub.
To avoid misunderstanding, I recommend referring to your auto-fill problem using the term “auto-fill on page load” or “automatic auto-fill” (to distinguish from the on-demand auto-fill that can be done by clicking the item in the browser extension pop-up, or using keyboard shortcuts, etc.). BY itself the term “auto-fill” encompasses both automatic and on-demand auto-filling functions.
In addition, I would suggest including a link to this thread in your bug report.
icon next to the IP address, and then change the value in the dropdown menu to “Host”?