Dear sync-developers,

Please forgive me if you have already received the emails I have sent. I
wasn't a member of the list and have the impression they have just
landed nowhere. If you haven't seen them, here is the newest and latest
version of my problem :)

First of all I'd like to thank you for this great product and for the
opportunity you are giving the community of being able to self-host the
sync server.

I am having some trouble setting up the whole thing and I hope you will
be able to shed some light on this.

The problem is I need to run the server(s) using SSL.

(Side-story: I tried to test it using the standard fxa-local-dev setup
but I was not able to, as FF would not allow me to sync to a non-https
server. I read in a couple of places that I should set enableHttp to
true. Unfortunately I could not find this option in any of the ff
versions I looked. I stopped looking for that as I need it to work with
ssl anyway).

In order to do this, I have configured the following servers so that
they'd use a self-signed certificate:
- fxa-content-server (https://127.0.0.1:3030)
- fxa-auth-server (9000)
- fxa-oauth-server (9010)

AFAIK these are the only ones with which ff directly speaks and the only
ones that really 'need' SSL.

Since I am using a self-signed certificate, I have also had to tell some
of the servers to accept non-validated certificates.

I have set up the servers one by one and have been executing one after
the other in order to troubleshoot all the errors I have been finding.

Up until now, the errors where more or less straight-forward and my
(very limited) nodejs knowledge - I saw nodejs last week for the first
time - was enough to solve them. Well, allegedly solve them. I might as
well just be doing everything worse :\

Running right now are the following servers:
- browserid-verifier (INSECURE_SSL=true nodejs server.js)
- fxa-profile-server (npm start)
- fxa-auth-server (npm start): this one actually starts other servers on
8000 9001 and 9999
- fxa-content-server (npm start)
- fxa-oauth-server (npm start)
- syncserver (make serve)

I have stumbled upon a problem I am just not able to solve.
I can create a new account and can 'verify' it using the verification
link that I found in the fxa-auth-server's log.

Right after doing this, ff tries to sync with the server to no avail. I
see the following errors in the logs:

fxa-auth-server.ERROR: request.summary
{"op":"request.summary","code":503,"errno":999,"rid":"1454945501756:debian-vm:22174:ike4rwk0:10014","path":"/v1/account/profile","remoteAddressChain":["127.0.0.1"],"t":268,"uid":"00","stack":"Error:
no nodes\n    at Object.exports.create
(/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/node_modules/boom/lib/index.js:21:17)\n
   at Object.exports.internal
(/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/node_modules/boom/lib/index.js:252:92)\n
   at Object.exports.serverTimeout
(/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/node_modules/boom/lib/index.js:276:20)\n
   at
/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/index.js:86:31\n
   at RequestSet.callback
(/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/node_modules/poolee/lib/pool.js:131:4)\n
   at RequestSet.handleResponse
(/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/node_modules/poolee/lib/request_set.js:66:8)\n
   at Endpoint.unhealthy.request
(/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/node_modules/poolee/lib/endpoint.js:359:12)\n
   at RequestSet.doRequest
(/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/node_modules/poolee/lib/request_set.js:89:7)\n
   at RequestSet.handleResponse
(/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/node_modules/poolee/lib/request_set.js:60:10)\n
   at Endpoint.complete
(/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/node_modules/poolee/lib/endpoint.js:157:11)\n
   at Endpoint.failed
(/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/node_modules/poolee/lib/endpoint.js:169:8)\n
   at ClientRequest.gotError
(/home/juanito/fxa-local-dev/fxa-auth-server/node_modules/hapi-fxa-oauth/node_modules/poolee/lib/endpoint.js:277:13)\n
   at emitOne (events.js:77:13)\n    at ClientRequest.emit
(events.js:169:7)\n    at Socket.socketOnEnd (_http_client.js:287:9)\n
  at emitNone (events.js:72:20)\n    at Socket.emit (events.js:166:7)\n
   at endReadableNT (_stream_readable.js:905:12)\n    at
nextTickCallbackWith2Args (node.js:441:9)\n    at
process._tickDomainCallback (node.js:396:17)"}

fxa-profile-server.routes.email.ERROR: request.auth_server.fail
{"code":503,"errno":999,"error":"Service Unavailable","message":"no
nodes","info":"https://github.com/mozilla/fxa-auth-server/blob/master/docs/api.md#response-format"}
fxa-profile-server.server.ERROR: summary
{"code":503,"method":"get","errno":105,"path":"/v1/email","agent":"Mozilla/5.0
(X11; Linux x86_64; rv:43.0) Gecko/20100101
Firefox/43.0","t":566,"stack":"Error: Auth server error\n    at new
authError
(/home/juanito/fxa-local-dev/fxa-profile-server/lib/error.js:142:10)\n
  at Request._callback
(/home/juanito/fxa-local-dev/fxa-profile-server/lib/routes/email.js:41:24)\n
   at Request.self.callback
(/home/juanito/fxa-local-dev/fxa-profile-server/node_modules/request/request.js:372:22)\n
   at emitTwo (events.js:87:13)\n    at Request.emit (events.js:172:7)\n
   at Request.<anonymous>
(/home/juanito/fxa-local-dev/fxa-profile-server/node_modules/request/request.js:1310:14)\n
   at emitOne (events.js:82:20)\n    at Request.emit (events.js:169:7)\n
   at IncomingMessage.<anonymous>
(/home/juanito/fxa-local-dev/fxa-profile-server/node_modules/request/request.js:1258:12)\n
   at emitNone (events.js:72:20)"}
fxa-profile-server.batch.ERROR: email.503
{"code":503,"errno":105,"error":"Service Unavailable","message":"Auth
server error","cause":"auth-server server erroroooooooooooooo"}
fxa-profile-server.server.ERROR: summary
{"code":503,"method":"get","errno":105,"path":"/v1/profile","agent":"Mozilla/5.0
(X11; Linux x86_64; rv:43.0) Gecko/20100101
Firefox/43.0","t":791,"stack":"Error: Auth server error\n    at
Function.from
(/home/juanito/fxa-local-dev/fxa-profile-server/lib/error.js:51:13)\n
 at /home/juanito/fxa-local-dev/fxa-profile-server/lib/batch.js:47:26\n
   at tryCatch1
(/home/juanito/fxa-local-dev/fxa-profile-server/node_modules/bluebird/js/main/util.js:45:21)\n
   at Promise$_callHandler [as _callHandler]
(/home/juanito/fxa-local-dev/fxa-profile-server/node_modules/bluebird/js/main/promise.js:660:13)\n
   at Promise$_settlePromiseFromHandler [as _settlePromiseFromHandler]
(/home/juanito/fxa-local-dev/fxa-profile-server/node_modules/bluebird/js/main/promise.js:675:18)\n
   at Promise$_settlePromiseAt [as _settlePromiseAt]
(/home/juanito/fxa-local-dev/fxa-profile-server/node_modules/bluebird/js/main/promise.js:845:14)\n
   at Promise$_settlePromises [as _settlePromises]
(/home/juanito/fxa-local-dev/fxa-profile-server/node_modules/bluebird/js/main/promise.js:988:14)\n
   at bound (domain.js:287:14)\n    at Promise.runBound
(domain.js:300:12)\n    at Async$_consumeFunctionBuffer [as
_consumeFunctionBuffer]
(/home/juanito/fxa-local-dev/fxa-profile-server/node_modules/bluebird/js/main/async.js:77:12)"}

And Firefox:
1454945502243   FirefoxAccounts ERROR   Could not retrieve profile data:
{"name":"FxAccountsProfileClientError","code":503,"errno":105,"error":"Service
Unavailable","message":"Auth server error"}
1454945502243   FirefoxAccounts ERROR   Could not retrieve profile data:
{"name":"FxAccountsProfileClientError","code":503,"errno":105,"error":"Service
Unavailable","message":"Auth server error"}
1454945502248   FirefoxAccounts ERROR   FxA rejecting with error AUTH_ERROR,
details:
{"name":"FxAccountsProfileClientError","code":503,"errno":105,"error":"Service
Unavailable","message":"Auth server error"}
1454945502248   FirefoxAccounts ERROR   FxA rejecting with error AUTH_ERROR,
details:
{"name":"FxAccountsProfileClientError","code":503,"errno":105,"error":"Service
Unavailable","message":"Auth server error"}


They seem to not be able to communicate correctly but I haven't been
able to figure out why. Do you have any idea why this is failing?

I believe I am following the right path, but please correct me if I'm wrong.

Again, I'd like to thank you for your time and efforts in building such
a cool tool!

If you find the time, some help would be really appreciated.

Cheers,
Juanito


_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev

Reply via email to