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.

Chrome Debugger could not be reached

See original GitHub issue

chrome: 58 os: macOS 10.12.4

trace:

🏎  Speed Racer v0.1.2

 ❯ Starting
   ✖ Launching headless browser
     → Chrome Debugger could not be reached.
     Starting tracing server
   Tracing
   Reporting
Error: Chrome Debugger could not be reached.
    at isDebuggerReady.then.isReady (/usr/local/lib/node_modules/speedracer/lib/launch-chrome.js:74:27)
    at process._tickCallback (internal/process/next_tick.js:109:7)

Let me know if you need more info.

Issue Analytics

State:
Created 6 years ago
Comments:7

Top GitHub Comments

1reaction

ngrymancommented, May 26, 2017

@AutoSponge Did you add the --no-headless flag?

0reactions

AutoSpongecommented, May 25, 2017

I have version 0.2.0 of speedracer on mac osx with chrome Version 58.0.3029.110 (64-bit). Same error: Chrome Debugger could not be reached.

Top Results From Across the Web

VS Code debug in Chrome - This site can't be reached error

I am trying to debug a very simple html app with Chrome, but when I get to my localhost I get an error...

Debugging type chrome fails when using request: attach in a ...

When using "type": "chrome" and "request": "attach" , the debugger will fail to start almost immediately with the following message: Cannot ...

Cannot debug with chrome - Visual Studio Feedback

We suspect this is a known issue. Please try killing all prior Chrome processes before launching debug(F5) and see if this can fix...

Chrome Browser debug logs - Google Support

You can troubleshoot problems with Chrome Browser, such as hanging tabs and error messages. Use debug logs to help you. These logs aren't...

Source tab sometimes does not refresh when browser window ...

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group. To unsubscribe from this group and...