Couldn't Run The Example Smoothly about colyseus HOT 8 CLOSED

Hi @ZeroHackeR,

I've never seen this error. Can you provide the version of node and operational system you're using? Thanks!

from colyseus.

Same problem. PORT=80 npm start works fine. With every other port it doesn't.
v. node: v8.1.4, running on docker (ubuntu).

from colyseus.

I didn't have anything running on port 80. That was the problem. If I start a webserver on port 80, I don't get any error when colyseus-examples is running on other ports.

from colyseus.

Oh, I see. Thanks @Federkun!

@ZeroHackeR probably has the PORT environment variable set to 80 for some reason. Using any other (unused) port should be fine!

I've just updated the examples to use a fixed port number instead of prioritizing process.env.PORT.

from colyseus.

Mh, I don't think that's the case. I'm trying to understand why colyseus require an unrelated process running on port 80 to work correctly, but the error message doesn't offer any meaningful information..

from colyseus.

@Federkun Colyseus spawns a match-making process for internal communication only, I'm not sure if this line could be causing the problem: https://github.com/gamestdio/colyseus/blob/c59901e637fc7538f3ea4267a81360c26300e2ee/src/matchmaking/Process.ts#L13

from colyseus.

After some debugging I'm sure that the problem is here:
https://github.com/gamestdio/colyseus/blob/3f0a1ee8ee1d03a9c59459d5348c7c3d58e139e0/src/cluster/Worker.ts#L89
ClientRequest uses the default port (80) instead of the ephemeral port that's been used here:
https://github.com/gamestdio/colyseus/blob/765401e9acab6c09d92a01cea2eeeefc93214110/src/ClusterServer.ts#L112

I'm not sure about the api of ClientRequest, but if we can change the port to server.address().port, it should fix the problem. If I can find how to do it, I'll apply a patch today.

from colyseus.

I had to dig the nodejs repository to learn how to do it. I'll do a pull request in a second, so you can review it.

from colyseus.