Error: Timeout (2000) waiting for 127.0.0.1:9229 to be free

[cristicmf]

Error: Timeout (2000) waiting for 127.0.0.1:9229 to be free
I have the same question

[jkrems]

Hey - thanks for the report! This should generally only happen if either a) you're using an older version of node-inspect or something else is genuinely blocking the port. The latter would happen if you'd try to start 2 CLI debuggers on the same machine.

Can you share an example script & command that was used to generate the error?

[Peripona]

there could also be the possibility, you are running node debug and try to run node inspect on another terminal.

[Michelle0609]

Hi ,I got the same issue. Does any one know how to fix that?
The script is very simple:
var person={
name:'Michelle'
};
person.age=25;
person.name='Mike';
console.log(person);

Command: node inspect app.js

[jkrems]

@Michelle0609 The most likely issue is that something else is running on port 9229. You can try running it on a different port using the following command:

node --inspect-port=9228 debug app.js

Alternatively you can try finding the thing blocking port 9229 on your machine. If neither of those options gets you anywhere, can you share the OS and version of node you're using?

[Michelle0609]

Hi Jan, Thanks for the email. I tried "node --inspect-port=9228 debug app.js" But got the following issue (node:12276) [DEP0068] DeprecationWarning: `node debug` is deprecated. Please use `node inspect` instead. There was an internal error in node-inspect. Please report this bug. Timeout (2000) waiting for 127.0.0.1:9228 to be free Error: Timeout (2000) waiting for 127.0.0.1:9228 to be free at Timeout.setTimeout [as _onTimeout] (node-inspect/lib/_inspect.js:63:14) at ontimeout (timers.js:478:11) at tryOnTimeout (timers.js:302:5) at Timer.listOnTimeout (timers.js:262:5) My OS is windows 10 and node version is 9.1.0 Thanks Michellle

…

On Wed, Nov 8, 2017 at 1:18 PM, Jan Olaf Krems ***@***.***> wrote: @Michelle0609 <https://github.com/michelle0609> The most likely issue is that something else is running on port 9229. You can try running it on a different port using the following command: node --inspect-port=9228 debug app.js Alternatively you can try finding the thing blocking port 9229 on your machine. If neither of those options gets you anywhere, can you share the OS and version of node you're using? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Afd7iRdk8Sq1EQtu1js6bQbYKJmxf8caks5s0Q-CgaJpZM4O7CL9> .

[jkrems]

Thanks for the details!

Wonder if there are any important error cases we're ignoring while trying. I don't have Windows around right now but I might be able to try debugging it when I'm back in the office tomorrow.

[Michelle0609]

Thanks Jan!

…

On Wed, Nov 8, 2017 at 1:59 PM, Jan Olaf Krems ***@***.***> wrote: Thanks for the details! Wonder if there are any important error cases we're ignoring while trying <https://github.com/nodejs/node-inspect/blob/49d7f88e3466d5b4b46886cb1f997b2dfc123d8b/lib/_inspect.js#L74>. I don't have Windows around right now but I might be able to try debugging it when I'm back in the office tomorrow. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Afd7ib6rifgpRGVsHnd5p_inSo0jmD1lks5s0RkJgaJpZM4O7CL9> .

[gosuto-inzasheru]

I encountered this error and found out while trying to close my Terminal window that there was another instance of node running in it still. Probably did not close it properly and that's why the port was blocked.

[shawncasaus]

To anyone making it to this thread with this issue, make sure you are exiting out of inspect using ctrl^c, not ctrl^z. If you use ctrl^z the debugger is still blocking the port and the only way to fix it is to exit and reenter terminal.

[blinking-in-the-light]

@Michelle0609 I got a good laugh from your example because it was identical enough to mine to know we were doing the same tutorial! Cheers.

[4rch1m3d35]

i'm having this issue as well and only have one terminal up still has same error
Node.js:12.2.0
OS: Windows 10
on VSC

$ node inspect app.js
Timeout (2000) waiting for 127.0.0.1:9229 to be free

[kerryja]

Hey @4rch1m3d35 did you figure this out? I am having the same problem!

[4rch1m3d35]

@kerryja nope nothing yet

[AleArmengol]

I'm having the same problem, did anyone figure this out? I already tried changing the port, but the error message is the same.
Timeout (2000) waiting for 127.0.0.1:9229 to be free
No matter what port I'm typing

[jkrems]

I'm having the same problem, did anyone figure this out? I already tried changing the port, but the error message is the same.

@AleArmengol To clarify your comment: Do you mean the message literally keeps talking about 9229 or just that you keep seeing timeouts for the various ports? If the port in the error stays the same, can you share the command you are using to set different ports?