Skip to content

Commit e54bfdb

Browse files
committed
docs: add troubleshooting.md
1 parent f030726 commit e54bfdb

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed

docs/troubleshooting.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# Troubleshooting
2+
3+
## General tips
4+
5+
- Run `npx chrome-devtools-mcp@latest --help` to test if the MCP server runs on your machine.
6+
- Make sure that your MCP client has the same npm and node versions.
7+
- When configuring your MCP client, try using the `--yes` argument to `npx` to
8+
auto-accept installation prompt.
9+
- Find a specific error in the output of the `chrome-devtools-mcp` server.
10+
Usually, if you client is an IDE, logs would be in the Output pane.
11+
12+
## Specific problems
13+
14+
### `Error [ERR_MODULE_NOT_FOUND]: Cannot find module ...`
15+
16+
This usually indicates either a non-supported Node version is in use or that the
17+
`npm`/`npx` cache is corrupted. Try clearing the cache, unsintalling
18+
`chrome-devtools-mcp` and installing it again.
19+
20+
### `Target closed` error
21+
22+
This indicates that the browser could not be started. Make sure that no Chrome
23+
instances are running or close them. Make sure you have the latest stable Chrome
24+
installed and that [your system is able to run Chrome].

0 commit comments

Comments
 (0)