You might also check your email account for messages from Bitwarden. At a minimum, there should be “good” ones from when you first signed up and logged in. These can help validate that you used the login-email you think you did, and they can also tell you if you are using the eu or the com vault, based on where the email was sent from. You should also be pay attention to any recent messages that may be “bad” or “suspicious”.
You can try creating a new account using the email and vault eu/com you think you used. If you guess right, it will fail saying “already exists”.
Maybe press “capslock” to see if you actually set your password to the “opposite” of what you think it is. Maybe substitute ones with ells, zeros with ohs, etc. to see if maybe you wrote it down unclearly. Try also capitalizing the letter after a case-transition. (e.g Password1 vs PAssword1) to see if it was typed incorrectly in the first place.
Do you have MFA set up? Is it blowing up on the password or the MFA?
It might be helpful to post a screenshot of the page immediately before the error and also the error itself, of course blurring any identifiable information. Maybe someone will notice a pesky detail.
Did you set up emergency access? If so, that could be your white knight.
You might try uninstalling one of the local apps/extensions, removing any local storage, rebooting and reinstalling the app to see if there is some sort of corruption (this would not explain a web-vault issue, though).
Have you ever backed-up/exported and maybe stashed a copy somewhere?
When you migrated to Bitwarden, did you keep the exports from the predecessor, or do you maybe still have the predecessor laying around awaiting a fresh export?
I hesitate to throw up artificial blinders when troubleshooting. Additional admittedly rare possibilities:
- IP being blacklisted on the Bitwarden side (support can check) or firewalling on corporate devices.
- Someone could have gotten access to the registered email and deleted the vault without ever knowing vault creds.
- Some sort of version mis-match problem, like we often see when Vaultwarden (a 3rd party thing) is involved.
In a way, the crowd-strike issue of a few months back was an example. Have there been large scale instances of it with Bitwarden? I do not believe so, given that they would have lit-up both this community and reddit with questions/complaints.