VSCode Chrome Debgugger Extension: Error: connect ECONNREFUSED 127.0.0.1:9222
<p>I am trying to leverage VSCode to debug a Meteor app. I have the following configuration in the .vscode/launch.json file:</p>

<p><code>{
   "name": "Attach Client",
   "type": "chrome",
   "request": "attach",
   "port": 9222,
   "address": "localhost",
   "sourceMaps": true,
   "diagnosticLogging": true,
   "webRoot": "${workspaceRoot}",
   "url": "http://localhost:3000/"
 }</code></p>

<p>Once the client side code is waiting for user action, I click on "Attach Client" and get the dreaded error in the title.</p>

<p>I have read the long and quite confusing too paragraphs concerning preventing this error in the readme page of the Chrome Debgugger Extension Github page, but:</p>

<ul>
<li>Most of it is undefined and unknown jargon to me so I am following the steps without understanding what they mean for the most part</li>
<li>Nothing seems to get rid of this error message</li>
</ul>

<p>a) I did execute in my mac terminal:</p>

<p><code>/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --rem
ote-debugging-port=9222</code></p>

<p>b) I did type <code>http://localhost:9222</code> on the chrome address bar and got localhost refused to connect, but I am not sure if this means that there something running at that port or not</p>

<p>c) I also did type <code>http://localhost:9222/json</code> and get the same, which according to the readme page means "something is wrong upstream of the extension" but it does not say what could be wrong and how to fix it.</p>

<p>My setup is:</p>

<ul>
<li>OS X El Capitan 10.11.6</li>
<li>VSCode 1.7.2 </li>
<li>VSCode Chrome Debugger extension 2.4.1</li>
<li>Google Chrome 55.0.2883.95</li>
</ul>

<p>Is there anyone out there who:</p>

<ul>
<li>Got around this error message and </li>
<li>Has experienced significant productivity gains by switching from debugging directly with plain Google Chrome Dev tools to debugging with the VSCode Chrome Debugger extension?</li>
</ul>