> As is the syncserver.ini:
>
> [app:main]
> use = egg:syncserver
>
> [syncserver]
> public_url = http://127.0.0.1:5000/
The "public_url" setting must be changed to match the external hostname
and port for the server, i.e. the hostname you would type into
about:config for your firefox client. Since you mention https below, I
guess the above value is not correct.
> Now I updated the services.sync.tokenServerURI accordingly, didn't
> forget to add a /token/1.0/sync/1.5 to the URl, which gave me following
> strange behaviour:
>
> Manually opening a tab with this exact url gives me the following string
> on the browser:
>
> {"status": "error", "errors": [{"location": "body", "name": "",
> "description": "Unauthorized"}]}
I agree it's not obvious, but this is the expected behaviour - you must
POST to that URL with a special Authorization header in order to get a
token.
Visiting the root of the server (i.e. without /token on it) should give
a nicer "it works!" style page.
> Could it be that the sync proccess can somehow ... have a problem with
> self signed SSL Certificates?
It does actually, but looks like you already worked around it by
visiting the site manually in the browser, and accepting the self-signed
certificate in the process.
> Or is there some way to get any debug
> messages from the syncing client?
Type "about:sync-log" into firefox and there should be some error logs
from the failed sync attempts.
The get logs from successful sync attempts, go to about:config and
search for "logOnSuccess".
> Thanks in advance, any response is appreciated, since my python mojo is
> close to non-existing and I'd like to know where I failed :)
AFAICT you've done pretty much everything right here, save for the
public_url issue. So I'm hopeful that will fix the problem.
Thanks for reaching out! Any suggestions for improving the docs or
process here are always appreciated.
Cheers,
Ryan
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
