linusleonard • PM |
Feb 19, 2015 5:05 AM
|
![]() Posts: 2 |
Hello,
This server is periodically registered as down even though it is up and running, and has been for the last month or so. http://www.gametracker.com/server_info/85.236.100.27:11527/ It's hosted by Multiplay, and it goes online and offline all the time according to Gametracker banners. All permissions are set according to this guide: http://www.gametracker.com/games/ts3/forum.php?thread=42258 I also had to set another permission not listed on the above guide (can't remember what it was) to allow the telnet "clientlist" command. All other telnet commands checks out fine. I didn't follow the guide with regards to the "permid=138 permname=i_channel_subscribe_power permdesc=Channel subscribe power" part, since there is no mention on what to set this to. It's currently greyed out in the server group permissions. It is grey for all other server groups except admin and a "friends" group that has some special priviliges. Wouldn't surprise me if this has something to do with Gametracker IPs not being in query_ip_whitelist.txt, since I cannot reach it because this is hosted at Multiplay. But I don't know how to troubleshoot to make sure this is not the case. And before taking this to Multiplay I want to explore all possible venues, because I'm pretty used to Multiplay support by now, and I'm almost positive their generic answer will be "use our own [inferior] comms tracker". |
burn • PM |
Feb 19, 2015 8:33 AM
|
![]() Posts: 10924 |
If the server shows up, then down, then up without your intervention or any changes to the actual server, something is likely temporarily blocking the GT scanner. It may solve it to put them in the whitelist, but it may also be the server firewall.
I don't know if it's as much of the case anymore, but TS3 used to consider GT as "flooding" for scanning every couple minutes which used to cause a lot of problems showing offline, but I haven't seen that much recently. ![]() |
linusleonard • PM |
Feb 26, 2015 4:10 AM
|
![]() Posts: 2 |
It was something on their end fortunately, fixed now it seems.
![]() |