Skip to content

docs: add error quick-reference table to troubleshooting skill #1103

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
natorion wants to merge 2 commits into from
Closed

docs: add error quick-reference table to troubleshooting skill #1103

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4c893d2
fix: add error quick-reference table to troubleshooting skill
natorion Mar 4, 2026
bbbcfd9
Merge branch 'main' into fix/troubleshooting-skill-quick-ref
natorion Mar 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions skills/troubleshooting/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,19 @@ If you cannot find any of these files, only then should you ask the user to prov

Before reading documentation or suggesting configuration changes, check if the error message matches one of the following common patterns.

#### Quick Reference

| Error / Symptom | Likely Cause | First Action |
|---|---|---|
| `Could not find DevToolsActivePort` | `--autoConnect`: Chrome not running or remote debugging not enabled | Ask user to open `chrome://inspect/#remote-debugging` and enable it |
| `Target closed` | Browser could not start; another Chrome instance may be running | Close other Chrome instances, verify Chrome is installed |
| `ProtocolError: Network.enable timed out` / `socket connection was closed unexpectedly` | `--autoConnect` handshake failure | Verify Chrome 144+ is running, remote debugging is enabled, and no other tool occupies the debug port |
| `Error [ERR_MODULE_NOT_FOUND]: Cannot find module` | Corrupted npm/npx cache or unsupported Node version | Clear cache: `rm -rf ~/.npm/_npx && npm cache clean --force` |
| "Tool not found" | Server started with `--slim` flag | Remove `--slim` from config to enable all tools |
| Server starts but creates a new empty profile | Typo in flags (e.g., `--autoBronnect`) | Check config for flag typos |
| Sandbox / permission errors on macOS | MCP client Seatbelt sandbox blocks Chrome | Disable sandbox for `chrome-devtools-mcp` or use `--browser-url` with manually launched Chrome |
| Connection fails from VM to host | Chrome rejects connection due to Host header validation | Create SSH tunnel: `ssh -N -L 127.0.0.1:9222:127.0.0.1:9222 user@host` |

#### Error: `Could not find DevToolsActivePort`

This error is highly specific to the `--autoConnect` feature. It means the MCP server cannot find the file created by a running, debuggable Chrome instance. This is not a generic connection failure.
Expand Down
Loading