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

NS_ERROR_CONNECTION_REFUSED

  • No replies
  • 3 have this problem
  • 14 views
more options

Sync is failing. Log below. I'm able to successfully login to accounts.firefox.com, however.

1441736838599 Sync.LogManager DEBUG Flushing file log 1441736838599 Sync.LogManager TRACE Beginning stream copy to error-sync-1441736838599.txt: 1441736838599 1441736838601 Sync.Service DEBUG Exception: Login failed: error.login.reason.network No traceback available 1441736838601 Sync.Service DEBUG Not syncing: login returned false. 1441736838676 Sync.LogManager TRACE finished copy to: C:\Users\halachmi\AppData\Roaming\Mozilla\Firefox\Profiles\0i7y7gr6.default\weave\logs\error-sync-1441736838599.txt 1441736838676 Sync.LogManager TRACE onCopyComplete: 1441736838676 1441736838677 Sync.LogManager TRACE Scheduling cleanup. 1441736838677 Sync.LogManager DEBUG Log cleanup threshold time: 1440872838677 1441736838786 Sync.LogManager DEBUG Done deleting files. 1441736912415 Sync.Tracker.History DEBUG Saving changed IDs to history 1441737009461 Sync.ErrorHandler DEBUG Beginning user-triggered sync. 1441737009468 Sync.Service DEBUG User-Agent: Firefox/38.2.1 FxSync/1.40.0.20150826044534. 1441737009468 Sync.Service INFO Starting sync at 2015-09-08 14:30:09 1441737009468 Sync.Service DEBUG In sync: should login. 1441737009469 Sync.Status DEBUG Status.service: error.login.failed => success.status_ok 1441737009469 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1441737009517 Sync.Service INFO Logging in the user. 1441737009517 Sync.Service DEBUG Caching URLs under storage user base: https://sync-248-us-west-2.sync.services.mozilla.com/1.5/28798625/ 1441737009518 Sync.BrowserIDManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys 1441737009519 Sync.Service DEBUG Fetching unlocked auth state returned success.status_ok 1441737009521 Sync.BrowserIDManager DEBUG _ensureValidToken already has one 1441737016533 Sync.Service DEBUG verifyLogin failed: Error: NS_ERROR_CONNECTION_REFUSED (resource://services-sync/resource.js:409:18) JS Stack trace: waitForSyncCallback@async.js:102:6 < Res__request@resource.js:405:13 < Res_get@resource.js:429:11 < verifyLogin@service.js:728:17 < onNotify@service.js:1008:11 < WrappedNotify@util.js:148:20 < WrappedLock@util.js:103:15 < WrappedCatch@util.js:77:15 < login@service.js:1019:11 < sync/<@service.js:1269:13 < WrappedCatch@util.js:77:15 < sync@service.js:1265:4 < Res_get@resource.js:429:12 < verifyLogin@service.js:728:18 < onNotify@service.js:1008:12 < WrappedNotify@util.js:148:21 < WrappedLock@util.js:103:16 < WrappedCatch@util.js:77:16 < login@service.js:1019:12 < sync/<@service.js:1269:14 < WrappedCatch@util.js:77:16 < sync@service.js:1265:5 1441737016533 Sync.Status DEBUG Status.login: error.login.reason.network => error.login.reason.network 1441737016533 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed 1441737016533 Sync.Status DEBUG Status.login: error.login.reason.network => error.login.reason.network 1441737016534 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1441737016534 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1441737016535 Sync.SyncScheduler DEBUG Next sync in 3600000 ms.