Closed Bug 1284319 Opened 10 years ago Closed 10 years ago

Firefox sync issue

Categories

(Firefox :: Sync, defect)

Product:
Firefox
Component:
Sync
Version:
47 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1284218

People

(Reporter: thomas, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0 Build ID: 20160623154057 Steps to reproduce: Firefox sync has stopped working on all of my 3 desktop devices, from different networks. No error is shown. The syncing silently fails. The sync log shows frequent failures over the last days. I don't know how long it has failed, it might have been for weeks. Seems like the used Firefox sync cluster is not working. All requests fail with NS_ERROR_CONNECTION_REFUSED. The sync cluster URL used is "https://sync-270-us-west-2.sync.services.mozilla.com/1.5/32824481/". Actual results: about:sync-log shows the following: 1467661241620 Sync.LogManager DEBUG Flushing file log 1467661241620 Sync.LogManager TRACE Beginning stream copy to error-sync-1467661241620.txt: 1467661241620 1467661241622 Sync.Service DEBUG Exception: Login failed: error.login.reason.network 1467661241622 Sync.Service DEBUG Not syncing: login returned false. 1467661241626 browserwindow.syncui DEBUG _loginFailed has sync state=error.login.reason.network 1467661241627 browserwindow.syncui DEBUG _loginFailed has sync state=error.login.reason.network 1467661241627 FirefoxAccounts TRACE not checking freshness of profile as it remains recent 1467661241627 FirefoxAccounts TRACE not checking freshness of profile as it remains recent 1467661241628 FirefoxAccounts TRACE not checking freshness of profile as it remains recent 1467661241629 browserwindow.syncui DEBUG observed: weave:ui:clear-error 1467661241645 Sync.LogManager TRACE finished copy to: C:\Users\xxx\AppData\Roaming\Mozilla\Firefox\Profiles\hu631j1n.default\weave\logs\error-sync-1467661241620.txt 1467661241645 Sync.LogManager TRACE onCopyComplete: 1467661241645 1467661241645 Sync.LogManager TRACE Scheduling cleanup. 1467661241645 Sync.LogManager DEBUG Log cleanup threshold time: 1466797241645 1467661241754 Sync.LogManager DEBUG Done deleting files. 1467661241934 Sync.ErrorHandler DEBUG Beginning user-triggered sync. 1467661241934 Sync.Service DEBUG User-Agent: Firefox/47.0.1 FxSync/1.49.0.20160623154057. 1467661241934 Sync.Service INFO Starting sync at 2016-07-04 21:40:41 1467661241935 Sync.Service DEBUG In sync: should login. 1467661241935 browserwindow.syncui DEBUG observed: weave:service:login:start 1467661241935 Sync.Status DEBUG Status.service: error.login.failed => success.status_ok 1467661241935 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1467661241935 Sync.Service INFO Logging in the user. 1467661241936 browserwindow.syncui DEBUG _loginFailed has sync state=error.login.reason.network 1467661241937 browserwindow.syncui DEBUG _loginFailed has sync state=error.login.reason.network 1467661241937 Sync.Service DEBUG Caching URLs under storage user base: https://sync-270-us-west-2.sync.services.mozilla.com/1.5/32824481/ 1467661241937 Sync.Service INFO User logged in successfully - verifying login. 1467661241937 Sync.BrowserIDManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys 1467661241937 Sync.Service DEBUG Fetching unlocked auth state returned success.status_ok 1467661241938 Sync.BrowserIDManager DEBUG _ensureValidToken already has one 1467661248597 Sync.Service DEBUG verifyLogin failed: Error: NS_ERROR_CONNECTION_REFUSED (resource://services-sync/resource.js:405:19) JS Stack trace: waitForSyncCallback@async.js:98:7 < Res__request@resource.js:398:14 < Res_get@resource.js:425:12 < verifyLogin@service.js:694:18 < onNotify@service.js:977:12 < WrappedNotify@util.js:146:21 < WrappedLock@util.js:101:16 < WrappedCatch@util.js:75:16 < login@service.js:988:12 < sync/<@service.js:1236:14 < WrappedCatch@util.js:75:16 < sync@service.js:1232:5 < Res_get@resource.js:425:12 < verifyLogin@service.js:694:18 < onNotify@service.js:977:12 < WrappedNotify@util.js:146:21 < WrappedLock@util.js:101:16 < WrappedCatch@util.js:75:16 < login@service.js:988:12 < sync/<@service.js:1236:14 < WrappedCatch@util.js:75:16 < sync@service.js:1232:5 1467661248598 Sync.Status DEBUG Status.login: error.login.reason.network => error.login.reason.network 1467661248598 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed 1467661248598 Sync.Status DEBUG Status.login: error.login.reason.network => error.login.reason.network 1467661248598 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1467661248599 browserwindow.syncui DEBUG observed: weave:service:login:error 1467661248599 browserwindow.syncui DEBUG onLoginError: login=error.login.reason.network, sync=success.sync 1467661248600 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1467661248601 Sync.SyncScheduler DEBUG Next sync in 3600000 ms. 1467661248601 Sync.ErrorHandler ERROR Sync encountered a login error Expected results: Sync should work. If it doesn't work (for whatever reason), I'd expect some message to appear.
I'm located in Germany. Is it correct that Firefox uses a US-based sync cluster URL?
Component: Untriaged → Sync
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.