This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Multiple problems with firefox sync

  • 4 replies
  • 12 have this problem
  • 2 views
  • Last reply by whyl

more options

I was using the old Firefox Sync and everything worked fine. I tried to switch to the new version with Firefox Accounts when it came out but it has been a pain ever since. Here are the problems I'm still having:

1) Nothing is synced between my desktop sessions (2 FF Nightly). No bookmarks, no history… In about:sync-logs, i have a huge list of logs that all say this:

1406103609386 Sync.ErrorHandler DEBUG Flushing file log. 1406103609388 Sync.BrowserIDManager ERROR Background fetch for key bundle failed: No keyFetchToken 1406103609388 Sync.BrowserIDManager ERROR Could not authenticate: No keyFetchToken 1406103609389 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1406103609389 Sync.SyncScheduler DEBUG Next sync in 600000 ms.

I tried loging out and back in, the palce maintenance add on, but still nothing.

2) I'm unable to connect my android device (HTC One M8 with up to date firefox v31) to sync. I get a "Connnexion impossible" (Impossible to connect) error message. Login & password are right.

Thanks for your help.

I was using the old Firefox Sync and everything worked fine. I tried to switch to the new version with Firefox Accounts when it came out but it has been a pain ever since. Here are the problems I'm still having: 1) Nothing is synced between my desktop sessions (2 FF Nightly). No bookmarks, no history… In about:sync-logs, i have a huge list of logs that all say this: 1406103609386 Sync.ErrorHandler DEBUG Flushing file log. 1406103609388 Sync.BrowserIDManager ERROR Background fetch for key bundle failed: No keyFetchToken 1406103609388 Sync.BrowserIDManager ERROR Could not authenticate: No keyFetchToken 1406103609389 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1406103609389 Sync.SyncScheduler DEBUG Next sync in 600000 ms. I tried loging out and back in, the palce maintenance add on, but still nothing. 2) I'm unable to connect my android device (HTC One M8 with up to date firefox v31) to sync. I get a "Connnexion impossible" (Impossible to connect) error message. Login & password are right. Thanks for your help.

Chosen solution

Ok, everything is fixed now, but I didn't do anything. FF Nightly bugged be about not being able to sync for a couple of days, I went to the settings and it asked be o re-auth. I did and this time it synced.

I immediately tried to sync my android phone as well, and again, this time it worked. Glad this is now working :)

Read this answer in context 👍 0

All Replies (4)

more options

Hi whyl, Please make sure that the HTC account does not have Firefox Sync (depricated) as well as make sure you can connect to [accounts.firefox.com]

Do you have cookies enabled? And do you have an antivirus or firewall that may be blocking a connection to the Firefox sync servers?

Looking forward to your reply.

more options

Someone filed Bug 1047700 which seems to match.

more options

Thank you for answering.

@guigs2: I can confirm that I don't have firefox sync installed. Loging in to accounts.firefox.com works from the phone. Cookies are enabled and there is no anti-virus or firewall that I'm aware of :/

@mewman: Maybe, though from what i can see the error logs are not the same.

more options

Chosen Solution

Ok, everything is fixed now, but I didn't do anything. FF Nightly bugged be about not being able to sync for a couple of days, I went to the settings and it asked be o re-auth. I did and this time it synced.

I immediately tried to sync my android phone as well, and again, this time it worked. Glad this is now working :)