On 14/04/2015 23:33, Robin Bankhead wrote:
> I am starting to find that I can no longer add desktop clients to my
> sync-1.1 server any more (I can pair them by installing an old FF
> version then upgrade through newer versions, but from FF32.0 they
> consistently stop syncing and try to register with FxA). I've therefore
> started trying to set up a self-hosted sync-1.5 stack.
>
> I have the syncserver (proxied behind Apache), fxa-auth-server and
> fxa-content-server components all running, and after some trial and
> error can get most of the way through registration using a desktop
> client with a fresh profile. However email verification never quite
> works -- the sync preferences tab shows the created account as
> unverified (the "Verify email" button does nothing), and although this
> changes after restarting the browser, sync still fails. The problem
> occurs with various calls to the fxa-auth-server returning status 401,
> error 109 (or 110 in some circumstances), example:
>
> 1429017392778 Sync.BrowserIDManager ERROR Background fetch for
> key bundle failed:
> {"details":{"code":401,"errno":109,"error":"Unauthorized","message":"Bad
> mac","info":"https://github.com/mozilla/fxa-auth-server/blob/master/docs/api.md#response-format","log":[]}}
The corresponding error code from here:
https://github.com/mozilla/fxa-auth-server/blob/master/docs/api.md#response-format
Is "109: invalid request signature". At a first guess, I suspect that
there's a mis-match between what the server and client consider the
canonical public URL of the server.
> fxa-auth-server/config/dev.json
>
> 3c3
> < "url": "http://127.0.0.1:3030";
> ---
>> "url": "https://fxa.example.com:3030";
> 4a5,11
>> "listen": {
>> "host": "192.168.2.7",
>> "port": "9900"
>> },
>> "useHttps": true,
>> "keyPath": "../server.key",
>> "certPath": "../server.crt",
> 7c14
> < "port": 9999,
> ---
>> "port": 25,
> 9c16,18
> < "sender": "[email protected]",
> ---
>> "sender": "[email protected]",
>> "user": "myusername",
>> "password": "mypassword",
>
Try setting the "publicUrl" key on this file, to tell the auth-server
what its public-facing URL is. This value should match the one you
configure in the content-server, which AFAICT from your examples should be:
"publicUrl": "https://fxa.example.com:9900";
Hope this helps,
Ryan
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
