installed but not working..

[Zibri]

When I go on chrome://inspect

in node I see this error: ERR! devtools-backend:Proxy Internal request failed http://192.168.42.11:9222/json/version Error: connect EMFILE 192.168.42.11:9222 - Local (undefined:undefined)

(same for localhost) and if a manually go to http://192.168.42.11:9222/json/version

I see: EMFILE 192.168.42.11:9222 - Local (undefined:undefined)

[Zibri]

and also ERR! devtools-backend:Proxy Internal request failed http://192.168.42.11:9222/json/version Error: socket hang up ERR! devtools-backend:Proxy Internal request failed http://192.168.42.11:9222/json/version Error: connect EMFILE 192.168.42.11:9222 - Local (undefined:undefined)

[christian-bromann]

Can you describe more what your setup is?

[Zibri]

Ubuntu 17.10 I just did what's written in the readme... but it does not work and I don't know why. I badly need this to remote debug a smart tv application..

[Zibri]

$ node -v v8.11.3 $ uname -a Linux zibrixnb 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:23:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.10 DISTRIB_CODENAME=artful DISTRIB_DESCRIPTION="Ubuntu 17.10"

[Zibri]

if you need anything else to debug.. just ask

[christian-bromann]

Can you provide any logs from the proxy? Also check out my talk on this project.

[Zibri]

I explain... I wish to do what I usually do with "weinre" but using chrome devtools. With weinre, I just add a

If I undesrtood, devtools-backend should do the same... but I can't get it to work on Ubuntu 17.10

Could you tell me a step by step so I check what I do wrong or what is wrong in my system?

[ZhangKejun]

When I go on chrome://inspect

in node I see this error: ERR! devtools-backend:Proxy Internal request failed http://192.168.42.11:9222/json/version Error: connect EMFILE 192.168.42.11:9222 - Local (undefined:undefined)

(same for localhost) and if a manually go to http://192.168.42.11:9222/json/version

I see: EMFILE 192.168.42.11:9222 - Local (undefined:undefined)

Have you solved the problem? Can you share the solution?

[leMaik]

For future users (including myself): The issue is that the server leaks sockets, EMFILE is caused by too many files being opened. The solution is to add a handler for every path (*) that just does req.status(404).end() after registering the other paths in lib/index.js. This resolves the issue and makes the server work.