Synchronization data lost on server after password reset.




2 years ago
2 months ago


(Reporter: jurajbevilaqua, Unassigned)


Firefox Tracking Flags

(Not tracked)




2 years ago
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20161101104304

Steps to reproduce:

I have been using synchronization at work on gmail account. 

Actual results:

Everything was fine until some moment that I reinstalled windows installed firefox and putted it into synch. Bookmarks history nor theme is not synchronized anymore. I simply use same email adress maybe password was changed and when I click sync nothing happens.

Expected results:

Synchronization of firefoxes at work computers.


2 years ago
Component: Untriaged → Firefox Sync: Backend
Product: Firefox → Cloud Services
Version: 50 Branch → unspecified
Did you reset your Firefox Accounts password?

Comment 2

2 years ago
Yes, Ive lost my pw on gmail acc so I did the reset. What now? New gmail acc for sync? I need to do it on our PCs at work.
If you do a password recovery your sync account will be reset. All sync data is encrypted by your browser with your password before it gets to the servers. So if you forget your password and reset it, we have to reset your sync account data too.
Flags: needinfo?(markh)
Hi Jurav, we're sorry you have this problem, but as described in, the string encryption used by sync means that resetting your password (as opposed to changing it) causes all data to be lost on the server, so only the data that still exists on devices you can reconnect with your new password. The form used to reset your password also warns about this, so unfortunately there's nothing we can do here to help you.
Last Resolved: 2 years ago
Flags: needinfo?(markh)
Resolution: --- → INVALID
Summary: Synchronization does not work → Synchronization data lost on server after password reset.


2 months ago
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.