ng serve connect ETIMEDOUT

[bafinneg]

Please provide us with the following information:

OS?

macOS Sierra

Versions.

angular-cli: 1.0.0-beta.17
node: 6.5.0
os: darwin x64

Repro steps.

ng new test
cd test
ng serve

The log given by the failure.

Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
Error: connect ETIMEDOUT fd00:9ca4:7675:4e2e:7153:a688:b525:2149:4200
at Object.exports._errnoException (util.js:1026:11)
at exports._exceptionWithHostPort (util.js:1049:20)
at TCPConnectWrap.afterConnect as oncomplete

Mention any other details that might be useful.

Hello!

Today I've been encountering a timeout when trying to run ng serve on a new (or ng init) project.

ng build works fine
ng serve in my existing projects work fine

Uninstalled & reinstalled angular cli using the instruction, no change.
Not sure what's causing the timeout on this go around. No recent updates to my dev environment.
Thank you!

---

Thanks! We'll be in touch soon.

[decooliveira]

I'm going through the same problem.

[haninaguib]

Same here

[nemec784]

Same problem

angular-cli: 1.0.0-beta.17
node: 6.8.1
os: darwin x64

[haninaguib]

ps: Still cant find a solution (not even sure what the problem is).
I am not running behind a proxy or anything strange.

OS X: 10.11.6 (El Capitan)
angular-cli: 1.0.0-beta.14 (also tried beta.17)
node: 6.8.1
os: darwin x64

It is a new project. (ie created via ng new today)
Existing projects are working.

[b091]

I think it's because some of the angular-cli dependency which was automatically updated because of "^version".

If you will delete ./node_modules and make npm install your existing project will get the same issue ;)

I dont know which one yet

[bafinneg]

Good find @b091! That's a good lead.
I wonder if fixing up package.json would could be a workaround? I'll be able to try it tomorrow.

@haninaguib same here no proxy on my end either.

[nikejaycn]

Same problem in the new ng project.
the old project working well.

os: macOS Sierra
angular-cli: 1.0.0-beta.17
node: 6.8.1
os: darwin x64

[b091]

portfinder is an issue it works with 1.0.7 it's not working with 1.0.8

[nemec784]

Yep,

npm install [email protected]

solves the problem

[l3bel]

Same here.
Turning WiFi off before issuing "ng serve" works for me

[l3bel]

@b091, @nemec784 , npm install [email protected] works, thanks !

maybe a clue, maybe not, but with wifi off (read: machine IP is 127.0.0.1), the server starts without issues, even without downgrading portfinder to 1.0.7
npm install [email protected] definitely worked for me
os: macOS Sierra
angular-cli: 1.0.0-beta.17
node: 6.8.1
os: darwin x64

[mikedsharp]

Just wanted to note that prior to running
npm install [email protected] (which worked for me), my ng serve would just hang, this is definitely an issue in beta 17

Projects created with previous versions run fine.

I'm running OSX Yosemite

[b091]

portfinder 1.0.9 released it's working now. You can close this issue ;)

duplicating #2769

[filipesilva]

Dupe of #2769, fixed by #2831

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}