Hello,
I've gotten a self-hosted sync-1.5/fxa stack operational across
multiple desktop clients, but have hit a problem trying to add an
Android client (Fennec 37 on Galaxy SIII, Android Jelly Bean).
I've installed callahad's fxa-custom-server-addon and entered my
self-hosted auth-server and token-server URLs, which are then visible
on the signup and signin screens, but when attempting to sign in I get
the error: "unable to connect to network". This comes up after a
couple of seconds the first time, then instantly (cached?) thereafter.
There are no problems with the phone's connection when doing this,
verified on 3G and wifi. I also wiped all of fennec's cache and
stored data via the Android Application Manager but this did not help.
I am able to go through signin, culminating in a success message, by
navigating to https://my-content-server.dom/signin so the server-side
seems all well.
My servers are all proxied through Apache so the external URLs I gave
to the addon are like:
https://fxa.mydomain.dom/v1
https://ffsync.mydomain.dom/token/1.0/sync/1.5
Only other comment is that the servers all use a self-signed
certificate, but I have made the appropriate exceptions in Fennec
before attempting the signin.
I will return with some adb logging once I have that worked out, but
in the meantime if anyone can suggest where the issue might lie from
any of the above, I'd be grateful.
Thanks,
Robin Bankhead
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
