Am 11.02.2016 um 04:31 schrieb Ryan Kelly:
>> Having the servers up and running I am struggling with a new problem. I
>> am able to register a new account and log in to existing ones, but once
>> I am logged in, I am confronted by an "unexpected error" message, which
>> roughly translates to: "System not available, please try again later."
>> This is a bit strange since I can only see result code 200 / errno 0
>> messages in the server logs. Example from the auth-server log:
>>
>> {"Timestamp":1455113872527000000,"Logger":"fxa-auth-server","Type":"request.summary","Severity":6,"Pid":4624,"EnvVersion":"2.0","Fields":{"op":"request.summary","code":200,"errno":0,"rid":"1455113872522:ffsync2:4624:ikgwijce:10054","path":"/v1/session/status","lang":"de,en-US;q=0.7,en;q=0.3","agent":"Mozilla/5.0
>> (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101
>> Firefox/44.0","remoteAddressChain":"[\"192.168.1.50\",\"127.0.0.1\"]","t":5,"uid":"<myuserid>"}}
>>
>> Same goes for the auth-db-mysql and content-server, no error codes
>> there. So I wonder what is causing the error which can be observed in
>> the user interface. I also tried pairing it with a syncserver and tried
>> to synchronize, though being able to log in, synchronization is never
>> happening and I am asked to log in again after the first try. The
>> about:sync-log is giving me an unauthorized error:
>>
>> 1455112853599 Sync.BrowserIDManager ERROR Could not authenticate:
>> {"details":{"now":"2016-02-10T14:00:53.578Z","message":"Authentication
>> failed.","cause":"invalid-credentials","response_body":"{\"status\":
>> \"invalid-credentials\", \"errors\": [{\"location\": \"body\", \"name\":
>> \"\", \"description\":
>> \"Unauthorized\"}]}","response_headers":{"content-type":"application/json;
>> charset=UTF-8","date":"Wed, 10 Feb 2016 14:00:58
>> GMT","x-timestamp":"1455112858","content-length":"110","connection":"keep-alive"},"response_status":401,"name":"TokenServerClientServerError"}}
>
> This error is happening when the browser goes to authenticate itself to
> the sync "tokenserver". Are you also running your own syncserver stack
> as documented at [1]?
Hi Ryan,
I did set up my own syncserver stack as documented there. But reading
the docs again, I noticed I had missed an important detail: The
syncserver token URI config entry was renamed in Firefox 42, which I had
not reflected yet. After adding the appropriate about:config entry,
synchronization appears to be working! Thank you!
Still, the "unexpected error - system not available" problem persists
when I navigate to the account server's settings interface
(https://my.account.server/settings) while being logged in. Do you have
an idea what could be the cause of it?
Thanks!
Nikolaus
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
