FAQ

So that TS3index.com can query the server information as well as the client, channel and server group lists permissions are required (e.g. to generate the viewer). The needed permissions are not granted in the default configuration. The error message can also be used to find out which permissions have not been granted. Please use these instructions to grant the necessary permissions.

Step 1: Enable "advanced permissions system"

The advanced permissions system is required for the adjustment. The "advanced permissions system" can be enabled in the options menu.

Select Tools in the top menu bar and Options (ALT + P) at the bottom. In the options dialog, Application should be preselected on the left. On the right side under Misc the checkbox next to Advanced permissions system must be checked.

The settings are saved with OK.

Step 2: Allow needed permissions

First connect to your TeamSpeak 3 server, select Rights in the top menu bar and then Server Groups (CTRL + F1). In the new window you will find all server groups on the left.

TS3index.com connects as a guest query with your TeamSpeak 3 Server therefore now select the server group Guest. It is possible that the server group has already been renamed.

You will find all permissions of your server group in the middle divided into categories. Please grant all needed permissions as shown in the screenshot. You can either double-click or right-click and choose Add permission. If the permission has already been granted but the right checkbox (value) is not checked, then the checkbox must be checked manually.

Note: The names of the permissions are shown in the screenshot. You can switch the view with the dropdown menu below the list.

In the TeamSpeak 3 Permission List you will find an overview of the permissions and their meaning.

There are two good reasons for this error message:

1. the TeamSpeak 3 server was stopped on the instance
2. there are multiple TeamSpeak 3 servers with the same port on the instance

TS3index.com select the TeamSpeak 3 server with the port. If there are other (stopped) TeamSpeak 3 servers with the same port on the instance then the first created and therefore maybe the wrong stopped TeamSpeak 3 server will be selected.

You need to change the port of the other TeamSpeak 3 servers on the instance to solve this problem. If you have rented a TeamSpeak 3 server, you will need to contact the hoster.

The ServerQuery of the TeamSpeak server refuses to connect because of wrong login credentials. In the connection settings the owner of the server has set a ServerQuery login. With this data TS3index.com cannot connect.

1. A ServerQuery login is bound to the identity of the user and there is only one ServerQuery login per identity. If you have created a new ServerQuery login, the old ServerQuery login has been replaced.
2. The user and the ServerQuery login was manually removed from the database.
3. Restoring the TeamSpeak server using a backup, because ServerQuery logins are not saved in a snapshot.

In order for TS3index.com to connect to the server again, the owner must set a new ServerQuery login in the connection settings. The ServerQuery login is not required for the default RAW protocol. The servergroup Guest needs more permissions so that TS3index.com can query the server without ServerQuery login. Our FAQ "insufficient client permissions" will help you.

TS3index.com connects to the TeamSpeak 3 server every 10 minutes and calls the latest server information and client, channel and server group list.

We try to keep the number of requests as low as possible so that TeamSpeak's flood protection does not block. Unfortunately, the viewer but also the number of servers per IP address can cause the limits to be exceeded. The later consequence is an "flood ban".

It is the result of "client is flooding". To prevent this, we recommend to enter the IP address of the serverlist 176.9.67.51 in "query_ip_allowlist.txt" (formerly "query_ip_whitelist.txt").

The file can be found in the main folder of the TeamSpeak 3 server. If you have rented a TeamSpeak 3 server, first check if a whitelist entry is possible via the hoster's web interface. If not possible, then you will need to contact the hoster of the TeamSpeak 3 server.

There are two good reasons for this error message:

1. the ServerQuery login is invalid (too many login attempts)
2. or it is the result of "client is flooding" and to be equated with "flood ban"

Step 1: Open the index of your TeamSpeak 3 Server

Step 2: Add Serverowner

Step 3: Login

Step by step:

If the connection to the TeamSpeak server is not possible you can update the address by trying to add the TeamSpeak server again.

The unique identity of a TeamSpeak 3 server can be used to determine whether the TeamSpeak server already exists in the server list. If the TeamSpeak server exists with a different address but is offline, then the new address is taken over.

If you have authorized yourself as the owner of the TeamSpeak server, then you can also hide information such as version, platform, ping, packet loss, traffic usage but also many other client and server statistics via the settings.

The TeamSpeak 3 server can only be deleted from the server list by the owner or an authorized person. There are two ways to delete the TeamSpeak 3 server from the list:

1. If you are authorized as the owner, the fastest way is via the "Edit" button.
   How you can authorize yourself as the owner is described here.
2. Without authorization, the entry can be deleted if you place the key DELETE#TS3INDEX anywhere in the server name or in the welcome message. If the server list finds the key during the next check, the TeamSpeak 3 server will be removed from TS3index.com.

Attention: All collected information and statistics will be irrevocably lost. If there are any problems you can contact us via our contactform.

The blacklist can be used to prevent an unauthorized re-added of a TeamSpeak server into the serverlist. A server on the blacklist cannot be added at TS3index.com.

The blacklist does not delete a server from the serverlist. If the server is already entered in the list, then you need to delete the server.

If a TeamSpeak 3 server is listed at TS3index.com, the current server information as well as client, channel and server group list are called every 10 minutes. If a problem occurs, the TeamSpeak 3 server will be displayed as "Offline".

The viewer will help you narrow down the cause. If the connection can be established but the information cannot be retrieved, then you will find an error message with "insufficient client permissions" there. You can solve the problem with Error Code: 2568 insufficient client permissions.

If the connection cannot be established, then the server address or query port has changed or the connection is blocked (e.g. firewall/flood protection).

We try to keep the number of requests as low as possible so that the flood protection of TeamSpeak does not block. Unfortunately, due to the viewer but also due to the number of servers per IP address, the limits can be exceeded. We recommend adding our serverlist IP address 176.9.67.51 to "query_ip_allowlist.txt" (formerly "query_ip_whitelist.txt"). The file can be found in the main folder of the TeamSpeak 3 server. If you have rented a TeamSpeak 3 server from a hoster, first check whether a whitelist entry is possible via the hoster's web interface. If no whitelist entry is possible via the web interface, you have to contact the hoster of the TeamSpeak 3 server.

If only the IP address or the query port has changed, you can change the data in the settings tab.

The connections are ServerQuery Cleints, which you can only see as Server Admin if you have enabled the option "Show ServerQuery Clients" in your favorites. In the standard configuration, a guest or member doesn't have permissions to see the query connections - not even with the "Show ServerQuery Clients" option.

If a TeamSpeak 3 server is listed at TS3index.com, the current server information as well as client, channel and server group list are called every 10 minutes. Only with this information is it possible to display the viewer on the website or to create statistics, banners or other helpful information.

The TeamSpeak server, like the client, has a unique identity (UID).The first setup creates the identity. It is impossible for the identity to exist more than once - therefore the identity is used to filter out duplicate entries in the server list.

If the identity is identical, then it is practically the same TeamSpeak server or a copy. The database must have been duplicated and/or a snapshot must have been used.

The snapshot option has been increasingly misused in the past. If you have imported a snapshot from any free channel template offered on the Internet, you have also taken over the identity. You are using the unique identity of the original TeamSpeak server.

Only votes from the last 30 days are listed in the server list. If these are legitimate votes, then we take no action. However, it goes without saying that fake votes will not be tolerated.

We have implemented several security measures to filter the majority of fake votes through Proxy/VPN or Tor. In case of unusual behavior, a manual check is performed. If a consistent pattern is detected, the affected votes are removed.

The server name must be changed to complete the authorization. A connection to the TeamSpeak server is established and the server name is checked.

With this measure we can ensure that only authorized persons can register as owners. If the step was successful, the server name can be changed back to the original state.