Repository navigation
node --inspect: dev tools console not working #7891
Description
Activity
- addedinspectorIssues and PRs related to the V8 inspector protocol.Issues and PRs related to the V8 inspector protocol.
on Jul 27, 2016 /cc @ofrobots
I am following the steps, and the console in the inspector works - I can even do
console.log('a')and that (a) shows up in the cli running the node process (which is outputting a random number on interval).
I have node v6.3.1 and OS X 10.11.3Reacted by Matt@zloylos, are other things like debugger and profiler working ?
@zloylos just curious, what do you have in
/etc/hosts?I'm having the same issue.
- Version: 6.3.1
- Chrome: 54.0.2816.0 dev (64-bit)
- Platform: Ubuntu 16.04
Inspecting the inspector with devtools shows a number of errors such as:

Changing localhost to 127.0.0.1 makes no difference.
This appears to affect more than just the console, for instance, when I hit
f11to step into a function, the window goes fullscreen.Error re Console.enable is expected (it will go away once #7988 lands).
I'm looking into other failures.
EDIT:ofrobots:fix link.
This should be fixed now.
Fixed by #7988.
I'm still having the original issue on the following:
- Version: 6.5.0
- Chrome: 54.0.2840.16 beta (64-bit)
- Platform: Ubuntu 16.04
+1
Still seeing this issue in Node v7.0.0 and Chrome 54.0.2840.71 (64-bit). At this point it seems more likely to be an issue with the Chrome Dev Tools but I wasn't able to find a similar bug over there.
+1
Tested on node
latestas well asv6.9.1 ( Chrome 54.0.2840.71 m )I'm found that all works fine when I change debug URL query param from
ws=localhost:9229/node to ws=127.0.0.1:9229/node@zloylos answer worked for me but for that, I also need to open the link in Incognito Mode.
Is it possible to change the web socket host from
localhostto127.0.0.1through my node command?Hi @ofrobots @claudiorodriguez ,
I made a small video to show the similar problem that I have been facing.
Also seeing this on Node 6.9.1 on Chrome 54.0.2840.87 m (64-bit). However, my node is being run from WSL (Windows Subsystem for Linux). I've not yet tested on node installed directly on windows. However, following @zloylos also seemed to resolve the issue for me.

node --inspect;I have suggest for input, but I can't execute code.