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!

Avatar for Username

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Firefox Sync: Unknown error

  • 2 件の返信
  • 23 人がこの問題に困っています
  • 9 回表示
  • 最後の返信者: Pedro

Pedro
Pedro
more options

I'm getting an "unknown error" in Firefox Sync across my two computers. Here is the most recent error log:

http://pastebin.com/17HCcAzu

Using Pastebin because the log exceeds the 10,000 characters limit.

I'm getting an "unknown error" in Firefox Sync across my two computers. Here is the most recent error log: http://pastebin.com/17HCcAzu Using Pastebin because the log exceeds the 10,000 characters limit.

選ばれた解決策

These stand out: 1412074958242 Sync.Status DEBUG Status.login: error.login.reason.no_username => error.login.reason.no_recoverykey 1412074958242 Sync.Status DEBUG Status.service: service.client_not_configured => service.client_not_configured

I think you may be affected by an old recovery key being stored. Is is possible to remove the account temporarily and sign in to sync one more time?

I also added this to the 503 error, but it may be related [Bug 1073270]bugzilla etiquette

この回答をすべて読む 👍 0

すべての返信 (2)

guigs
guigs
more options

選ばれた解決策

These stand out: 1412074958242 Sync.Status DEBUG Status.login: error.login.reason.no_username => error.login.reason.no_recoverykey 1412074958242 Sync.Status DEBUG Status.service: service.client_not_configured => service.client_not_configured

I think you may be affected by an old recovery key being stored. Is is possible to remove the account temporarily and sign in to sync one more time?

I also added this to the 503 error, but it may be related [Bug 1073270]bugzilla etiquette

この投稿は guigs により に変更されました

Pedro
Pedro 質問者
more options

That's what I did, and it seems the error has disappeared. Nice to hear.

Thanks!