Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Avatar for Username

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

Firefox Sync is not working

  • 2 svar
  • 1 har detta problem
  • 19 visningar
  • Senaste svar av cor-el

user2795551
user2795551
more options

Hello, Here is the log:

1595593736593 Sync.LogManager DEBUG Flushing file log 1595593736621 Sync.LogManager DEBUG Log cleanup threshold time: 1594729736621 1595593736644 Sync.LogManager DEBUG Done deleting files. 1595593737349 Services.Common.RESTRequest DEBUG GET https://profile.accounts.firefox.com/v1/profile 304 1595593738071 Services.Common.RESTRequest DEBUG GET https://api.accounts.firefox.com/v1/account/device/commands?index=0 200 1595593738072 Hawk DEBUG (Response) /account/device/commands?index=0: code: 200 - Status text: OK 1595593738073 Hawk DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -1073 1595593804251 FirefoxAccounts INFO Polling device commands. 1595593804251 Sync.Service DEBUG User-Agent: Firefox/78.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.80.0.20200708170202.desktop 1595593804252 Sync.Service INFO Starting sync at 2020-07-24 14:30:04 in browser session t3NmXHhu5AEj 1595593804252 Sync.Service DEBUG In sync: should login. 1595593804252 Sync.Service INFO User logged in successfully - verifying login. 1595593804254 FirefoxAccounts TRACE not checking freshness of profile as it remains recent 1595593804255 Sync.BrowserIDManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys 1595593804255 Sync.Status DEBUG Status.login: error.sync.reason.serverMaintenance => success.status_ok 1595593804255 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1595593804255 Sync.Service DEBUG Fetching unlocked auth state returned success.status_ok 1595593804256 FirefoxAccounts TRACE not checking freshness of profile as it remains recent 1595593804264 Services.Common.RESTRequest DEBUG GET request to https://api.accounts.firefox.com/v1/account/device/commands?index=0 1595593805688 Sync.Resource DEBUG GET fail 503 https://sync-607-us-west-2.sync.services.mozilla.com/1.5/93779942/info/collections 1595593805688 Sync.Resource WARN GET request to https://sync-607-us-west-2.sync.services.mozilla.com/1.5/93779942/info/collections failed with status 503 1595593805689 Sync.Status DEBUG Status.login: success.status_ok => error.login.reason.server 1595593805689 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1595593805689 Sync.ErrorHandler DEBUG Got Retry-After: 3600 1595593805689 Sync.Status DEBUG Status.login: error.login.reason.server => error.sync.reason.serverMaintenance 1595593805690 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1595593805690 Sync.SyncScheduler DEBUG Got backoff notification: 3600000ms 1595593805691 Sync.SyncScheduler DEBUG Fuzzed minimum next sync: 1595597405690 1595593805691 Sync.ErrorHandler ERROR Sync encountered a login error 1595593805692 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1595593805693 Sync.SyncScheduler DEBUG Next sync in 4304150.043309951 ms. (why=schedule) 1595593805696 Sync.Service DEBUG Exception calling WrappedLock: Error: Login failed: error.sync.reason.serverMaintenance(resource://services-sync/service.js:1043:15) JS Stack trace: onNotify@service.js:1043:15 1595593805697 Sync.Service DEBUG Not syncing: login returned false. 1595593805698 FirefoxAccounts TRACE not checking freshness of profile as it remains recent

Thank you

Hello, Here is the log: 1595593736593 Sync.LogManager DEBUG Flushing file log 1595593736621 Sync.LogManager DEBUG Log cleanup threshold time: 1594729736621 1595593736644 Sync.LogManager DEBUG Done deleting files. 1595593737349 Services.Common.RESTRequest DEBUG GET https://profile.accounts.firefox.com/v1/profile 304 1595593738071 Services.Common.RESTRequest DEBUG GET https://api.accounts.firefox.com/v1/account/device/commands?index=0 200 1595593738072 Hawk DEBUG (Response) /account/device/commands?index=0: code: 200 - Status text: OK 1595593738073 Hawk DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -1073 1595593804251 FirefoxAccounts INFO Polling device commands. 1595593804251 Sync.Service DEBUG User-Agent: Firefox/78.0.2 (Windows NT 10.0; Win64; x64) FxSync/1.80.0.20200708170202.desktop 1595593804252 Sync.Service INFO Starting sync at 2020-07-24 14:30:04 in browser session t3NmXHhu5AEj 1595593804252 Sync.Service DEBUG In sync: should login. 1595593804252 Sync.Service INFO User logged in successfully - verifying login. 1595593804254 FirefoxAccounts TRACE not checking freshness of profile as it remains recent 1595593804255 Sync.BrowserIDManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys 1595593804255 Sync.Status DEBUG Status.login: error.sync.reason.serverMaintenance => success.status_ok 1595593804255 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1595593804255 Sync.Service DEBUG Fetching unlocked auth state returned success.status_ok 1595593804256 FirefoxAccounts TRACE not checking freshness of profile as it remains recent 1595593804264 Services.Common.RESTRequest DEBUG GET request to https://api.accounts.firefox.com/v1/account/device/commands?index=0 1595593805688 Sync.Resource DEBUG GET fail 503 https://sync-607-us-west-2.sync.services.mozilla.com/1.5/93779942/info/collections 1595593805688 Sync.Resource WARN GET request to https://sync-607-us-west-2.sync.services.mozilla.com/1.5/93779942/info/collections failed with status 503 1595593805689 Sync.Status DEBUG Status.login: success.status_ok => error.login.reason.server 1595593805689 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1595593805689 Sync.ErrorHandler DEBUG Got Retry-After: 3600 1595593805689 Sync.Status DEBUG Status.login: error.login.reason.server => error.sync.reason.serverMaintenance 1595593805690 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1595593805690 Sync.SyncScheduler DEBUG Got backoff notification: 3600000ms 1595593805691 Sync.SyncScheduler DEBUG Fuzzed minimum next sync: 1595597405690 1595593805691 Sync.ErrorHandler ERROR Sync encountered a login error 1595593805692 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1595593805693 Sync.SyncScheduler DEBUG Next sync in 4304150.043309951 ms. (why=schedule) 1595593805696 Sync.Service DEBUG Exception calling WrappedLock: Error: Login failed: error.sync.reason.serverMaintenance(resource://services-sync/service.js:1043:15) JS Stack trace: onNotify@service.js:1043:15 1595593805697 Sync.Service DEBUG Not syncing: login returned false. 1595593805698 FirefoxAccounts TRACE not checking freshness of profile as it remains recent Thank you

Alla svar (2)

Huguette JEAN-FRANCOIS
Huguette JEAN-FRANCOIS
more options

Hi

I understand that Firefox Sync did not connect to your mobile device on this occasion, but hopefully I should be able to help you force a Sync event to take place.

Assuming you have connected the same Sync account on both your mobile and desktop copies of Firefox:

In Firefox on your mobile device:

  1. Go into the Settings menu and select Firefox Account.
  2. Tap on Synchronise now.

This will “force” a synchronisation of the data that is on the local device storage.

Regards

Huguette

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

I see this in the log: error.sync.reason.serverMaintenance

So you may have to retry at a later time when this maintenance is done.