Vault will not load in Chrome

[bituser]

For those that were assisting with these issues, Sync not working on Firefox extensions in multiple profiles, the faulty profile has been eliminated, as well as the sync problems, as far as I know,

I recently launched my Portableapps version of Chrome to discover everything was wiped out, lost. Essentially a fresh version. I reported it, but no solutions forthcoming.

First thing I did was to add Bitwarden, but the weirdness continues. It was already logged in. I did not have to login to BW.

Finally, the vault will not load. Initially, it looked like this for a while

Then it eventually transitioned to this, where it remains

I also have a couple of unrelated issues. Please let me know if I need to post separately

I am using Firefox to post. These suggestions popped up, but the links don’t work. Not only that, but my browser is set to mark links in “red” when they are selected.

I have one other question. When I am logging into this community website, why am I offered “Vault” autofill suggestions? It’s a different web address, not to mention, I was under the impression that the last credentials used would gain the top position, but that is not the case.

Although the first selection is not identified as “Vault”, like the fourth autoifill suggestion, their credentials are identical.

[grb]

@bituser

I have one other question. When I am logging into this community website, why am I offered “Vault” autofill suggestions?

First, delete the duplicate login item for your Web Vault. Next ,edit the item hat you did not delete, and click the gear icon to the right of the https://vault.bitwarden.com website address (URI). This will toggle the visibility of a dropdown menu labeled “Match Detection”; in the dropdwon list, select the option “Host”, then click the Save button.

You can learn more about match detection here:

https://bitwarden.com/help/uri-match-detection/#match-detection-by-item

[bituser]

@grb

First, delete the duplicate login item for your Web Vault

Which one? The first, fourth?

How about the Chrome stuff?

[Neuron5569]

@bituser

I am using Firefox to post. These suggestions popped up, but the links don’t work. Not only that, but my browser is set to mark links in “red” when they are selected.

I tested this on a brand-new community account using my normal incognito Firefox profile, and I don’t have the same problems. Again, I suggest you test this with a brand-new profile to see if it’s related to your profile’s settings or extensions.

[grb]

@bituser

@grb

First, delete the duplicate login item for your Web Vault

Which one? The first, fourth?

Either one, according to your preference. Having duplicate login items for the same set of credentials is just inviting trouble.

[bituser]

I stated on my OP that this was with a fresh Chrome profile, not Firefox. I mentioned Firefox because I was using it to post this thread, and that’s where i was having the ‘You’re topic is similar to…) links problem. Are there plans to address that?

[bituser]

Should I expect vault credentials to appear as autofill suggestions on the community page?

Should I no longer expect the latest used autofill suggestion to appear at the top?

I just want to know what behavior to expect in the future for this site, and elsewhere, in general.

[Nail1684]

@bituser

Should I expect vault credentials to appear as autofill suggestions on the community page?

I think @grb already answered this here, including the link he provided there.

The community forum uses community.bitwarden.com as the domain.
The BW web vault uses vault.bitwarden.com as a domain.

If you choose “Base domain” as matching detection option, then only the base domain is needed for items to match – in this case bitwarden.com. So, you would get your item then as an autofill suggestion on community.bitwarden.com and vault.bitwarden.com, but also on (examples) abc.bitwarden.com or 123.bitwarden.com or whatever…

When you choose “Host” as a matching detection option instead, a login item would be only shown on the “complete” domain, e.g. only on community.bitwarden.com (or only on vault.bitwarden.com etc.).

(screenshot from that Help Site)

@bituser

Should I no longer expect the latest used autofill suggestion to appear at the top?

I just tried it myself, and with the latest extension 2025.12.1, the last autofill should appear at the top. (PS: Though, as I just tested something else, I had at least one instance where I used the keyboard shortcut to autofill a username, and then that used credential didn’t wander to the top. So there seems to be some kind of bug…)

@bituser

I just want to know what behavior to expect in the future for this site, and elsewhere, in general.

For that, I can only again recommend to have a read about all different matching detection options in the Help Sites: https://bitwarden.com/help/uri-match-detection/#set-match-detection

[Neuron5569]

@bituser

I mentioned Firefox because I was using it to post this thread, and that’s where i was having the ‘You’re topic is similar to…) links problem.

I was addressing the problem you had with the forum using Firefox.

[Nail1684]

@bituser

Should I expect vault credentials to appear as autofill suggestions on the community page?

… ah, and to answer this also directly: yes, when you chose “Base domain” then this is expected. When you chose another matching detection option (like “Host”) then this will not happen, i.e. the “Vault” credential will only be offered on vault.bitwarden.com and the “Community” login item will only be offered on community.bitwarden.com.

And of course, this is not limited to the “Vault” item. This is true for all login items and all websites – and how you like to configure autofill / match detection options there.

[bituser]

@grb

First, delete the duplicate login item for your Web Vault. Next ,edit the item hat you did not delete,

Done

@grb

First, delete the duplicate login item for your Web Vault. Next ,edit the item hat you did not delete, and click the gear icon to the right of the https://vault.bitwarden.com website address (URI). This will toggle the visibility of a dropdown menu labeled “Match Detection”; in the dropdwon list, select the option “Host”, then click the Save button.

Ok. Vault credentials no longer appear in community autofill suggestions. I’m going to document these instructions. Thank you for that

Please answer me this tho. Isn’t the app supposed to figure this sort of basic behavior/decision making itself? Particularly for the Bitwarden website? When you go into the ‘View Login”, the web address is “vault.bitwarden.com", but you have to go thru further settings manipulation to get it to work as you should expect in the first place?

In this example, shouldn’t “Host” have been the default when it was created? How does Bitwarden envision the average user will deal with this?

I’ve already stated how much I value & appreciate BW, but why make simple things unnecessarily complicated? Wouldn’t you experts rather be tackling real problems?

@Nail1684

… ah, and to answer this also directly: yes, when you chose “Base domain” then this is expected. When you chose another matching detection option (like “Host”) then this will not happen, i.e. the “Vault” credential will only be offered on vault.bitwarden.com and the “Community” login item will only be offered on community.bitwarden.com.

Well, there you are. All I ask is to to be able to log into websites. Does BW really expect a dummy like me to know the difference between “Base domain” and “Host”. I picked “Base domain” because it sounds “basic”, which is basically how I intend to use BW. I didn’t know I needed to read a manual for fundamental usage.

[Nail1684]

@bituser

In this example, shouldn’t “Host” have been the default when it was created? How does Bitwarden envision the average user will deal with this?

I’ve already stated how much I value & appreciate BW, but why make simple things unnecessarily complicated? Wouldn’t you experts rather be tackling real problems?

@Nail1684

… ah, and to answer this also directly: yes, when you chose “Base domain” then this is expected. When you chose another matching detection option (like “Host”) then this will not happen, i.e. the “Vault” credential will only be offered on vault.bitwarden.com and the “Community” login item will only be offered on community.bitwarden.com.

Well, there you are. All I ask is to to be able to log into websites. Does BW really expect a dummy like me to know the difference between “Base domain” and “Host”. I picked “Base domain” because it sounds “basic”, which is basically how I intend to use BW. I didn’t know I needed to read a manual for fundamental usage.

Well, that is a question worth to discuss.

But just an example that is true for many websites (if not exactly, then it’s similar): if “Host” was the default, then a “dummy” would certainly have issues when they only added www.example.com to a login item… Because when the login form would then not be on www.example.com, but e.g. on account.example.com, that “dummy” would not get any autofill suggestions on account.example.com for that login item.

And they probably would protest why “Host” would be the default and if that wouldn’t make it unnecessarily complicated for many sites to get autofill suggestions and use Bitwarden for easily logging in…

[grb]

@bituser

Please answer me this tho. Isn’t the app supposed to figure this sort of basic behavior/decision making itself? Particularly for the Bitwarden website? When you go into the ‘View Login”, the web address is “vault.bitwarden.com", but you have to go thru further settings manipulation to get it to work as you should expect in the first place?

If you want for the Bitwarden autofill function to automatically always treat aaa.example.com as different from bbb.example.com, then simply go to Settings > Autofill > Additional Options, and select “Host” for the option named “Default URI match detection”.

If you do this, then you never have to customize the match detection settings for individual website addresses (using the ). All website addresses in your login items will use the match detection method specified in Settings > Autofill > Additional Options* — unless you use the icon to select a non-default match detection method.

For most users, “Base Domain” works very well as the “Default URI match detection” method (which is why “Base Domain” is the selection that has been pre-configured in new installations of the browser extension), but it sounds like you might be happier if you set the default match detection option to “Host”.

[bituser]

@Nail1684

Well, that is a question worth to discuss.

@grb

If you want for the Bitwarden autofill function to automatically always treat aaa.example.com as different from bbb.example.com, then simply go to Settings > Autofill > Additional Options, and select “Host” for the option named “Default URI match detection”.

After reading reading the posts about 10 times, I “think” I’m beginning to very basically understand. I don’t want to be distracted from my work to have to deal with this from site to site. Maybe I’m a bit too sensitive to the situation because of the duplicate bug, and now having to manually edit the autofill suggestions now on many of the websites I visit, and the fact that apparently the last autofill is still not taking the top position, at least in some cases.

It sounds like staying with “Base Domain” would be the logical choice for my purposes.

I can still use “Host” on individual sites, right?

[Nail1684]

@bituser

I can still use “Host” on individual sites, right?

Only to that: of course! Besides the “Default URI match detection” (Settings → Autofill) as the default for all URIs, you can also set an individual match detection option for every single URI in any login item, that then “deviates” from the “default”:

(–> in “Edit Login” or “New Login”…)

[DenBesten]

I’d also suggest reading through Bitwarden’s help page on the topic that @Nail1684 earlier linked.

https://bitwarden.com/help/uri-match-detection/#set-match-detection

When match detection is well set up, Bitwarden autofill becomes much more convenient. And bonus, it also helps keep credentials from being incorrectly entered on the “wrong” site (especially when using host match detection). It is a rare case of simultaneously improving both usability and security.

The help page is one of those pages you ought to revisit a few times over a few months, because thing become much clearer as your experience grows.

[bituser]

@Nail1684

Thanks

[bituser]

I will check it out. Thanks

[Nail1684]

@bituser From your original post here:

@bituser

First thing I did was to add Bitwarden, but the weirdness continues. It was already logged in. I did not have to login to BW.

Finally, the vault will not load. Initially, it looked like this for a while

That is indeed weird, when you install the BW extension and don’t have to log in. Did you install the BW extension before on that particular Chrome browser?

Whatever happened – the BW apps don’t login on their own.

To the “vault will not load” issue:

• this was reported before
• there doesn’t seem to be a perfect working solution
• I think what did seem to help some users: deleting the used Chrome profile / using a fresh Chrome profile… and deinstalling the BW extension, deleting the local data of the BW extension, restarting the device, reinstalling the BW extension and logging in again

[bituser]

@Nail1684

To the “vault will not load” issue:

i uninstalled/reinstalled. Works now.