Sync has a "non-authentication error"
Just noticed that I haven't had a successful sync for 2-3 weeks now, see the following sync log. Any ideas?
1433531181146 Sync.Tracker.Clients DEBUG Saving changed IDs to clients 1433531181149 Sync.Tracker.Passwords DEBUG Saving changed IDs to passwords 1433531181152 Sync.Tracker.Bookmarks DEBUG Saving changed IDs to bookmarks 1433533307307 Sync.SyncScheduler DEBUG Woke from sleep. 1433538251610 Sync.SyncScheduler DEBUG Woke from sleep. 1433538252278 Sync.Service DEBUG User-Agent: Firefox/38.0.5 FxSync/1.40.0.20150525141253. 1433538252278 Sync.Service INFO Starting sync at 2015-06-05 14:04:12 1433538252283 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1433538252284 Sync.Status INFO Resetting Status. 1433538252284 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1433538252285 FirefoxAccounts DEBUG already verified 1433538252286 Sync.BrowserIDManager INFO Getting an assertion from: https://token.services.mozilla.com/1.0/sync/1.5 1433538252286 FirefoxAccounts DEBUG enter getAssertion() 1433538252330 FirefoxAccounts DEBUG getKeyPair: already have a keyPair 1433538252330 FirefoxAccounts DEBUG getCertificate already had one 1433538252330 FirefoxAccounts DEBUG getAssertionFromCert 1433538252665 FirefoxAccounts DEBUG getAssertionFromCert returning signed: true 1433538252666 Sync.BrowserIDManager DEBUG Getting a token 1433538252666 Common.TokenServerClient DEBUG Beginning BID assertion exchange: https://token.services.mozilla.com/1.0/sync/1.5 1433538252785 Sync.BrowserIDManager ERROR Non-authentication error in _fetchTokenForUser: TokenServerClientNetworkError({"error":{}}) (resource://gre/modules/services-common/tokenserverclient.js:36:35) JS Stack trace: @tokenserverclient.js:36:36 < @browserid_identity.js:14:1 < @status.js:15:1 < SyncServiceObserver.init@sync.js:76:62 < @sync.js:459:1 < require@bootstrap.js:137:7 < @main.js:30:1 < require@bootstrap.js:137:7 < startup@bootstrap.js:21:3 < XPI_callBootstrapMethod@XPIProvider.jsm:4451:9 < XPI_startup@XPIProvider.jsm:2168:13 < callProvider@AddonManager.jsm:208:12 < _startProvider@AddonManager.jsm:669:5 < AMI_startup@AddonManager.jsm:840:9 < AMP_startup@AddonManager.jsm:2471:5 < AMC_observe@addonManager.js:55:7 1433538252786 Sync.Status DEBUG Status.login: success.login => error.login.reason.network 1433538252786 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed 1433538252818 Sync.BrowserIDManager ERROR Failed to fetch a token for authentication: TokenServerClientNetworkError({"error":{}}) (resource://gre/modules/services-common/tokenserverclient.js:36:35) JS Stack trace: @tokenserverclient.js:36:36 < @browserid_identity.js:14:1 < @status.js:15:1 < SyncServiceObserver.init@sync.js:76:62 < @sync.js:459:1 < require@bootstrap.js:137:7 < @main.js:30:1 < require@bootstrap.js:137:7 < startup@bootstrap.js:21:3 < XPI_callBootstrapMethod@XPIProvider.jsm:4451:9 < XPI_startup@XPIProvider.jsm:2168:13 < callProvider@AddonManager.jsm:208:12 < _startProvider@AddonManager.jsm:669:5 < AMI_startup@AddonManager.jsm:840:9 < AMP_startup@AddonManager.jsm:2471:5 < AMC_observe@addonManager.js:55:7 1433538252908 Sync.Status DEBUG Status.sync: success.sync => error.login.reason.network 1433538252908 Sync.Status DEBUG Status.service: error.login.failed => error.sync.failed 1433538252909 Sync.SyncScheduler DEBUG Next sync in 3600000 ms.
All Replies (4)
hello, can you reach the https://token.services.mozilla.com/1.0/sync/1.5 url when you try to access it manually?
I can reach https://token.services.mozilla.com/1.0/sync/1.5; the response is {"status": "error", "errors": [{"location": "body", "name": "", "description": "Unauthorized"}]}
ok, that looks alright - can you try to create a new profile for testing purposes and see if you can sync successfully there? (this would be to determine if it's a problem with the network or the individual configuration)
If I create a new profile, and connect it to the same Firefox account, the bookmarks etc show up (probably missing recent changes).
about:sync-log is empty, even after doing a "Sync Now" from the menu...