Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

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

  • 2 odpowiedzi
  • 2 osoby mają ten problem
  • 4 wyświetlenia
  • Ostatnia odpowiedź od 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.

Wybrane rozwiązanie

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.

Przeczytaj tę odpowiedź w całym kontekście 👍 1

Wszystkie odpowiedzi (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

Wybrane rozwiązanie

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.