ECONNREFUSED about chromeless

[victormejia]

@stevenvachon you need to have the chrome instance running

[DualWield]

I have run Chrome Canary locally,But still get this error.

{ Error: connect ECONNREFUSED 127.0.0.1:9222
    at Object.exports._errnoException (util.js:1024:11)
    at exports._exceptionWithHostPort (util.js:1047:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1150:14)
  code: 'ECONNREFUSED',
  errno: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 9222 }

[stevenvachon]

It is running.

Oh, I was just running regular Chrome. Can't this library start it headlessly for us? (#23)

[victormejia]

You will need Chrome Canary, and you can easily achieve this using an npm script of some sort. However, I do recommend adding in that alias that they specify in the README.

[schickling]

Future versions will automatically start Chrome locally. See #23 for more.

[happy-dev]

Same behavior here than @DualWield is facing.

[joelgriffith]

I've started to notice this as well... I'll investigate, got a feeling we're not passing through ports in all the right places

[happy-dev]

I found the solution here

Chrome actually needs to be running already, listening to the appropriate port, ie. 9222 here.