Closed Account |
Jan 12, 2014 8:42 PM
|
![]() |
Server has had no firewall rule changes nor server queryclient changes.
GameTracker IP addresses are currently whitelisted on server config. Local Query and Remote query are functional server, and from secondary remote locations. Server In Question UnitedOperations - Teamspeak 3 IP: 70.42.74.59 Port: 9987 Query Port: 10011 http://www.gametracker.com/server_info/70.42.74.59:9987/ Unsure in how to proceed at this time, as I would like GameTracker's reporting to be functional with my Teamspeak Server. Edit - Within 5 minutes of creating this thread, GameTracker did update and indicate that my server is now alive for the first time in the last 6+ hours. I am unsure if later scans will continue to report as alive/active. |
burn • PM |
Jan 12, 2014 8:52 PM
|
![]() Posts: 10924 |
Sounds good. Let me know if you run into issues again and I can check it.
![]() |
Closed Account |
Sep 07, 2014 8:47 PM
|
![]() |
Same issue is occurring again.
There have been no changes to the firewall rules. I have updated the query IP addresses that GameTracker uses a few times last week, after the error started, to include the new addresses, but no change has been observed. Scanning has been down for a few days now. No changes have been made to this server before this change had occurred. |
burn • PM |
Sep 07, 2014 8:58 PM
|
![]() Posts: 10924 |
It's down because the query permissions were removed.
TS3 Welcome to the TeamSpeak 3 ServerQuery interface, type "help" for a list of comm ands and "help <command>" for information on a specific command. use port=9987 error id=0 msg=ok serverinfo error id=2568 msg=insufficient\sclient\spermissions failed_permid=23 clientlist error id=2568 msg=insufficient\sclient\spermissions failed_permid=27 channellist error id=2568 msg=insufficient\sclient\spermissions failed_permid=25 More info @ http://www.gametracker.com/games/ts3/forum.php?thread=42258 ![]() |
Closed Account |
Sep 07, 2014 11:16 PM
|
![]() |
Server Groups had been working properly. Confirmed Settings.
Issue Seen/Resolved - Channel Guest permissions were modified/lost. Added same permissions as above from Guest accounts to channel guests and scanning was restored. Thank you for your assistance. |