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!

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

Multiple problems with firefox sync

  • 4 odpovědi
  • 12 má tento problém
  • 2 zobrazení
  • Poslední odpověď od 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.

Zvolené řešení

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 :)

Přečíst dotaz v kontextu 👍 0

Všechny odpovědi (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

Zvolené řešení

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 :)