Hi Guys, im trying to add an Dayz server to the gametracker, but i can to add it as it seems to :

One of the following suggestions may help you:

Your server is currently offline.
GameTracker needs your server to be online before you can add it to our database. Please restart your server and make sure it's up before hitting ADD SERVER again.
You entered the wrong query port.
Please update your query port and hit scan again
Your server is firewalled.


On the network level, i can see packets comming from gametracker IPs, response is getting back, but no futher query comming. What shall i do ? The server is running on internal network, the packets are NATed - there are only UDP ports opened ( as arma is not using TCP).

The IP is 195.47.117.130, port 2302. I'd even put GameTrackerClaimServer into the servers name, but no change.

Can you point me what im doing wrong ?
Thanks.

At first glance, your server does not seem to be using the correct query protocol. Have you made any changes to the server that may have caused this? I would recommend doing a reinstall of the server to see if there is any difference before your configuration.

Im sorry, but im using Arma 2 with latest Dayz installed. The server uses private Bliss Hive - may be this the cause ?

Hi, no change at all - reinstalled to latest Arma II, latest Dayz Bliss Hive and nothing changed.

Hm, im using the same configuration as http://www.gametracker.com/server_info/95.156.214.152:10500/, except it is running on private server with NATed public IP...

Hello,

It is difficult to tell exactly where the problem would lie on your end. From our side, it appears that your DayZ server is using a different query protocol. I tried adjusting our scanner for the differences being reported by your server, and it did not help.

I'm not familiar with DayZ administration, but if the protocol changed, I would expect to see more servers down on this graph: http://www.gametracker.com/images/graphs/game_graph_server.php?GMID=176
This leads me to believe that the issue is only affecting your server.

My guess is that it is likely related to your private server 'bliss hive', or something modifying packets on the machine running the actual server.

Best regards.

Solved, the issue was in the firewall settings - as we control everything, the reporting runs on UDP protocol, not TCP. Something which i need to 'sniff', including BE server communication.

OK - good to hear that you're up and running. Thanks for replying back with your solution.

Best regards.