Sync not working on Firefox extensions in multiple profiles

I believed I established clearly that profile 1 is my '“main”.

What I’m finding most difficult to reconcile is that we have established/verified the valid connection/relationship with the cloud database from profile 1. So, why are we looking to my browser for the problem?

Yes, I’m aware that’s what a “sync’ is designed to do. “Some” cloud database? Sorry, I’m really trying not to be difficult, but you used the term “ambiguous” before. Some “arbitrary” cloud database?

I just performed a sync. I assume it means that it “syncs” with the whatever was previously stored in the database.

So, we’re back to the beginning. If the “sync”,which, which has been established, by conventional means, via the web developer exercise you proposed and by manual sync as seen below, and hypothetically done it’s job, then what has then where is the evidence?

What do you think would happen if I uninstalled/reinstalled BW in profile 1. What would you expect t see after logging in? The contents of profile 1 or 2?

@bituser For the general understanding…

  • What Windows version are you using?
  • And what Firefox version?
  • What are your session timeout settings (interval and action) for your different profiles?
  • Could you – in a general sense – say how you “treat” Firefox? (e.g. do you open and close Firefox several times a day – or do you practically never close Firefox and your PC runs 24/7? etc.)
  • Did you apply some specific configurations on your computer and/or on Firefox? (like network rules, firewall, AV programs…)
1 Like

I feel like we’re going in circles.

I have already explained how Bitwarden’s password manager is supposed to work (i.e., how it works for other users). To recap, each Bitwarden account (as defined by its email address and server URL) has but one single cloud database, which is the master database that coordinates the data on all devices and client apps used by the account holder. For individual (non-organization) vaults, when a change (e.g., edits, new items added, existing items deleted) is made in any app or browser extension (on any device, browser, or browser profile), that change is immediately uploaded to the unique cloud database. From there, the change is synchronized to all other logged-in apps or browser extensions, within seconds (via Live Sync based on Websockets technology). If the server is unavailable when the user attempts to make a change in the vault, the user will not be able to save the change locally — there will be an error message (e.g., “Failed to Fetch”).

Thus, by design, different instances of Bitwarden (e.g., different browser extensions or apps) should not become desynchronized. Unfortunately, in your case, you are evidently seeing different states of your vault data using different instances of the browser extension. Neither you nor I know why. Because it is a mystery at this point, all bets are off — i.e., any attempt to reason logically because the premises are not valid.

Your Profile 2 is at least able to synchronize with another client (the Web Vault) as expected; for this reason, I trust that version more. I have no idea how your Profile 1 is able to synchronize its data with any database without also affecting Profiel 2, which is why I have to be ambiguous about where Profiel 1 is sending its data (and from where it is receiving data when logging in from a blank slate).

 

There is no way to predict this, because of the unknown cause of your symptoms. If I had to guess, I would say that if reinstalling the extension in Profiel 1 fixes the problem, then it would be more likely to get a copy of what you see in Profile 2.

Did you ever create a brand new profile for testing purposes (as suggested 10 days ago by @Neuron5569)? If so, which vault state appears when you install the browser extension there and log in?

That;s why I said earlier that I was done, and i don’t expect answers.

But I hope you understand that I’m trying to understand. That’s why I ask questions relating to your explanations, so hopefully my curiosity is informed, makes sense, to avoid wasting our time.

I just tested BW in a fresh profile. As we expected, it synced with profile 2. And, as much as I would like to pass along the autofill suggestion changes from profile 1, can we say for sure i won’t also be passing along the problems?

I suppose I could import the profile 1 into profile 2, and see what happens, and If the sync problem is re-created, I could try to reverse things by then importing the profile 2 vault, but who knows what happens then? Is It worth the gamble?

That’s a rhetorical question. Just thinking out loud.

We can’t say anything for sure until we know what is going on with your Profile 1.

As I advised earlier, I personally would not recommend blindly importing Profile 1 data into Profile 2 until you/we have a better understanding of the data in Profile 1. I don’t think that the sync problems are contagious, but I would not have a lot of trust in the integrity of the data exported from Profile 1 without doing some inspection of that data. If Profile 1 has been preventing the browser extension from properly exchanging data with your cloud database, then who knows what could be missing or corrupted in your Profile 1 export? Even if your sync problem doesn’t re-appear after importing the Profile 1, how can you trust that your vault is intact (and how long would it take for you to start noticing issues in the vault contents?)?

I already gave you an approach for comparing the two vault states. Do you wish to try it?

Frankly, I don’t know If I am capable. I understand the concept.

When you first mentioned the spreadsheets, my first thought was file comparison tools, which sounds similar to this de-duplication feature.

I have Excel 2007. Haven’t used it in quite a while.