Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

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

  • 2 respostas
  • 2 têm este problema
  • 4 visualizações
  • Última resposta de 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.

Solução escolhida

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.

Ler esta resposta 👍 1

Todas as respostas (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

Solução escolhida

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.