Device on LAN
http://ds1621:5000/#/signin comes up from bookmark to login box and Bitwarden\autofill says No matching logins. Username and Password are filled in. Does Bitwarden not accept this address?
@SierraFoothills and welcome to the Community!
I think you may be running into a known issue related to “http:” instead of “https:”:
Add the ability to disable unsecured HTTP page warning
I would like the ability to not have the unsecured HTTP page warning show up.
This is the warning in question:
It could be disabled on an item-by-item basis, or via trusting specific IPs/URLs, or globally disabled. Any would work for my use case.
The current behavior is not ideal for me because of the setup of an internal/selfhosted site. It is behind a reverse-proxy with SSL for HTTPs, but I also…
Does that match what is happening to you?
@SierraFoothills and welcome to the community,
Could you perhaps be using the Samsung Internet browser, or otherwise be on mobile?
When using the Bitwarden app with Samsung Internet, it has troubles with local hostnames and IP addresses.
It does not recognize them correctly. The name of the site will show up as “–” when adding them, and although it shows the right URI in the website field, it will not match them.
The workaround is to visit the sites by IP address instead, but it is still buggy as it does not match on portnumbers, no matter what matching setting you pick.
Will this ever be fixed?
I reported this using the Google Forms as well (at least I hope I did) but never heard back so I thought to post here as well. I use custom dns aliases for some internal systems which are just simple hostnames without a domain; this works without problems on desktops operating systems (MacOS, ChromeOS, Linux), however on mobile devices (iOS + iPadOS) Bitwarden has trouble matching the hostname to the saved entry and I need to manually search for it. Is this something on the radar for the de…
Otherwise the below post may assist with your questions, I believe there have been some changes but the
Host auto-fill option appears to continue to work for both the browser extension and mobile apps respectively.
Thanks for the ping, I actually had this post bookmarked for review later on so this helped bring it to my forefront.
Unfortunately I’ve never come across this issue similarly within my internal networks. My home network is using a personal valid domain.tld and all internal devices have linked hostnames for my internal subdomain. Our work’s network is a .local which as it appears in the linked
seems to be a valid public suffix per the
jamescridland commented on Oct 31, 2021
My browser (Firefox) complains about it being insecure but I can fill it in manually and it works. Bitwarden will launch it but then does not see it to fill it in.
The simple answer here is to not use
http://ds1621:5000 on my local network, which works but Bitwarden doesn’s see as a valid URL but to use http://192.168.1.122:5000 (it’s IP address) which Bitwarden does see and fills in. The question is and was why doesn’t Bitwarden see ds1621. LastPass did…but I don’t want to go there.
Problem solved. After a bit of reading “Match detection options” changing from Default detection to Host detection made it work. This is good stuff.