On 17/07/2014 6:01 AM, Ben Curtis wrote:
> Hi all,
>
> This is my first time setting up FxA and a sync server, and I've worked
> through most problems except getting the server to work with a client.
> My setup this far:
>
> fxa-auth-server running:
> - Port 9000 w/ internal SSL locally, NATed from port 13900 publicly
> - Port 3030 locally, NATed from port 13303 reverse-proxied from apache
> w/ SSL, and NATed publicly
>
> fxa-content-server running:
> - Port 13433 via Apache WSGI and NATed publicly at 13443 as well
>
> Firefox client about:config:
> - identity.fxaccounts.auth.uri;https://HOST.DOMAIN.com:13900/v1
> -
> identity.fxaccounts.remote.force_auth.uri;https://HOST.DOMAIN.com:13303/force_auth?service=sync&context=fx_desktop_v1
>
> -
> identity.fxaccounts.remote.signin.uri;https://HOST.DOMAIN.com:13303/signin?service=sync&context=fx_desktop_v1
>
> -
> identity.fxaccounts.remote.signup.uri;https://HOST.DOMAIN.com:13303/signup?service=sync&context=fx_desktop_v1
>
> - identity.fxaccounts.settings.uri;https://HOST.DOMAIN.com:13303/settings
> -
> services.sync.fxa.privacyURL;https://HOST.DOMAIN.com:13303/legal/privacy
> - services.sync.fxa.termsURL;https://HOST.DOMAIN.com:13303/legal/terms
One thing to check is the various url-related settings in the auth and
content servers. They must know what their own public URLs are, as well
as how to talk to each via public URLs.
For example, the auth-server has "publicUrl" and "contentServer.url"
settings.
You can also try using the Firefox developer tools to inspect the
network traffic when interacting with the content-server, you may find
more information in the raw error responses than gets presented in the UI.
Cheers,
Ryan
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
