This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Why does Firefox Sync say my recovery key has been changed when I do not have another device to change it?

  • 2 (ردّان اثنان)
  • 2 have this problem
  • 4 views
  • آخر ردّ كتبه Emeret

more options

I am trying to perform my first sync, but the progress bar on the tab that opens up does not move. I've left it overnight and still no change. When I click sync now, a message appears stating that I am using the Wrong Recovery Key. I've tried using the same key, and generating a new one several times with no success.

I am trying to perform my first sync, but the progress bar on the tab that opens up does not move. I've left it overnight and still no change. When I click sync now, a message appears stating that I am using the Wrong Recovery Key. I've tried using the same key, and generating a new one several times with no success.

الحل المُختار

I figured out the issue, FIPS was preventing the sync. Unfortunately, the error logs were not too helpful, there were constant references to logon errors with error.login.reason.recoverykey and no tracebacks.

Either way, once FIPS was disabled sync started to work. That level of encryption is probably overkill for standard web browsing anyway.

Read this answer in context 👍 1

All Replies (2)

more options

Hi,

You can type about:sync-log in the location (address) bar to check the helpful messages. You can also try deleting the current account and start afresh.

Please also see this detailed (three steps) setup help.

Firefox Sync

Sync QA

more options

الحل المُختار

I figured out the issue, FIPS was preventing the sync. Unfortunately, the error logs were not too helpful, there were constant references to logon errors with error.login.reason.recoverykey and no tracebacks.

Either way, once FIPS was disabled sync started to work. That level of encryption is probably overkill for standard web browsing anyway.