search

gabrielbrunop / haxball-server

A small server utility for Haxball
20 stars 4 forks source link

Error #1

Closed rocosttaa closed 3 years ago

rocosttaa commented 3 years ago

image

I've been using this server for a while and when it's time to open the room it's giving it away. Help

rocosttaa commented 3 years ago

Sorted out. Problem was in the syntax by mistake myself.

rocosttaa commented 3 years ago

I have a problem where a room opens but people can't get into it and does not receive messages on the console. Please help.

gabrielbrunop commented 3 years ago

This issue was solved on Discord. Because of WebRTC's local IPs anonymization, implemented on Chrome 78 since it exposed the IP of VPN users (considered a security problem), connections to Haxball became problematic in some VPS.

A server.disableAnonymizeLocalIps option to the configuration file was added. This option disables the anonymization feature, according to Haxball Headless' documentation. Version 4.1.0 has been released with the new option.

If problems persist, make sure you've got all the required ports open. Haxball Server requires the 9500 and 9501 ports to be open and free to work.

It also dinamically attaches ports to Chrome sessions. Although it automatically detects and avoids using ports being used, I recommend reserving the 9500-9520 range to Haxball Server (or 9500-9501 + the number of rooms you want to open with it. I'm pretty sure though you're not going to open more than 19 rooms, so it's safe to use 9520).