ember-cli: ember serve fails when ipv6 disabled

Here’s log:

[user@workstation work]$ ember serve
version: 2.4.2
Looks like you have a different program called watchman, falling back to NodeWatcher.
Visit http://www.ember-cli.com/user-guide/#watchman for more info.
listen EAFNOSUPPORT ::1:49152
Error: listen EAFNOSUPPORT ::1:49152
    at Object.exports._errnoException (util.js:856:11)
    at exports._exceptionWithHostPort (util.js:879:20)
    at Server._listen2 (net.js:1223:19)
    at listen (net.js:1272:10)
    at net.js:1381:9
    at nextTickCallbackWith3Args (node.js:485:9)
    at process._tickCallback (node.js:391:17)

IPv6 is probably disabled on this machine. Is there a way to bind only IPv4 adress?

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 24 (16 by maintainers)

Commits related to this issue

freeze portfinder at a sha; make pass on appveyor so we can close #5602 fixes #5602 — committed to eriktrom/ember-cli by eriktrom 8 years ago
freeze portfinder at a sha; make pass on appveyor so we can close #5602 fixes #5602 — committed to eriktrom/ember-cli by eriktrom 8 years ago
freeze portfinder at a sha; make pass on appveyor so we can close #5602 fixes #5602 — committed to eriktrom/ember-cli by eriktrom 8 years ago
update portfinder version to ^1.0.3; handle test failure on windows fixes #5602 — committed to eriktrom/ember-cli by eriktrom 8 years ago

Most upvoted comments

@ajgordo - can you run this:

netstat -an | grep THE_PORT_IT_TRIED_TO_START_ON

My guess is that the interface its trying to start on is ::0 or ::2 which will happen if you run from a vm like parallels.

See the discussion at the bottom (closed issue) https://github.com/indexzero/node-portfinder/issues/21 which became an open issue on portfinder https://github.com/indexzero/node-portfinder/issues/32

I need to add some more interfaces and would be happy too do so. Let me know what interface you need.

eriktrom on Jul 1, 2016