Hi, I have exactly the same issue. I first reported it in GitHub (see https://github.com/mozilla-services/syncserver/issues/37), and then realize that I would have more help from the ML :)
As I reported in GitHub, my setup is working using HTTP, but not with HTTPS. I've double checked that the public_url has been set correctly. Here is the sync-log: 1408892150337 FirefoxAccounts DEBUG (Response) /account/keys: code: 200 - Status text: OK 1408892150338 FirefoxAccounts DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -338 1408892150339 FirefoxAccounts DEBUG Keys Obtained: kA=true, kB=true 1408892150343 FirefoxAccounts DEBUG Notifying observers of fxaccounts:onverified 1408892150346 Sync.BrowserIDManager DEBUG Getting an assertion 1408892150346 FirefoxAccounts DEBUG enter getAssertion() 1408892150367 FirefoxAccounts DEBUG got keyPair 1408892150382 FirefoxAccounts DEBUG getCertificateSigned: true true 1408892150614 FirefoxAccounts DEBUG (Response) /certificate/sign: code: 200 - Status text: OK 1408892150615 FirefoxAccounts DEBUG Clock offset vs https://api.accounts.firefox.com/v1: -615 1408892150615 FirefoxAccounts DEBUG getCertificate got a new one: true 1408892150616 FirefoxAccounts DEBUG getAssertionFromCert 1408892150617 FirefoxAccounts DEBUG getAssertionFromCert returning signed: true 1408892150618 Sync.BrowserIDManager DEBUG Getting a token 1408892151555 Sync.BrowserIDManager ERROR Authentication error in _fetchTokenForUser: AuthenticationError(TokenServerClientServerError({"now":"2014-08-24T14:55:51.555Z","message":"Authentication failed.","cause":"invalid-credentials","response_body":"{\"status\": \"invalid-credentials\", \"errors\": [{\"location\": \"body\", \"name\": \"\", \"description\": \"Unauthorized\"}]}","response_headers":{"server":"nginx","date":"Sun, 24 Aug 2014 14:55:51 GMT","content-type":"application/json; charset=UTF-8","content-length":"110","connection":"keep-alive","x-weave-timestamp":"1408892151.55","x-timestamp":"1408892151"},"response_status":401})) 1408892151556 Sync.Status DEBUG Status.login: error.login.reason.account => error.login.reason.account 1408892151556 Sync.Status DEBUG Status.service: error.login.failed => error.login.failed 1408892151556 Sync.SyncScheduler DEBUG Clearing sync triggers and the global score. Is it a configuration problem within nginx? Configuration seems the same from my point of view, but we never know… I am using an SSL certificate signed with my own CA, that I imported first into Firefox store. I tried a lot of things, but I have no clue what can go wrong when switching to HTTPS… Thanks a lot for keeping SyncServer self-hosted! Adrien _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
