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?

[4rch1m3d35]

this is the command to change ports
node --inspect=127.0.0.1:9230

[jkrems]

To clarify, the command to start the CLI debugger on a custom port is node inspect --port=9230 path/to/script.js.

When using node --inspect, the error above shouldn't appear since that's the program being debugged, it's not starting the CLI debugger (node-inspect).

[victorgutemberg]

same issue here.

Node v10.13.0
Windows 10

Tried running in VSC and then another attempt in PowerShell.
Tried changing the ports and for all of then, the same error message appears.

Timeout (2000) waiting for 127.0.0.1:12903 to be free
Timeout (2000) waiting for 127.0.0.1:25612 to be free
Timeout (2000) waiting for 127.0.0.1:5122 to be free

[jkrems]

@victorgutemberg When you say "tried running in VSC", do you mean its integrated terminal? Also, can you share the exact command you ran?

[jkrems]

I wonder if this is something specific to Windows since so far that seems to be a common thread. I don't have a Windows machine anymore to test that on, so if somebody could do some debugging, it would be much appreciated. :)

[AleArmengol]

I ran this commands
node inspect --port=9229 app.js
Timeout (2000) waiting for 127.0.0.1:9229 to be free

node inspect --port=9230 app.js
Timeout (2000) waiting for 127.0.0.1:9230 to be free

[victorgutemberg]

@jkrems yeah, I meant the integrated terminal. I've tried using the default cdm and PowerShell, same result on both.

And the command that I was running is the same as just mentioned by @AleArmengol.

[pjgorman]

same problem (node v 12.3.1) on Windows 10 Pro, Build 18362:
node inspect myScript.js gets "Timeout (2000) waiting for 127.0.0.1:9229 to be free".
Reproduced on various ports (9228, 9227)
Also, not specific to the VSC terminal. Reproduced in windows cmd and in powershell

Seems to work fine on the Windows 7 machine

[juergba]

Same problem on Windows 10 Home, Node v12.2.0,
happens with different ports.

[hessproject]

I am also having this issue on different ports in Windows 10, both in VSC integrated terminal and regular powershell

[boba1987]

Had the same issue, the problem was that I was starting multiple instances of node app inside a docker container, so the first instance that starts occupies 127.0.0.1:9229 and other instances cannot get to the port, thus trowing the error. After I set docker to start a single node app instance, error was gone

[4rch1m3d35]

unfortunately i am not using docker and i am only starting one instance of the integrated terminal

[linqFR]

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

Windows x64 18362.207
Node 12.6.0 AND 10.16

and i have checked used ip:port (netstat command) and no entry is using this port

[vikingdv]

@yilmazdurmaz
Thanks! I opened node.exe in a hex editor and changed delay in portIsFree from 2000 to 3000. That was enough. Your comment was very helpful.
Windows 10 x64
Node 10.16

[95rajasekar]

Anyone knows whats the difference between node inspect app.js & node --inspect app.js
I was trying the first one and was facing the same Timeout issue. When i tried the latter it worked fine.

[jkrems]

Anyone knows whats the difference between node inspect app.js & node --inspect app.js

Yeah, those two commands look more similar than they should. The difference is:

• node --inspect: Run app.js but expose the remote debugging interface that things like vscode, Chrome devtools, Intellij, etc. can attach to. Otherwise app.js will run just like always and have full control over the terminal.
• node inspect: Start the interactive CLI debugger that's bundled with node. It's an alternative for visual debuggers like vscode or Chrome devtools. The CLI debugger will then use node --inspect to start the script in a separate process and attaches to it.

The relationship between the two is more obvious in the more explicit flow that also supports remote debugging across machines:

# Start app.js with the inspect interface exposed, by default on port 9229:
node --inspect app.js
# In a separate terminal, start the inspect client against port 9229:
node inspect -p 9229

Now the CLI debugger (node inspect) is connected to the node process with the debug interface enabled (node --inspect). Hope that helps. :)

[95rajasekar]

Anyone knows whats the difference between node inspect app.js & node --inspect app.js

Yeah, those two commands look more similar than they should. The difference is:

• node --inspect: Run app.js but expose the remote debugging interface that things like vscode, Chrome devtools, Intellij, etc. can attach to. Otherwise app.js will run just like always and have full control over the terminal.
• node inspect: Start the interactive CLI debugger that's bundled with node. It's an alternative for visual debuggers like vscode or Chrome devtools. The CLI debugger will then use node --inspect to start the script in a separate process and attaches to it.

The relationship between the two is more obvious in the more explicit flow that also supports remote debugging across machines:

# Start app.js with the inspect interface exposed, by default on port 9229:
node --inspect app.js
# In a separate terminal, start the inspect client against port 9229:
node inspect -p 9229

Now the CLI debugger (node inspect) is connected to the node process with the debug interface enabled (node --inspect). Hope that helps. :)

Thanks! got the diff b/w the two 👍

[Haisum92]

guys this works. just type node --inspect-brk "your filename.js" for eg: mine is app.js so
node --inspect-brk app.js @ @ @ @yilmazdurmaz @kerryja

node: ../deps/uv/src/unix/core.c:117: uv_close: Assertion `!(((handle)->flags & (UV_CLOSING | UV_CLOSED)) != 0)' failed.
Aborted (core dumped)

[yilmazdurmaz]

@jkrems is there a way you may put a summary at the end and then put this discussion on a hold? it is too long that people miss the important parts we talked about.

[Prottoy2938]

I have tried --inspect-brk app.js, it works,
But I can't debug in crome when using this method. I press the play button in crome inspect, and nothing happens in the even I had typed debugger in my code.

And after typing --inspect-brk app.js the timeout error is happening again. So have anyone solved this issue? How do I get out of this timeout error?

[teriyaki-89]

use --inspect-brk

you're magician

[mm41707]

• find a hex editor, open node.exe, search for portIsFree, currently 2 results comes up, one of them has timeout = 2000 nearby, replace it with a higher value, I suggest 9999.

Hey! Great job. I didn't even expect to find any plain text parameters inside win PE file. Great clean solution, without any 3rd party modules. That's what i was hoping to get. Cheers man!

[Ang3lExtreme]

@mikemaccana Today, I am in a bit of debugger/patcher mood, so here is 4th, but surely unsupported method. After this, node inspect works without timeout error.

• find a hex editor, open node.exe, search for portIsFree, currently 2 results comes up, one of them has timeout = 2000 nearby, replace it with a higher value, I suggest 9999.

While doing that, you will notice that Node.js actually holds packages almost as is. If you look at the beginning of the file, you will see the "native" codes. Native codes are only read by machine logic (assembler). In contrast, packages are hold as their human readable form.

Actually I didn't expect this result. Anyone may apply this method on their free will, just should not expect support if something else gets broken.

you are a god!

[rathore-raj]

any Of This is not working

[ghost]

try this:

node --inspect-brk app.js

it works fine with me.

[rajithaeyee]

node --inspect-brk app.js solves the problem

[rathore-raj]

Thanks Now its Working😅

[dwkrueger2]

We need to move the
node --inspect-brk app.js to the top of this feed instead of the bottom.

[yilmazdurmaz]

"--inspect" and "--inspect-brk" does things in slight different ways, and depending on what you need the second does the jobs.

we have a fix about the "timeout" for "--inspect" already committed&merged, so possibly the next node version change will include it. as for the fix, it is an increased value on the setTimeout function, 2000 to 9999, because the problem here is that Windows is somehow slow on taking the requested port, about 3-5 seconds, thus timeout was happening.

keep an eye on it and update your node installation when the fixed one comes out.

[jkrems]

Update: A change increasing the timeout has landed here and there's an open PR to pull it into node (nodejs/node#33447).

[chumaachike]

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

try node --inspect-brk filename.js

[PassionateInCoding]

Still I am facing issue with debugging. Didn't worked for me. Using node version v12.18.0.
node --inspect-brk index.js
Debugger listening on ws://127.0.0.1:9229/93410f83-bdd1-488d-bcc9-595904b41697
For help, see: https://nodejs.org/en/docs/inspector

[vivekvking]

Go to your chrome browser and enter the url: chrome://inspect
then you will find something under remote target, then just click on the inspect option given over there and you are good to go.
If you donot find anything under remote targets then click upon configure option there and enter the ip that you got on the console that is 127.0.0.1:9229

[PassionateInCoding]

@vivekvking , i have updated chrome://inspect and added configuration - discover network targets as 127.0.0.1:9229. But the issue resists to
Error: Timeout (2000) waiting for 127.0.0.1:9229 to be free
then realized, under https://nodejs.org/en/docs/guides/debugging-getting-started/ for latest version we need to install independently [npm install -g node-inspect] and [node-inspect myscript.js] worked for me.

[sagartyagi121]

If you want to debug your code use node --inspect yourJs.js
not node inspect yourJS.js

[juniorbuba]

Tried everything and none worked but node --inspect app

[jochri3]

@mikemaccana Today, I am in a bit of debugger/patcher mood, so here is 4th, but surely unsupported method. After this, node inspect works without timeout error.

• find a hex editor, open node.exe, search for portIsFree, currently 2 results comes up, one of them has timeout = 2000 nearby, replace it with a higher value, I suggest 9999.

While doing that, you will notice that Node.js actually holds packages almost as is. If you look at the beginning of the file, you will see the "native" codes. Native codes are only read by machine logic (assembler). In contrast, packages are hold as their human readable form.

Actually I didn't expect this result. Anyone may apply this method on their free will, just should not expect support if something else gets broken.

You're great❤️❤️❤️

[jbrandona119]

Typed up a whole gosh darn thing and after reading the docs I got it working finally! After installing globally with "npm install -g node-inspect" and restarting the terminal, I was able to use "node-inspect fileName.js" and it successfully starts and keeps the debugger running in that terminal. I suggest trying that if you're still struggling. I did try "node inspect" and "node --inspect" but they didn't work. What a strange issue!

[yilmazdurmaz]

Hey there all future newcomers to the topic (and some old still struggling).

TL:DR - we have many possible solutions. please try to read comments.

I wish comments were not this long and we had the habit of reading long things, impossible by our nature.

just know that, we know the problem and we have the solutions.

PROBLEM: newer version of windows is slow to assign debug port that takes about 3-5 seconds, but this debug utility had a predefined (working in the past) 2 seconds timeout. this is the only reason we have this issue.

SOLUTION: we already have the fix submitted to Node.JS codebase, and sometime in the future, depending on Node's own release schedule. until then there are many working solutions depending on your expectation, so please, please, please read these comments and try solutions.

thanks for patience

PS: the solution in above comment works now without any modification because we really have it fixed here. two post above works too because of the nature of the problem; we need a simple timeout increase.

PS: I really hope new readers will at least read the last post in the line, and keep this one as the last post.

[harikanani]

To clarify, the command to start the CLI debugger on a custom port is node inspect --port=9230 path/to/script.js.

When using node --inspect, the error above shouldn't appear since that's the program being debugged, it's not starting the CLI debugger (node-inspect).

I'm having

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

Same Issue is there but this Command Works for Mine.

node --inspect=127.0.0.1:9230 app_name.js

Thanks

[yilmazdurmaz]

Hi all

Latest Node v12.19.0 and v15.0.1 now has the fix in them (timeout set to 9999ms). Please update your installations when you are ready.

@jkrems , this #48 and #54 issues should be safe to be marked as solved.