On 17/10/2015 04:33, Nicholas Alexander wrote:
> On Fri, Oct 16, 2015 at 10:26 AM, B. Tkatch <[email protected]
> <mailto:[email protected]>> wrote:
>
> It is. Ryan was kind enough to fix the issue, but the saga
> continues. :) And that was prolly me in irc.
>
> Of course, after he fixed this, i made my own really stupid mistake
> that he was kind about. (Referring to non-existent directories tends
> to not work.)
>
> Anyway, i finally saw a handshake, but sync setup (in ff) times out
> waiting for auth.services.mozilla.com
> <http://auth.services.mozilla.com> So, methinks not everything is
> perfect yet.
>
>
> Right. It's my understanding that this no longer exists, and it was the
> endpoint that provided the JPAKE pairing "Easy Setup" I linked above.
> You'll have to either manually add users to your DB, and configure them;
> or run the "Easy Setup" service yourself; or find such a service
> (perhaps OwnCloud is hosting such an instance).
The JPAKE server was "setup.services.mozilla.com" and is only necessary
when you go to add a second device. I recently added it to the
self-hosting setup along with a brief note, because it did indeed stop
working when the mozilla-hosted one went away [1]
The URL "auth.services.mozilla.com" is the old user-registration API and
it's definitely covered by the self-hosted setup. I suspect this may
just be an artifact of the Firefox client behaviour, e.g.
* You enter your email address, Firefox tries to contact the default
services at auth.services.mozilla.com to see if it's registered
* This request doesn't get a response because the server has gone away
* You change the URL to point to the self-hosted setup
* Firefox times out the initial request and displays an error.
You *may* be able to unstick this by waiting for the timeout error, then
going back to the "email address" field and re-entering your email.
This triggers Firefox to try the lookup again using the custom server
URL you've entered.
It's a gross back, but please try it and let us know whether it works
for you.
Unfortunately there's no chance of doing on work in the Firefox client
code to make this flow smoother, but perhaps we can have those servers
return an error response immediately instead of just timing out. I
filed a bug to investigate:
https://bugzilla.mozilla.org/show_bug.cgi?id=1216024
Cheers,
Ryan
[1]
https://docs.services.mozilla.com/howtos/run-sync.html#configuring-firefox
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
