Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

My Firefox devices stopped sync (win10, win7, raspbian, android)

  • 1 antwoord
  • 1 heeft dit probleem
  • 3 weergaven
  • Laatste antwoord van the-edmeister

more options

about:sync-log

1573387978968 Sync.LogManager DEBUG Flushing file log 1573387978971 FirefoxAccounts DEBUG FxAccountsProfileClient: Requested profile 1573387978971 FirefoxAccounts DEBUG getOAuthToken enter 1573387978976 FirefoxAccounts TRACE getCachedToken returning cached token 1573387978976 FirefoxAccounts DEBUG getOAuthToken returning a cached token 1573387978977 Services.Common.RESTRequest DEBUG GET request to https://profile.accounts.firefox.com/v1/profile 1573387978994 Sync.LogManager DEBUG Log cleanup threshold time: 1572523978994 1573387979023 Sync.LogManager DEBUG Done deleting files. 1573387979759 Services.Common.RESTRequest DEBUG GET https://profile.accounts.firefox.com/v1/profile 304 1573388006387 FirefoxAccounts DEBUG FxAccountsWebChannel message received: fxaccounts:fxa_status 1573388006388 FirefoxAccounts DEBUG fxa_status received 1573388006388 FirefoxAccounts DEBUG service: 30b11ae57025e70b 1573388006388 FirefoxAccounts DEBUG is private browsing: false 1573389100448 FirefoxAccounts INFO Polling device commands. 1573389100448 Sync.Service DEBUG User-Agent: Firefox/70.0.1 (Windows NT 10.0; Win64; x64) FxSync/1.72.0.20191030021342.desktop 1573389100449 Sync.Service INFO Starting sync at 2019-11-10 14:31:40 in browser session O1gxzMml8M5- 1573389100449 Sync.Service DEBUG In sync: should login. 1573389100450 Sync.Service INFO User logged in successfully - verifying login. 1573389100520 Sync.BrowserIDManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys 1573389100521 Sync.Status DEBUG Status.login: error.sync.reason.serverMaintenance => success.status_ok 1573389100521 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1573389100522 Sync.Service DEBUG Fetching unlocked auth state returned success.status_ok 1573389100580 Services.Common.RESTRequest DEBUG GET request to https://api.accounts.firefox.com/v1/account/device/commands?index=1 1573389101382 Services.Common.RESTRequest DEBUG GET https://api.accounts.firefox.com/v1/account/device/commands?index=1 200 1573389101383 Hawk DEBUG (Response) /account/device/commands?index=1: code: 200 - Status text: OK 1573389101383 Hawk DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -383 1573389101386 Sync.Resource DEBUG GET fail 503 https://sync-581-us-west-2.sync.services.mozilla.com/1.5/91863943/info/collections 1573389101386 Sync.Resource WARN GET request to https://sync-581-us-west-2.sync.services.mozilla.com/1.5/91863943/info/collections failed with status 503 1573389101389 Sync.Status DEBUG Status.login: success.status_ok => error.login.reason.server 1573389101389 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1573389101389 Sync.ErrorHandler DEBUG Got Retry-After: 3600 1573389101389 Sync.Status DEBUG Status.login: error.login.reason.server => error.sync.reason.serverMaintenance 1573389101389 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1573389101390 Sync.SyncScheduler DEBUG Got backoff notification: 3600000ms 1573389101390 Sync.SyncScheduler DEBUG Fuzzed minimum next sync: 1573392701390 1573389101391 Sync.ErrorHandler ERROR Sync encountered a login error 1573389101391 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1573389101421 Sync.SyncScheduler DEBUG Next sync in 4369256.143576094 ms. (why=schedule) 1573389101424 Sync.Service DEBUG Exception calling WrappedLock: Error: Login failed: error.sync.reason.serverMaintenance(resource://services-sync/service.js:984:15) JS Stack trace: onNotify@service.js:984:15 1573389101426 Sync.Service DEBUG Not syncing: login returned false.

about:sync-log 1573387978968 Sync.LogManager DEBUG Flushing file log 1573387978971 FirefoxAccounts DEBUG FxAccountsProfileClient: Requested profile 1573387978971 FirefoxAccounts DEBUG getOAuthToken enter 1573387978976 FirefoxAccounts TRACE getCachedToken returning cached token 1573387978976 FirefoxAccounts DEBUG getOAuthToken returning a cached token 1573387978977 Services.Common.RESTRequest DEBUG GET request to https://profile.accounts.firefox.com/v1/profile 1573387978994 Sync.LogManager DEBUG Log cleanup threshold time: 1572523978994 1573387979023 Sync.LogManager DEBUG Done deleting files. 1573387979759 Services.Common.RESTRequest DEBUG GET https://profile.accounts.firefox.com/v1/profile 304 1573388006387 FirefoxAccounts DEBUG FxAccountsWebChannel message received: fxaccounts:fxa_status 1573388006388 FirefoxAccounts DEBUG fxa_status received 1573388006388 FirefoxAccounts DEBUG service: 30b11ae57025e70b 1573388006388 FirefoxAccounts DEBUG is private browsing: false 1573389100448 FirefoxAccounts INFO Polling device commands. 1573389100448 Sync.Service DEBUG User-Agent: Firefox/70.0.1 (Windows NT 10.0; Win64; x64) FxSync/1.72.0.20191030021342.desktop 1573389100449 Sync.Service INFO Starting sync at 2019-11-10 14:31:40 in browser session O1gxzMml8M5- 1573389100449 Sync.Service DEBUG In sync: should login. 1573389100450 Sync.Service INFO User logged in successfully - verifying login. 1573389100520 Sync.BrowserIDManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys 1573389100521 Sync.Status DEBUG Status.login: error.sync.reason.serverMaintenance => success.status_ok 1573389100521 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1573389100522 Sync.Service DEBUG Fetching unlocked auth state returned success.status_ok 1573389100580 Services.Common.RESTRequest DEBUG GET request to https://api.accounts.firefox.com/v1/account/device/commands?index=1 1573389101382 Services.Common.RESTRequest DEBUG GET https://api.accounts.firefox.com/v1/account/device/commands?index=1 200 1573389101383 Hawk DEBUG (Response) /account/device/commands?index=1: code: 200 - Status text: OK 1573389101383 Hawk DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -383 1573389101386 Sync.Resource DEBUG GET fail 503 https://sync-581-us-west-2.sync.services.mozilla.com/1.5/91863943/info/collections 1573389101386 Sync.Resource WARN GET request to https://sync-581-us-west-2.sync.services.mozilla.com/1.5/91863943/info/collections failed with status 503 1573389101389 Sync.Status DEBUG Status.login: success.status_ok => error.login.reason.server 1573389101389 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1573389101389 Sync.ErrorHandler DEBUG Got Retry-After: 3600 1573389101389 Sync.Status DEBUG Status.login: error.login.reason.server => error.sync.reason.serverMaintenance 1573389101389 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1573389101390 Sync.SyncScheduler DEBUG Got backoff notification: 3600000ms 1573389101390 Sync.SyncScheduler DEBUG Fuzzed minimum next sync: 1573392701390 1573389101391 Sync.ErrorHandler ERROR Sync encountered a login error 1573389101391 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1573389101421 Sync.SyncScheduler DEBUG Next sync in 4369256.143576094 ms. (why=schedule) 1573389101424 Sync.Service DEBUG Exception calling WrappedLock: Error: Login failed: error.sync.reason.serverMaintenance(resource://services-sync/service.js:984:15) JS Stack trace: onNotify@service.js:984:15 1573389101426 Sync.Service DEBUG Not syncing: login returned false.

Gekozen oplossing

1573389101389 Sync.Status DEBUG Status.login: error.login.reason.server => error.sync.reason.serverMaintenance

We have been getting "serverMaintenance" error codes here since Friday and most (or all) are with this URL. https://sync-581-us-west-2.sync.services.mozilla.com/...

Dit antwoord in context lezen 👍 1

Alle antwoorden (1)

more options

Gekozen oplossing

1573389101389 Sync.Status DEBUG Status.login: error.login.reason.server => error.sync.reason.serverMaintenance

We have been getting "serverMaintenance" error codes here since Friday and most (or all) are with this URL. https://sync-581-us-west-2.sync.services.mozilla.com/...