On 12/02/2016 21:37, Juan Garcia wrote:
>>
>> This is fxa-auth-server trying to talk to fxa-oauth-server. Make sure
>> that you've configured the link between them properly. I think by
>> default it expects the oauth-server to be running on port 9010, but you
>> can change this by setting the following environment variable when
>> running the fxa-auth-server:
>>
>> OAUTH_URL=http://127.0.0.1:<WHATEVER-PORT>
>>
>> (You shouldn't need to use an https:// URL for this internal
>> communication, but you can)
>>
>
> Well, I actually had to serve the oauth over SSL because firefox would
> complain about not wanting to show any non-encrypted content in https so
> I did have to use https.
>
> This is actually a problem because it expects http. I am not really sure
> where I can change this (the other logs ff and fxa-profile remain the
> same as in my first email).
>
> fxa-auth-server.ERROR: request.summary
> {"op":"request.summary","code":500,"errno":999,"rid":"1455102565822:debian-vm:10171:ikgqhsp8:10000","path":"/v1/account/profile","remoteAddressChain":["127.0.0.1"],"t":13,"uid":"00","stack":"Error:
> Uncaught error: Protocol \"https:\" not supported. Expected \"http:\".\n
The underlying "Poolee" library here should be able to support http, so
I suspect a configuration problem. Can you share the contents of your
"oauth" configuration section in fxa-auth-server? If you've got e.g. an
explicit "insecure: true" in there or something, it could cause this
code to think it should be using http rather than https.
Cheers,
Ryan
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
