🐛 BUG: Starting inspector on 0.0.0.0:9229 failed: address already in use
See original GitHub issueWhat version of Wrangler
are you using?
2.0.26
What operating system are you using?
Pop!_OS 22.04 LTS
Describe the Bug
run pnpm wrangler pages dev -- next dev
in next.js project folder.
trying to run with --inspector-port
and different port, same result.
checked with netstat
, port 9229 and any different ports that i tried not in use.
wrangler did working (serve proxy next dev
and /functions
).
other software version details: node 16.17.0 with nvm 0.39.1 pnpm 7.9.3
Issue Analytics
- State:
- Created a year ago
- Reactions:14
- Comments:16 (4 by maintainers)
Top Results From Across the Web
Starting inspector on 127.0.0.1:9229 failed: address already in ...
Run attach to process and show the error. Look up the occupied port with lsof command: lsof -i :9229 COMMAND PID USER FD...
Read more >Starting inspector failed: address already in use
This means the address is already in use by another Node.js app and you may have forgotten to exit it. Solution§.
Read more >VS Code: Starting inspector on 127.0.0.1:9229 failed
In the console I get "Starting inspector on 127.0.0.1:9229 failed: address already in use". I have not figured out what the problem is....
Read more >Unable to remotely debug Application: Address already in use
I get the following error in the terminal: /bin/node --inspect-brk=0.0.0.0:43535 ... Starting inspector on 0.0.0.0:43535 failed: address already in use.
Read more >Starting inspector on localhost:9200 failed - Glitch Help Center
Starting inspector on localhost:9200 failed: address not available. print icon. views icon 1467. Here are some tips to fix this error:.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
i’m still seeing this on
wrangler dev --local
on2.2.1
. no matter the port supplied either via--inspector-port
or theinspector_port
value in the wrangler.toml, the address is always considered in use when there is nothing running on the provided portstill seeing with wrangler 2.1.11 on macOS 12.6