Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

new error after update

See original GitHub issue

Component	Version
Operating system	Linux workstation 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Node.js	8.7
Chrome/Chromium/…	Google Chrome 62.0.3202.62 unknown
chrome-remote-interface	0.25.2

Is Chrome running in a container? YES / NO

Ciao!

How are you? I just updated I get this error, is there a change?

2017-10-20 23:05:10 unhandledRejection Error: unexpected server response (404)
    at ClientRequest._req.on (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-server/node_modules/ws/lib/WebSocket.js:656:26)
    at emitOne (events.js:115:13)
    at ClientRequest.emit (events.js:210:7)
    at HTTPParser.parserOnIncomingClient (_http_client.js:549:21)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:116:23)
    at Socket.socketOnData (_http_client.js:438:20)
    at emitOne (events.js:115:13)
    at Socket.emit (events.js:210:7)
    at addChunk (_stream_readable.js:264:12)
    at readableAddChunk (_stream_readable.js:251:11)
    at Socket.Readable.push (_stream_readable.js:209:10)
    at TCP.onread (net.js:587:20)

Issue Analytics

State:
Created 6 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

cyrus-andcommented, Oct 20, 2017

Are you using the browser target ws://127.0.0.1:9222/devtools/browser URL explicitly in your code? If that’s the case, you should use the one printed on stderr since Chrome 62. You can fetch it programmatically from CDP.Version(), see an example here.

Otherwise please try to provide a minimal example that reproduces this issue.

0reactions

p3x-robotcommented, Oct 21, 2017

ahh, thanks!