We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

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

  • 2 antwoorden
  • 2 hebben dit probleem
  • 4 weergaven
  • Laatste antwoord van 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.

Gekozen oplossing

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.

Dit antwoord in context lezen 👍 1

Alle antwoorden (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

Gekozen oplossing

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.