Vultr.com - Instant Cloud Server Deployment
Game Rank
Servers:
Teams:
Fans:
23598
Players:
2640
Forum Home > Rust Server Administration & Help > Claim ownership not working
evltick1PM
#1
Claim ownership not working
Nov 30, 2016 1:07 AM
Joined: Nov 18, 2016
Posts: 1
I went into the config and changed the name to GameTrackerClaimServer as it requires. However its not working. gametracker keeps telling me to update it. and it is. ive reset, wiped, reboot, shutdown you name it. wth do I got to do? am I missing something?

thanks in advance.
chimaera500PM
#2
Nov 30, 2016 2:21 AM
GAMETRACKER MODERATOR Joined: Jul 14, 2009
Posts: 4303
Is this the server?

http://www.gametracker.com/server_info/45.32.65.71:28026/

The instructions state that the name must include the string "GameTrackerClaimServer".

At the moment, the server name does not include that string.

When you change name, you should try waiting until Gametracker 'sees' the new name.

__
I am a community user. I do not reply to private message requests for support.
Hint: I do not accept (or reply to) personal requests for re-ranking or unbanning.
You must use the forums please.

Links:
Forum Guidelines | Reporting abuse | Guides & FAQs | General Help
chimaera500PM
#3
Nov 30, 2016 3:07 AM
GAMETRACKER MODERATOR Joined: Jul 14, 2009
Posts: 4303
I had a look via HLSW
Your server name appears to be changed, but Gametracker isn't seeing the name change.

This normally happens when Gametracker scanner expects a different server variable to contain the name, or the scanning port is blocked, or query port has been incorrectly specified (yours is currently set to 28016 on Gametracker).

It appears that most Rust servers use the same port for join and query, and that is the default expectation of Gametracker when adding the server, so I suggest that you check this first.

I have also noted that in HLSW that your server is regularly unable to be scanned at all. Ping timeouts of up to 45 seconds.
This could certainly prevent Gametracker from scanning correctly as the intervals between scans are much longer than for HLSW.

Edit:
To add to the above. There is a distinct pattern in the successful to unsuccessful ping attempts in HLSW.
Your server is responding for 10-15 seconds, and then not responding for 45 seconds. It is a very consistent pattern.


__
I am a community user. I do not reply to private message requests for support.
Hint: I do not accept (or reply to) personal requests for re-ranking or unbanning.
You must use the forums please.

Links:
Forum Guidelines | Reporting abuse | Guides & FAQs | General Help
Last edited by: chimaera500 Nov 30, 2016 4:01 AM
doffePM
#4
Nov 30, 2016 4:19 PM
Joined: Oct 28, 2016
Posts: 3
i can also not claim my server
chimaera500PM
#5
Nov 30, 2016 4:35 PM
GAMETRACKER MODERATOR Joined: Jul 14, 2009
Posts: 4303
__
I am a community user. I do not reply to private message requests for support.
Hint: I do not accept (or reply to) personal requests for re-ranking or unbanning.
You must use the forums please.

Links:
Forum Guidelines | Reporting abuse | Guides & FAQs | General Help