TeamSpeak 3 server problems

Common TeamSpeak 3 server problems. See TeamSpeak 3 settings.

Where is my privilege key (admin token)?

Why it happens: On first start, TeamSpeak generates a server admin privilege key (along with the ServerQuery login details) and shows it in the Console. It gives you server admin rights.

How to fix it:

1. Open Console and scroll to the very start of the first run.
2. Look for the line ServerAdmin privilege key created, please use the line below. The line after it starts with token= and is your key.
3. Copy the key after token=. In the TeamSpeak client, open Permissions, then Use Privilege Key, and paste it.
4. If you cannot find it, open a ticket.

Privilege key is invalid or already used

Why it happens: A privilege key normally works once. A second server also has a different key.

How to fix it: Check you used the key from this server’s Console. If the server was reset or reinstalled, a new key is printed on the next first start. Open a ticket if you have lost admin access.

Cannot connect to my server

Why it happens: Wrong address, port or password, or the server is offline.

How to fix it:

1. Check the status is Online.
2. Use the address and port shown on Network. See Network and ports.
3. Leave the port out if your TeamSpeak address already contains it.
4. See Can’t connect to any game server.

Connection failed, “Server version is too old” or “Client version is too old”

Why it happens: The server and TeamSpeak client versions are too far apart.

How to fix it:

1. Update your TeamSpeak client.
2. Check Server Version (TS_VERSION) on Startup. latest gets the newest.
3. Restart the server.

Server is full, or too many users

Why it happens: A TeamSpeak 3 server has a slot limit, the most people connected at once. Our plan allows up to 32 slots.

How to fix it:

1. Ask idle users to leave.
2. If you need more than 32 slots, open a ticket and tell us how many you need.

“You are banned from this server”

Why it happens: A ban was set on the user’s name, IP address or unique ID, either by an admin or an auto ban.

How to fix it:

1. As an admin, open Permissions > List Bans in the TeamSpeak client.
2. Delete the ban, or check who set it.
3. If you locked yourself out by banning your own IP, open a ticket.

Permissions do not work as expected

Why it happens: TeamSpeak uses server groups and channel groups, and permission values compete. Higher power beats lower.

How to fix it:

1. Open Permissions > Server Groups and check the groups the user is in.
2. Check i_group_needed_modify_power style permissions, which limit what a user can grant.
3. If it is still unclear, open a ticket.

ServerQuery does not work, “Access denied”

Why it happens: Query access needs the right password, and the protocol must be allowed. The query user is separate from a normal user.

How to fix it:

1. On Startup, set Server Query Admin Password (SERVERADMIN_PASSWORD).
2. Check Query Protocols (QUERY_PROTOCOLS_VAR) includes the one your tool uses (raw, ssh or http).
3. Restart and use the address and query port shown for your server. If the query port is not listed on Network, open a ticket.

Password not accepted

Why it happens: The server password and the query password are two different things.

How to fix it: The server password is set from inside TeamSpeak (server settings). The query password is the Startup value.

Server stuck or restarts on its own

Why it happens: Bad config or update.

How to fix it: See Server keeps restarting.

Voice quality is poor or laggy

Why it happens: Usually the player’s network, not the server.

How to fix it:

1. Ask the person to check their microphone and codec settings in the client.
2. Test from a different connection.
3. Open a ticket if many users have trouble at once.

Still stuck?

Open a ticket or ask on Discord. See Contact support.