node --inspect in private network - debugger never opens

[gilly3]

• Version: v6.10.0
• Platform: Linux myhostname 3.13.0-86-generic lib: reintroduce v8 module #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

When I attempt to debug my script via --inspect, the dev tools never open.

$ node --debug-brk --inpect myscript.js

If I paste the URL from the console into Chrome (v55.0, running on Windows Server 2012 R2), nothing ever loads. If I go into the dev tools and view the remote devices, I can see my script right there:

Clicking the "inpect" button opens a window that remains blank (white), the dev tools never load.

I'm running in a private network without internet access. Is access to the web required to use the debugger?

As it is, I'm stuck using only the command line debugger, which is quite difficult.

[mscdex]

/cc @nodejs/v8-inspector

[eugeneo]

Note that this is not Node.JS issue as other frontends (like VS.Code) should work fine.

Node 6.10 requires a specific version of the Chrome DevTools and Chrome needs a network access to download it.
Newer Node.JS versions expose a stable protocol so Chrome can use a bundled DevTools frontend for debugging. There still might be some functionality that will require network access for the Chrome.

[bnoordhuis]

Question answered, closing.