3 ms·
Yup, that's because we connect to port 8080 directly (that's the port the server is running on internally, see http://fititgame.com:8080 http://fititgame.com:80
by sgehlich 14y ago
Yup, that's because we connect to port 8080 directly (that's the port the server is running on internally, see http://fititgame.com:8080 http://fititgame.com:8080). But unfortunately, we can't fix this right now since nginx isn't able to forward websockets, yet (AFAIK, correct me if I'm wrong)
- Khao 14y agoIf you're running on a single server with nginx I guess the only way you could fix this is by getting a second IP address from your host to point on your server and binding nginx to one IP and node on the other IP.