Failed to connect to Standalone V8 VM, connection refused

[GoogleCodeExporter]

SDK/Debugger version: chromium javascript remote debugger 0.3.6.2012070
Eclipse version: Version: Indigo Service Release 2, Build id: 20120216-1857
Google Chrome/V8 Embedder + version: Node.JS v0.6.18
[For WebKit (WIP) protocol] Backend version:
OS + version: Mac OSX 10.8

What steps will reproduce the problem?
1. run node.js application in a remote server in debug mode
2. configure the Eclipse debugger to connect to the remote instance with remote 
hostname and port
3. keep getting "Failed to connect to Standalone V8 VM, connection refused" 
error. Debugger and remote host are on the same network and there is no 
firewall in between.
4. if I run the same Node.JS application on the local box, debugger can connect 
to local Node instance without any issues

What is the expected result?
Debugger should work for the remote instance the same way as local instance.

What happens instead?
Getting debugger failure saying connection refused.

Please provide any additional information below. If possible, attach a
(reduced) test-case.

Original issue reported on code.google.com by guozheng...@gmail.com on 11 Aug 2012 at 2:03

[GoogleCodeExporter]

At the first glance,  if connection is refused there's nothing can be done with 
it on our side. Probably V8 debugger agent in Node.JS only accepts local 
connections (for security reasons).
In this case there are 2 options:
- patch V8 in Node.JS
- provide a simple TCP proxy at Node's host (needs exactly one TCP connection 
per debug session).

Original comment by peter.ry...@gmail.com on 11 Aug 2012 at 5:56

[GoogleCodeExporter]

Thanks for the suggestions. I actually tried to set up SSH local port 
forwarding to the remote node server and it gave the same error message. Let me 
try again and get back to you.

Original comment by guozheng...@gmail.com on 13 Aug 2012 at 5:41

[GoogleCodeExporter]

Original comment by peter.ry...@gmail.com on 4 Oct 2012 at 8:35

• Changed state: WontFix