I updated the email address after the timeout message, but that does not seem to help.
When i type in my server name (http://example.com:5000) on the account details screen, it reports an error "Please enter a valid server URL" Regardless, i can see the initial request in the console (which is running: sudo bin/paster server development.ini about:config services.sync.serverURL is still: https://auth.services.mozilla.com/ (Entering it directly just resets it as soon as the sync is tried) However, if i drop the http:// and simply use: example.com:5000 the setting updates itself to" example.com:5000/ (it adds the solidus) (using https:// doesn't show any connection on the server) FWIW, i'm not running the server under Apache (yet), just straight from the console. Changing services.sync.jpake.serverURL to: http://example.com:5000/jpake (or example.com:5000/jpake) acts differently. The initial connection is not seen, the server still times out (auth.services.mozilla.com), and hitting cancel on sync setup causes the jpake value to revert. changing the email address after the timeout results in "unknown error" about:sync-log shows no log created (recently) Using "example.com:5000" as opposed to "example.com:5000/jpake" does not seem to make a difference. Neither does 127.0.0.1 --- Changing services.sync.serverURL to: example.com/5000 (or http://example.com:5000) before opening the sync setup, when clicking the create a new account button, the setting immediately resets to: https://auth.services.mozilla.com/ (services.sync.jpake.serverURL remains as is) and the sync setup screen shows: "The address wasn't understood" error. Setting up the screen goes through the same timeout and shows "Unknown error" under the email field. Changing it to https://example.com/5000 shows: The proxy server is refusing connections (that may be the corporate firewall) All this makes no difference whether the jpake value was changed as well or not. And all this shows nothing on the server. Though, at this point, i am afraid i am missing something. Not changing any values (that is, cancelling sync setup which reverts the two values to their defaults) and doing a normal setup, no longer connects to the server. Restarting FF made no difference. What did i change? (Going to the site directly (not via sync) does get logged by the sync server.) --- I just asked a friend to connect, he installed a portable version of FF28 from home. (What are friends for, eh? :) ) He's getting similar errors. Except his is looking for /capcha. That is, instead of my: INFO [syncserver] xxx.xxx.xxx.xxx - - [...] "GET /user/1.0/a HTTP/1.1" 200 1 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0" xxx.xxx.xxx.xxx - - [...] "GET /user/1.0/a HTTP/1.1" 200 1 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0" For his connection it's: INFO [syncserver] xxx.xxx.xxx.xxx - - [...] "GET /misc/1.0/captcha_html HTTP/1.1" 404 175 "-" "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0" xxx.xxx.xxx.xxx - - [...] "GET /misc/1.0/captcha_html HTTP/1.1" 404 175 "-" "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0" He changed services.sync.serverURL and tried, same error as me, and the server doesn't log it. Canceling the setup (thus reverting the value) causes future attempts to not be logged by the server either. Restarting FF didn;t change that. No logging either. --- With all these settings and changes, am i missing something obvious? B. On Mon, Oct 19, 2015 at 1:19 AM, Ryan Kelly <[email protected]> wrote: > 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
