Master crashes when opening two apps (and port conflicts)

[gaearon]

This is some new issue.

[Timer]

This regression was introduced when we fixed the behavior of our HOST binding. detect-port does not support specifying an address to check on, so we need to switch packages or send a PR upstream to add the functionality.

tl;dr we listen on 127.0.0.1, detect-port checks on 0.0.0.0

[Timer]

Filed an issue upstream: node-modules/detect-port#19.

[gaearon]

Hmm. If we're listening on 127.0.0.1, does it mean access from local network doesn't mean by default anymore? This seems frustrating. Why did we change this?

[Timer]

We've always said we're listening on localhost which implies we're not listening on the entire local network. Mainly, it was done out of interest in security (since we proxy API calls which are going to be elevated during development).

Previously we said localhost but actually listened on 0.0.0.0.

I'm not opposed to listening to 0.0.0.0 by default.

[gaearon]

I'd prefer we keep the existing behavior with using 0.0.0.0 as a default. I'm cool with printing 0.0.0.0 to the console in this case for posterity.

[Timer]

Fair enough, the 0.9.x branch currently does this (and prints 0.0.0.0). I'll send a PR.

[Timer]

Opened #2117; that issue still doesn't solve this issue because Node's default behavior is to bind to IPv6, not IPv4. We might want to follow suit, but it's a bit more involved than specifying :: or 0:0:0:0:0:0:0:0.

[gaearon]

Um. I still don't quite get it. Can we just revert to old behavior in the meantime? Or was that fix important?

[Timer]

It's important because HOST doesn't work otherwise, the issue was already fixed in detect port so we just have to update the dependency and this should start working again.

[gaearon]

Okay. Can you take care of this?

[Timer]

#2126

[Timer]

#2147

[Timer]

Fixed via #2147