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

Firefox Sync not working with own server

  • 1 பதிலளி
  • 3 இந்த பிரச்னைகள் உள்ளது
  • 14 views
  • Last reply by guigs

I tired using my own firefox sync 1.5 server. The server is running and I see something in the logs, but these data looks ok: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): verifier.accounts.firefox.com INFO:mozsvc.metrics:{"tokenserver.backend.get_user": 0.0023899078369140625, "code": 200, "request_time": 0.7886579036712646, "remoteAddressChain": ["127.0.0.1"], "agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0", "tokenserver.assertion.verify": 0.7827959060668945, "token.assertion.verify_success": 1, "path": "http://sync.mydomain.de/token/1.0/sync/1.5", "method": "GET"} INFO:mozsvc.metrics:{"code": 200, "request_time": 0.0017180442810058594, "remoteAddressChain": ["127.0.0.1"], "agent": "Firefox/33.0a2 FxSync/1.35.0.20140806004002.desktop", "path": "http://sync.mydomain.de/storage/1.5/1/info/collections", "method": "GET"} INFO:mozsvc.metrics:{"tokenserver.backend.get_user": 0.001628875732421875, "code": 200, "request_time": 0.2062840461730957, "remoteAddressChain": ["127.0.0.1"], "agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0", "tokenserver.assertion.verify": 0.20348882675170898, "token.assertion.verify_success": 1, "path": "http://sync.mydomain.de/token/1.0/sync/1.5", "method": "GET"}


On about:sync-log I have this in my logfile: http://pastebin.com/avar0JB1

The user is created in my mysql database. On the next sync try, this is in my log: 1407393996302 Sync.ErrorHandler DEBUG Flushing file log. 1407393996303 Sync.Service DEBUG Exception: Login failed: error.login.reason.account No traceback available 1407393996303 Sync.Service DEBUG Not syncing: login returned false. 1407393996304 Sync.Status DEBUG Status.service: error.login.failed => success.status_ok 1407393996306 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996307 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996309 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996311 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996313 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996314 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996316 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996318 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996320 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996321 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996323 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996324 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996327 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996328 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996330 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996331 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996333 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996335 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996337 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996338 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996342 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996343 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996345 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996347 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996348 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996355 Sync.ErrorHandler DEBUG Log cleanup threshold time: 1406529996355 1407393996355 Sync.ErrorHandler DEBUG No logs to clean up. 1407394083475 Sync.Tracker.History DEBUG Saving changed IDs to history 1407394174283 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407394174285 Sync.ErrorHandler DEBUG Beginning user-triggered sync. 1407394174285 Sync.Service DEBUG User-Agent: Firefox/33.0a2 FxSync/1.35.0.20140806004002. 1407394174285 Sync.Service INFO Starting sync at 2014-08-07 08:49:34 1407394174285 Sync.Service DEBUG In sync: should login. 1407394174286 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407394174287 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407394174287 Sync.Service INFO Logging in the user. 1407394174287 Sync.Service DEBUG Caching URLs under storage user base: https://sync.myserver.de/storage/1.5/1/ 1407394174288 Sync.BrowserIDManager DEBUG _ensureValidToken already has one 1407394174341 Sync.Resource DEBUG mesg: GET fail 401 https://sync.myserver.de/storage/1.5/1/info/collections 1407394174342 Sync.Resource DEBUG GET fail 401 https://sync.myserver.de/storage/1.5/1/info/collections 1407394174342 Sync.Service WARN 401: login failed. 1407394174343 Sync.BrowserIDManager DEBUG _findCluster found existing clusterURL, so discarding the current token 1407394174343 Sync.BrowserIDManager INFO Fetching assertion and token from: https://sync.myserver.de/token/1.0/sync/1.5 1407394174343 FirefoxAccounts DEBUG already verified 1407394174343 Sync.BrowserIDManager DEBUG Getting an assertion 1407394174343 FirefoxAccounts DEBUG enter getAssertion() 1407394174343 FirefoxAccounts DEBUG getKeyPair: already have a keyPair 1407394174343 FirefoxAccounts DEBUG getCertificate already had one 1407394174343 FirefoxAccounts DEBUG getAssertionFromCert 1407394174345 FirefoxAccounts DEBUG getAssertionFromCert returning signed: true 1407394174345 Sync.BrowserIDManager DEBUG Getting a token 1407394175388 Sync.BrowserIDManager DEBUG Successfully got a sync token 1407394175388 Sync.BrowserIDManager DEBUG _findCluster returning https://sync.myserver.de/storage/1.5/1/ 1407394175389 Sync.Service DEBUG Cluster value = https://sync.myserver.de/storage/1.5/1/ 1407394175389 Sync.Status DEBUG Status.login: error.login.reason.account => error.login.reason.account 1407394175389 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed 1407394175389 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score.


The sync is stopping with the yellow infobar and the text: (something like) Invalid Username or password. But on the firefox accounts website i can login.

I tired using my own firefox sync 1.5 server. The server is running and I see something in the logs, but these data looks ok: INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): verifier.accounts.firefox.com INFO:mozsvc.metrics:{"tokenserver.backend.get_user": 0.0023899078369140625, "code": 200, "request_time": 0.7886579036712646, "remoteAddressChain": ["127.0.0.1"], "agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0", "tokenserver.assertion.verify": 0.7827959060668945, "token.assertion.verify_success": 1, "path": "http://sync.mydomain.de/token/1.0/sync/1.5", "method": "GET"} INFO:mozsvc.metrics:{"code": 200, "request_time": 0.0017180442810058594, "remoteAddressChain": ["127.0.0.1"], "agent": "Firefox/33.0a2 FxSync/1.35.0.20140806004002.desktop", "path": "http://sync.mydomain.de/storage/1.5/1/info/collections", "method": "GET"} INFO:mozsvc.metrics:{"tokenserver.backend.get_user": 0.001628875732421875, "code": 200, "request_time": 0.2062840461730957, "remoteAddressChain": ["127.0.0.1"], "agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0", "tokenserver.assertion.verify": 0.20348882675170898, "token.assertion.verify_success": 1, "path": "http://sync.mydomain.de/token/1.0/sync/1.5", "method": "GET"} On about:sync-log I have this in my logfile: http://pastebin.com/avar0JB1 The user is created in my mysql database. On the next sync try, this is in my log: 1407393996302 Sync.ErrorHandler DEBUG Flushing file log. 1407393996303 Sync.Service DEBUG Exception: Login failed: error.login.reason.account No traceback available 1407393996303 Sync.Service DEBUG Not syncing: login returned false. 1407393996304 Sync.Status DEBUG Status.service: error.login.failed => success.status_ok 1407393996306 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996307 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996309 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996311 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996313 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996314 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996316 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996318 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996320 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996321 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996323 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996324 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996327 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996328 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996330 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996331 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996333 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996335 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996337 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996338 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996342 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996343 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996345 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996347 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996348 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407393996355 Sync.ErrorHandler DEBUG Log cleanup threshold time: 1406529996355 1407393996355 Sync.ErrorHandler DEBUG No logs to clean up. 1407394083475 Sync.Tracker.History DEBUG Saving changed IDs to history 1407394174283 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407394174285 Sync.ErrorHandler DEBUG Beginning user-triggered sync. 1407394174285 Sync.Service DEBUG User-Agent: Firefox/33.0a2 FxSync/1.35.0.20140806004002. 1407394174285 Sync.Service INFO Starting sync at 2014-08-07 08:49:34 1407394174285 Sync.Service DEBUG In sync: should login. 1407394174286 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407394174287 Sync.Status DEBUG Status.service: success.status_ok => success.status_ok 1407394174287 Sync.Service INFO Logging in the user. 1407394174287 Sync.Service DEBUG Caching URLs under storage user base: https://sync.myserver.de/storage/1.5/1/ 1407394174288 Sync.BrowserIDManager DEBUG _ensureValidToken already has one 1407394174341 Sync.Resource DEBUG mesg: GET fail 401 https://sync.myserver.de/storage/1.5/1/info/collections 1407394174342 Sync.Resource DEBUG GET fail 401 https://sync.myserver.de/storage/1.5/1/info/collections 1407394174342 Sync.Service WARN 401: login failed. 1407394174343 Sync.BrowserIDManager DEBUG _findCluster found existing clusterURL, so discarding the current token 1407394174343 Sync.BrowserIDManager INFO Fetching assertion and token from: https://sync.myserver.de/token/1.0/sync/1.5 1407394174343 FirefoxAccounts DEBUG already verified 1407394174343 Sync.BrowserIDManager DEBUG Getting an assertion 1407394174343 FirefoxAccounts DEBUG enter getAssertion() 1407394174343 FirefoxAccounts DEBUG getKeyPair: already have a keyPair 1407394174343 FirefoxAccounts DEBUG getCertificate already had one 1407394174343 FirefoxAccounts DEBUG getAssertionFromCert 1407394174345 FirefoxAccounts DEBUG getAssertionFromCert returning signed: true 1407394174345 Sync.BrowserIDManager DEBUG Getting a token 1407394175388 Sync.BrowserIDManager DEBUG Successfully got a sync token 1407394175388 Sync.BrowserIDManager DEBUG _findCluster returning https://sync.myserver.de/storage/1.5/1/ 1407394175389 Sync.Service DEBUG Cluster value = https://sync.myserver.de/storage/1.5/1/ 1407394175389 Sync.Status DEBUG Status.login: error.login.reason.account => error.login.reason.account 1407394175389 Sync.Status DEBUG Status.service: success.status_ok => error.login.failed 1407394175389 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. The sync is stopping with the yellow infobar and the text: (something like) Invalid Username or password. But on the firefox accounts website i can login.

All Replies (1)

Why in the pastebin in the debugging line is the version of sync the older one:

1407393996002 Sync.Service DEBUG User-Agent: Firefox/33.0a2 FxSync/1.35.0.20140806004002.

More info on self hosting can be found here: https://blog.mozilla.org/services/201.../firefox-accounts-sync-1-5-and-self-hosting/ where you can also ask this in the #sync IRC channel or https://mail.mozilla.org/listinfo/sync-dev join the dev mailing list to get a more technical answer.

Are you using the first method? Where the Firefox server is the authenticating server and the hosted server is your own?

It fails to login because it flags it already has a token, but 401 failed to Get the collections at your server, these are strange errors and I am not an expert, please do ask your question in the mailing list, the technical eye will be able to catch the issue much quicker.