Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Search Support

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

This thread was archived. Please ask a new question if you need help.

Firefox Sync: Unknown error

  • 2 replies
  • 23 have this problem
  • 34 views
  • Last reply by Pedro
  • Solved

Pedro
Pedro

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.

Chosen solution

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

Read this answer in context 👍 0

All Replies (2)

guigs
guigs

Chosen Solution

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

Modified by guigs

Pedro
Pedro Question owner

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

Thanks!