This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Error 'error.login.reason.network' in about:sync-log

  • 2 àwọn èsì
  • 1 ní ìṣòro yìí
  • 4 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ galvane

galvane
galvane
more options

I have two Mac computers with OS Mojave 10.14.4. This problem also happened with OS Sierra in the past. Firefox is unable to Sync, and the error message I find in about:sync-log is:

1556770452859 Sync.LogManager DEBUG Flushing file log 1556770452860 FirefoxAccounts TRACE not checking freshness of profile as it remains recent 1556770452871 Sync.LogManager DEBUG Log cleanup threshold time: 1555906452871 1556770452875 Sync.LogManager DEBUG Done deleting files. 1556770483720 FirefoxAccounts INFO Consuming missed commands. 1556770483720 Sync.Service DEBUG User-Agent: Firefox/66.0.3 (Intel Mac OS X 10.14) FxSync/1.68.0.20190409155332.desktop 1556770483721 Sync.Service INFO Starting sync at 2019-05-02 13:14:43 in browser session 88Clh6jea-0A 1556770483721 Sync.Service DEBUG In sync: should login. 1556770483721 Sync.Service INFO User logged in successfully - verifying login. 1556770483723 Sync.BrowserIDManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys 1556770483723 Sync.Status DEBUG Status.login: error.login.reason.network => success.status_ok 1556770483724 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1556770483724 Sync.Service DEBUG Fetching unlocked auth state returned success.status_ok 1556770483725 Services.Common.RESTRequest TRACE local time, offset: 1556770483724, -878 1556770483726 Services.Common.RESTRequest DEBUG GET request to https://api.accounts.firefox.com/v1/account/device/commands?index=0 1556770483727 Services.Common.RESTRequest TRACE HTTP Header authorization: ***** (suppressed) 1556770483727 Services.Common.RESTRequest TRACE HTTP Header content-type: text/plain 1556770483727 Services.Common.RESTRequest TRACE HTTP Header accept-language: en-US, en 1556770483849 Sync.Resource DEBUG GET fail 401 https://sync-211-us-west-2.sync.services.mozilla.com/1.5/119663841/info/collections 1556770483849 Sync.Resource WARN GET request to https://sync-211-us-west-2.sync.services.mozilla.com/1.5/119663841/info/collections failed with status 401 1556770483849 Sync.Service WARN 401: login failed. 1556770483849 Sync.BrowserIDManager DEBUG _findCluster has a pre-existing clusterURL, so fetching a new token token 1556770483849 Sync.BrowserIDManager INFO Getting keys 1556770483850 Sync.BrowserIDManager INFO Getting an assertion from: https://token.services.mozilla.com/1.0/sync/1.5 1556770483850 FirefoxAccounts DEBUG enter getAssertion() 1556770483851 FirefoxAccounts DEBUG getKeypairAndCertificate: already have keyPair and certificate 1556770483851 FirefoxAccounts DEBUG getAssertionFromCert 1556770483851 FirefoxAccounts DEBUG getAssertionFromCert returning signed: true 1556770483851 Sync.BrowserIDManager DEBUG Getting a token 1556770483851 Services.Common.TokenServerClient DEBUG Beginning BID assertion exchange: https://token.services.mozilla.com/1.0/sync/1.5 1556770483852 Services.Common.RESTRequest DEBUG GET request to https://token.services.mozilla.com/1.0/sync/1.5 1556770483852 Services.Common.RESTRequest TRACE HTTP Header accept: application/json 1556770483852 Services.Common.RESTRequest TRACE HTTP Header authorization: ***** (suppressed) 1556770483852 Services.Common.RESTRequest TRACE HTTP Header x-client-state: ***** (suppressed) 1556770483859 Services.Common.RESTRequest TRACE onStartRequest: GET https://api.accounts.firefox.com/v1/account/device/commands?index=0 1556770483859 Services.Common.RESTRequest TRACE Channel for GET https://api.accounts.firefox.com/v1/account/device/commands?index=0 returned status code 0 1556770483859 Services.Common.RESTRequest DEBUG GET https://api.accounts.firefox.com/v1/account/device/commands?index=0 200 1556770483859 Hawk DEBUG (Response) /account/device/commands?index=0: code: 200 - Status text: OK 1556770483859 Services.Common.RESTResponse TRACE Processing response headers. 1556770483859 Hawk DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -859 1556770483859 FirefoxAccounts DEBUG _updateAccountData with items: ["device"] 1556770483860 FirefoxAccounts DEBUG writing plain storage: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1556770483860 FirefoxAccounts TRACE starting write of json user data: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1556770483862 FirefoxAccounts TRACE finished write of json user data - took: 2 1556770483862 FirefoxAccounts DEBUG writing secure storage: ["kSync","kXCS","kExtSync","kExtKbHash"] 1556770483862 FirefoxAccounts TRACE starting write of user data to the login manager 1556770483867 FirefoxAccounts TRACE finished write of user data to the login manager 1556770484247 Services.Common.RESTRequest TRACE onStartRequest: GET https://token.services.mozilla.com/1.0/sync/1.5 1556770484247 Services.Common.RESTRequest TRACE Channel for GET https://token.services.mozilla.com/1.0/sync/1.5 returned status code 0 1556770484247 Services.Common.RESTRequest DEBUG GET https://token.services.mozilla.com/1.0/sync/1.5 200 1556770484248 Services.Common.TokenServerClient DEBUG Got token response: 200 1556770484248 Services.Common.RESTResponse TRACE Processing response headers. 1556770484248 Services.Common.TokenServerClient DEBUG Successful token response 1556770484248 Sync.Status DEBUG Status.login: success.status_ok => success.login 1556770484248 Sync.Status DEBUG Status.service: error.login.failed => success.status_ok 1556770484248 Sync.BrowserIDManager DEBUG _findCluster returning https://sync-211-us-west-2.sync.services.mozilla.com/1.5/119663841/ 1556770484248 Sync.BrowserIDManager DEBUG Cluster value = https://sync-211-us-west-2.sync.services.mozilla.com/1.5/119663841/ 1556770484248 Sync.Status DEBUG Status.login: success.login => error.login.reason.network 1556770484248 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed 1556770484248 Sync.ErrorHandler ERROR Sync encountered a login error 1556770484249 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1556770484249 Sync.SyncScheduler DEBUG Next sync in 3600000 ms. (why=schedule) 1556770484251 Sync.Service DEBUG Exception calling WrappedLock: Error: Login failed: error.login.reason.network(resource://services-sync/service.js:872:15) JS Stack trace: onNotify@service.js:872:15 1556770484251 Sync.Service DEBUG Not syncing: login returned false. 1556770484252 FirefoxAccounts TRACE not checking freshness of profile as it remains recent

I have unsuccessfully tried: http://forums.mozillazine.org/viewtopic.php?f=38&t=3037171 https://github.com/mozilla-services/syncserver/issues/152 (read this, but did not understand how to implement the solution).

Also, reinstalling Firefox did not succeed.

I appreciate the help.

I have two Mac computers with OS Mojave 10.14.4. This problem also happened with OS Sierra in the past. Firefox is unable to Sync, and the error message I find in about:sync-log is: 1556770452859 Sync.LogManager DEBUG Flushing file log 1556770452860 FirefoxAccounts TRACE not checking freshness of profile as it remains recent 1556770452871 Sync.LogManager DEBUG Log cleanup threshold time: 1555906452871 1556770452875 Sync.LogManager DEBUG Done deleting files. 1556770483720 FirefoxAccounts INFO Consuming missed commands. 1556770483720 Sync.Service DEBUG User-Agent: Firefox/66.0.3 (Intel Mac OS X 10.14) FxSync/1.68.0.20190409155332.desktop 1556770483721 Sync.Service INFO Starting sync at 2019-05-02 13:14:43 in browser session 88Clh6jea-0A 1556770483721 Sync.Service DEBUG In sync: should login. 1556770483721 Sync.Service INFO User logged in successfully - verifying login. 1556770483723 Sync.BrowserIDManager DEBUG unlockAndVerifyAuthState already has (or can fetch) sync keys 1556770483723 Sync.Status DEBUG Status.login: error.login.reason.network => success.status_ok 1556770483724 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1556770483724 Sync.Service DEBUG Fetching unlocked auth state returned success.status_ok 1556770483725 Services.Common.RESTRequest TRACE local time, offset: 1556770483724, -878 1556770483726 Services.Common.RESTRequest DEBUG GET request to https://api.accounts.firefox.com/v1/account/device/commands?index=0 1556770483727 Services.Common.RESTRequest TRACE HTTP Header authorization: ***** (suppressed) 1556770483727 Services.Common.RESTRequest TRACE HTTP Header content-type: text/plain 1556770483727 Services.Common.RESTRequest TRACE HTTP Header accept-language: en-US, en 1556770483849 Sync.Resource DEBUG GET fail 401 https://sync-211-us-west-2.sync.services.mozilla.com/1.5/119663841/info/collections 1556770483849 Sync.Resource WARN GET request to https://sync-211-us-west-2.sync.services.mozilla.com/1.5/119663841/info/collections failed with status 401 1556770483849 Sync.Service WARN 401: login failed. 1556770483849 Sync.BrowserIDManager DEBUG _findCluster has a pre-existing clusterURL, so fetching a new token token 1556770483849 Sync.BrowserIDManager INFO Getting keys 1556770483850 Sync.BrowserIDManager INFO Getting an assertion from: https://token.services.mozilla.com/1.0/sync/1.5 1556770483850 FirefoxAccounts DEBUG enter getAssertion() 1556770483851 FirefoxAccounts DEBUG getKeypairAndCertificate: already have keyPair and certificate 1556770483851 FirefoxAccounts DEBUG getAssertionFromCert 1556770483851 FirefoxAccounts DEBUG getAssertionFromCert returning signed: true 1556770483851 Sync.BrowserIDManager DEBUG Getting a token 1556770483851 Services.Common.TokenServerClient DEBUG Beginning BID assertion exchange: https://token.services.mozilla.com/1.0/sync/1.5 1556770483852 Services.Common.RESTRequest DEBUG GET request to https://token.services.mozilla.com/1.0/sync/1.5 1556770483852 Services.Common.RESTRequest TRACE HTTP Header accept: application/json 1556770483852 Services.Common.RESTRequest TRACE HTTP Header authorization: ***** (suppressed) 1556770483852 Services.Common.RESTRequest TRACE HTTP Header x-client-state: ***** (suppressed) 1556770483859 Services.Common.RESTRequest TRACE onStartRequest: GET https://api.accounts.firefox.com/v1/account/device/commands?index=0 1556770483859 Services.Common.RESTRequest TRACE Channel for GET https://api.accounts.firefox.com/v1/account/device/commands?index=0 returned status code 0 1556770483859 Services.Common.RESTRequest DEBUG GET https://api.accounts.firefox.com/v1/account/device/commands?index=0 200 1556770483859 Hawk DEBUG (Response) /account/device/commands?index=0: code: 200 - Status text: OK 1556770483859 Services.Common.RESTResponse TRACE Processing response headers. 1556770483859 Hawk DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -859 1556770483859 FirefoxAccounts DEBUG _updateAccountData with items: ["device"] 1556770483860 FirefoxAccounts DEBUG writing plain storage: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1556770483860 FirefoxAccounts TRACE starting write of json user data: ["email","sessionToken","uid","verified","device","oauthTokens","profileCache"] 1556770483862 FirefoxAccounts TRACE finished write of json user data - took: 2 1556770483862 FirefoxAccounts DEBUG writing secure storage: ["kSync","kXCS","kExtSync","kExtKbHash"] 1556770483862 FirefoxAccounts TRACE starting write of user data to the login manager 1556770483867 FirefoxAccounts TRACE finished write of user data to the login manager 1556770484247 Services.Common.RESTRequest TRACE onStartRequest: GET https://token.services.mozilla.com/1.0/sync/1.5 1556770484247 Services.Common.RESTRequest TRACE Channel for GET https://token.services.mozilla.com/1.0/sync/1.5 returned status code 0 1556770484247 Services.Common.RESTRequest DEBUG GET https://token.services.mozilla.com/1.0/sync/1.5 200 1556770484248 Services.Common.TokenServerClient DEBUG Got token response: 200 1556770484248 Services.Common.RESTResponse TRACE Processing response headers. 1556770484248 Services.Common.TokenServerClient DEBUG Successful token response 1556770484248 Sync.Status DEBUG Status.login: success.status_ok => success.login 1556770484248 Sync.Status DEBUG Status.service: error.login.failed => success.status_ok 1556770484248 Sync.BrowserIDManager DEBUG _findCluster returning https://sync-211-us-west-2.sync.services.mozilla.com/1.5/119663841/ 1556770484248 Sync.BrowserIDManager DEBUG Cluster value = https://sync-211-us-west-2.sync.services.mozilla.com/1.5/119663841/ 1556770484248 Sync.Status DEBUG Status.login: success.login => error.login.reason.network 1556770484248 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed 1556770484248 Sync.ErrorHandler ERROR Sync encountered a login error 1556770484249 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. 1556770484249 Sync.SyncScheduler DEBUG Next sync in 3600000 ms. (why=schedule) 1556770484251 Sync.Service DEBUG Exception calling WrappedLock: Error: Login failed: error.login.reason.network(resource://services-sync/service.js:872:15) JS Stack trace: onNotify@service.js:872:15 1556770484251 Sync.Service DEBUG Not syncing: login returned false. 1556770484252 FirefoxAccounts TRACE not checking freshness of profile as it remains recent I have unsuccessfully tried: http://forums.mozillazine.org/viewtopic.php?f=38&t=3037171 https://github.com/mozilla-services/syncserver/issues/152 (read this, but did not understand how to implement the solution). Also, reinstalling Firefox did not succeed. I appreciate the help.

Ọ̀nà àbáyọ tí a yàn

Can you log in to the Sync account via this page?

In case of issues with Sync you can try this:

Disconnect from Sync and Reconnect to Sync again. You can disconnect from Sync by clicking the e-mail address in the "3-bar" Firefox menu button drop-down list or go to "Options/Preferences > Sync".

Delete the signedInUser.json file in the Firefox profile folder and delete the Weave folder (Sync was formerly named Weave) with Firefox closed.

Remove an existing chrome://FirefoxAccounts entry in the Firefox Password Manager.

If that isn't enough then delete the prefs.js files to reset all prefs and maybe also delete the compatibility.ini file to reinitialize the profile.

Delete and re-create the Firefox account or change the Sync password. Note that changing the Sync password will wipe all data stored on the Sync server.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:preferences page.

Ka ìdáhùn ni ìṣètò kíkà 👍 1

All Replies (2)

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

Ọ̀nà àbáyọ Tí a Yàn

Can you log in to the Sync account via this page?

In case of issues with Sync you can try this:

Disconnect from Sync and Reconnect to Sync again. You can disconnect from Sync by clicking the e-mail address in the "3-bar" Firefox menu button drop-down list or go to "Options/Preferences > Sync".

Delete the signedInUser.json file in the Firefox profile folder and delete the Weave folder (Sync was formerly named Weave) with Firefox closed.

Remove an existing chrome://FirefoxAccounts entry in the Firefox Password Manager.

If that isn't enough then delete the prefs.js files to reset all prefs and maybe also delete the compatibility.ini file to reinitialize the profile.

Delete and re-create the Firefox account or change the Sync password. Note that changing the Sync password will wipe all data stored on the Sync server.

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:preferences page.

galvane
galvane Ìbéèrè olóhun
more options

Deleting the account and creating it again got it done. Thank you.