How to host a TeamSpeak 3 server: privilege key, permissions and backups

TeamSpeak has been the voice server of choice for clans, guilds and esports teams for years, and plenty of communities still prefer it: low-latency voice, fine-grained permissions, and a server that you control rather than one run by a platform. Running your own means deciding who can talk where, who can kick or ban, and keeping your channel layout exactly as you want it. This guide covers what a TeamSpeak 3 server is, how to claim admin on a fresh one, how to set up channels and permissions, and how to keep it backed up.

What you are hosting

A TeamSpeak 3 server is a program that your members’ TeamSpeak clients connect to. It handles voice, text chat, channels, file transfers inside channels, and a detailed permission system. Members connect using the server’s address, and everything about the server, from channel names to who can use push-to-talk in which room, is stored in its database.

By default the server keeps that data in an SQLite database file, ts3server.sqlitedb, next to the server itself. That file is the heart of your server: channels, groups, permissions, bans and registered identities all live in it.

Why run it on a server rather than at home?

You can run TeamSpeak on a home PC, but every member then depends on your machine being on and your upload being steady. A voice server needs to be reachable whenever your community wants to talk, often late at night and across time zones. A hosted server stays on, restarts itself if the process exits, and keeps your home IP address out of everyone’s connection details.

What resources it needs

TeamSpeak is efficient. The server itself uses little CPU and memory; most of what it does is pass voice packets between clients. The main things that grow with your community are:

• Concurrent users. More people talking at once means more traffic through the server.
• Voice quality settings. Higher-quality codec settings on a channel use more bandwidth per speaker.
• File transfers. If members upload files to channels, those take up storage.

Small communities need very little. Size by how many people are on at your busiest time, not by how many have ever joined.

Licence notes

The TeamSpeak 3 server is proprietary software from TeamSpeak, and its licence decides how many slots and virtual servers you can run. You also have to accept the licence agreement before the server will start for the first time. Before planning a very large server, read TeamSpeak’s current licence terms on its own site, since they set the limits rather than the host.

First start: claiming admin with the privilege key

The first time the server starts, it prints two important things to its log:

• A ServerAdmin privilege key, shown after token=. This is a one-time key that puts whoever uses it into the Server Admin group.
• ServerQuery login details for the serveradmin account, used for scripting and administration over the ServerQuery interface.

To claim the server:

1. Connect to the server with the TeamSpeak client.
2. When it asks for a privilege key, paste the token. If it does not ask, use the option to enter a privilege key in the client’s Permissions menu.
3. You now have Server Admin. Save the ServerQuery password somewhere safe.

The privilege key only works once. Use it yourself straight away, before anyone else can, and do not post a screenshot of the console with it visible.

Channels and permissions

TeamSpeak’s permission system is powerful, and the defaults are a sensible starting point. It is built from two kinds of groups:

Server groups

These apply across the whole server. Server Admin holds full control. Create your own groups for moderators, members and guests, each with only the powers they need: moderators who can move and kick, members who can create temporary channels, guests who can only listen in certain rooms.

Channel groups

These apply per channel, such as a channel admin who can manage one team’s room without touching anything else. They are handy for giving each team or squad control over its own space.

A few habits keep things tidy:

• Plan the channel tree first. A lobby, a few general rooms, team channels, and an AFK channel cover most communities.
• Use channel passwords sparingly. Groups and permissions are easier to manage than a list of shared passwords.
• Keep Server Admin small. Two or three trusted people is plenty. Everyone else gets a narrower group.

Keeping it running and reading logs

The panel’s live console shows the server’s output, and TeamSpeak also writes log files that record connections, kicks, bans and permission changes. When someone says they cannot connect or were removed, the logs are the first place to look. If the process exits, the panel restarts it automatically.

Security habits

• Change the server password if it leaks, or remove it and rely on groups instead.
• Protect the ServerQuery login. It can do everything an admin can. Do not share it, and change it if anyone who knew it leaves.
• Review groups now and then. Remove people from admin and moderator groups when they step back.

Updating

TeamSpeak releases server updates from time to time. When you update, the database carries over, but take a backup first so you can roll back if something goes wrong. Read the release notes before a large update.

Backups

Losing ts3server.sqlitedb means losing every channel, group, permission and ban you have built. On GGHOST Cloud, backups run on a schedule you set and restore from the panel without a ticket. If you are moving from another host, upload the database file over SFTP and your channels and permissions come with you.

Getting TeamSpeak on GGHOST Cloud

TeamSpeak hosting is set up on request, so we can size it around your community.

1. Tell us what you need. Ask us on Discord (or open a ticket) with roughly how many people are on at your busiest and whether you are moving an existing server.
2. Get a quote. We size it, quote a monthly price, and set it up on our Pterodactyl panel, usually within a few days.
3. Start the server and copy the privilege key from the console.
4. Claim admin, build your channels, and share the address and port shown in the panel with your members.

You get the full panel at panel.gghost.cloud: live console and logs, file manager, SFTP, startup variables, scheduled tasks and sub-users, with auto-restart if the process exits. Every node is behind DDoS protection from our network providers. Live regions today are Singapore and Europe (France–Germany border), with the United States (East, Central and West), the United Kingdom, India, Japan and Australia on demand. There is no setup fee and no contract, billing is at app.gghost.cloud, and support comes from the people who run the servers, on Discord or at hello@gghost.cloud.

The short version

Accept the licence, use the privilege key from the first start yourself, and save the ServerQuery password. Build a simple channel tree, give people narrow groups rather than admin, and back up ts3server.sqlitedb on a schedule. That keeps a TeamSpeak server tidy and recoverable for years.