Can't login to existing Sync account or create a new account
I hope Mozilla isn't winding down the slow path to the heap of once useful software that no longer is worth the trouble. Make it useful and make it so that it works and you will own the world. (Think Apple, most of the time)
Started getting the "can't sync" messages on my PC's a few weeks ago. Decided today to dive into it. Tried everything I could think of including:
1. Disabled Sync on all PC's
2. Refreshed or whatever it's called Firefox
3. Downloaded latest exe and installed over old FF
4. Tried everything in Safe mode
5. Turned off any AV and firewall software
6. Dug into the browser logs and it showed certificate issues with Mozilla side
7. Sync error logs - (not showing every line)
Not syncing: login returned false.
Status.login: error.login.reason.network => error.login.reason.network
Waiting for user to be verified.
already verified
Starting fetch for key bundle.
already verified
Getting an assertion from: https://token.services.mozilla.com/1.0/sync/1.5
enter getAssertion()
getKeyPair: already have a keyPair
error POSTing /certificate/sign: {"error":{},"errorString":"[Exception... \"<no message>\" nsresult: \"0x805a1ff3 (<unknown>)\" location: \"JS frame :: resource://services-common/rest.js :: onStopRequest :: line 460\" data: no]","message":null,"code":null,"errno":null}
HAWK.signCertificate error: {"error":{},"errorString":"[Exception... \"<no message>\" nsresult: \"0x805a1ff3 (<unknown>)\" location: \"JS frame :: resource://services-common/rest.js :: onStopRequest :: line 460\" data: no]","message":null,"code":null,"errno":null}
Non-authentication error in _fetchTokenForUser: {"error":{},"errorString":"[Exception... \"<no message>\" nsresult: \"0x805a1ff3 (<unknown>)\" location: \"JS frame :: resource://services-common/rest.js :: onStopRequest :: line 460\" data: no]","message":null,"code":null,"errno":null}
8. Unable to create a NEW account. "unexpected error"
Hearing lots of unfavorable things about the new Sync and where FF is headed. I am hopeful but not optimistic about things.
由gregzilla于修改
所有回复 (5)
Make sure that you allow cookies for the accounts.firefox.com domain if you aren't allowing cookies generally or use the 'Ask me' cookie setting. Various data is stored in localStorage and sessionStorage, so make sure that DOM storage is enabled.
Thanks. Did all of that with the same result.
Any other ideas from anyone? Not having the bookmarks synced is starting to cause major headaches for business productivity.
I really, really want to stay with FF. Have used it from the beginning and fully understand the implications of having/not having an open source major browser in the marketplace. For obvious reasons I would never consider IE. But if I can't get the Sync fixed I am going to have to change to something else. Most likely Chrome - and NOT because I want to but because I really need sync to work.
Sorry if my earlier comments were sarcastic. I just don't want to see FF slowly disappear.
Thanks
I figured it out. For any of you having problems with the new Sync (there are lots of posts out there from unhappy people) I have the fix.
If you revert back to FF 28 everything works great. FF staff will tell you about the gloom and doom of using older versions. They don't seem too concerned that those of us who have relied on Sync for years and probably only use FF because of Sync are unhappy with the new less secure version and in my case can't even register a new account.
I think you can get away with going up to higher versions and maintaining the old Sync. If anyone knows what the highest working version is please post it. I will probably upgrade one version at a time to see where it stops working and will post here.
If the old version of Sync works for you now with Firefox 28, my guess is that you never upgraded your Sync account for the new version of Sync that first came with Firefox 29. See this KB article - Sync your Firefox bookmarks, history, passwords and more - to see what users were supposed to do once they upgraded to Firefox 29 (or later), almost a year ago - 4-29-2014.