Halloween at Nexthosting: 10% off game servers with the code – until November 1
Practical guide for self-hosters: TeamSpeak server on a VPS, ports 9987/10011/30033, VPS sizing guidelines, licensing, and security tips.
Yes, a TeamSpeak server runs reliably on a VPS. The first step is to get a VPS with root access, connect via SSH or RDP, download the server archive from the official TeamSpeak download area, and open the required ports. TeamSpeak 3 is still considered the most practical version for self-hosters in 2026 because its permission system and plugin ecosystem are mature. After that, you are responsible for updates, backups, and license checks yourself.
In short:
- A stable TeamSpeak server requires a VPS with root access, sufficient upload bandwidth, and a dedicated, restricted system user.
- Server size depends mainly on the number of users; for large communities, higher network priority and DDoS protection matter more than additional processing power.
- Installation on Linux is quick, but it requires secure handling of the privilege token as well as regular updates and backups for stable performance.
- For Windows servers, an RDP connection is sufficient, but firewall rules and automatic startup configuration are essential to keep the server securely and permanently reachable.
- When choosing a VPS, look for guaranteed bandwidth, professional DDoS protection, and reliable support to ensure stable connections and a secure environment in the long term.
Nothing works without root access. You need a VPS with full root access (Linux) or administrator rights (Windows), access via SSH or Remote Desktop, and at least basic command-line skills. Ubuntu LTS and Debian are the best choices for an operating system, since both offer long support cycles and extensive community documentation. Windows Server works as well but usually involves somewhat more administrative effort.
Surprising to many: the first limit on a TeamSpeak server is not processing power but bandwidth. Voice data is small, but with many simultaneous connections the traffic adds up quickly, especially on the upload side of your VPS.
From a security standpoint, there is a simple rule: create a dedicated system user for TeamSpeak and never let the service run as root permanently. Otherwise, a compromised process with root privileges opens the door to the entire system.
On licensing: the free license is enough for small, non-commercial communities. If you use the server commercially or need more slots, you need a Gamer or Commercial license. The license file is your responsibility; it must be stored securely and taken along when you move the server.
The right VPS size depends almost entirely on the number of concurrent users, not on game load as with a game server. TeamSpeak itself is resource-efficient; voice packets barely load the CPU and RAM.
For a small community, an entry-level VPS with sufficient RAM is entirely adequate. As the number of users grows, the network connection becomes more important than additional processing power. With many simultaneous connections, a VPS with more guaranteed bandwidth and a more stable network connection is recommended so that voice quality and latency do not suffer.
| Concurrent users | Recommended resources | Key criterion |
|---|---|---|
| Small number | A few vCPUs, matching RAM | Stable baseline connection |
| Medium number | More vCPUs and RAM | Sufficient upload bandwidth |
| Larger number | Even more resources | DDoS protection and guaranteed bandwidth |
NVMe storage is worthwhile mainly for fast backups and log files, less so for the actual voice operation. If you make the server publicly visible and list it in community directories, you should treat DDoS protection as a fixed selection criterion, because servers like that are often targeted. A server location in Germany also reduces latency for most German-speaking users and makes support easier when questions come up.
Pro tip: If you don't have the time or desire to manage a server yourself, consider a preconfigured VPS package instead of a do-it-yourself installation on a bare system.
Installation on Ubuntu or Debian follows a fixed procedure that can be completed in a few minutes.
apt update && apt upgrade).adduser teamspeak, and switch to it.wget.tar -xjf) and change into the resulting directory../ts3server_startscript.sh start or set up a systemd unit so that it starts automatically after a reboot.At the very first start, the privilege token is the only way to log in as server administrator. If it is lost, often the only option is a complete reinstallation of the database.
Docker is an alternative. A container isolates the TeamSpeak process from the rest of the system and makes updates easier, because you simply pull a new image instead of patching manually. A typical start command looks roughly like this: docker run -d -p 9987:9987/udp -p 10011:10011 -p 30033:30033 teamspeak. For continuous production use, a systemd unit is often still the more stable and more easily monitored solution.
On a Windows VPS, setup goes through Remote Desktop Protocol instead of SSH, but the basic process is similar.
First you connect to the VPS via RDP and download the Windows server archive from the official TeamSpeak Download Center. After extracting it, you start ts3server.exe manually once to have the privilege token displayed, and write it down immediately in a safe place.
The Windows firewall must then open the required ports. This takes only a few commands in PowerShell, for example:
New-NetFirewallRule -DisplayName "TS3 Voice" -Direction Inbound -Protocol UDP -LocalPort 9987 -Action AllowNew-NetFirewallRule -DisplayName "TS3 Query" -Direction Inbound -Protocol TCP -LocalPort 10011 -Action AllowNew-NetFirewallRule -DisplayName "TS3 FileTransfer" -Direction Inbound -Protocol TCP -LocalPort 30033 -Action AllowTo make the server run automatically after every restart, you create a task in the Task Scheduler that runs ts3server.exe at system startup, regardless of whether anyone logs in.
One important security note to finish: don't let the server process run permanently under an administrator account. A separate, restricted user account limits the damage if the process ever becomes vulnerable.
A TeamSpeak server needs several ports opened in the firewall so that clients can connect and all features work.
Two firewalls often stand in the way here: your provider's firewall at the network level and the one built into the operating system itself, such as ufw on Ubuntu or the Windows firewall. Both must allow the same ports, otherwise the connection stays dead even though the server is running. With tools like nc or nmap run from an external machine, you can quickly check whether a port is actually reachable.
For a clean address, a DNS A record pointing to the server IP is worthwhile, optionally supplemented by an SRV record. That way, users connect through a domain name instead of a bare IP address. If you want to stay private, you should also keep the server out of public server directories.
Pro tip: Always test your port's reachability from outside your own network, not from the VPS itself; otherwise you may miss a blocking provider firewall rule set.
The free license is completely sufficient for small communities and allows a limited number of slots. If you need more slots or run the server commercially, you need a Gamer or Commercial license, which directly determines the maximum number of users.
Important for operation: the license check is performed over TCP port 443 against the license server, so this port must remain permanently open. The license file itself is among the most critical files on the server and should be backed up regularly.
If your community grows significantly, check the license terms early, before slots run short.
A running server is only half the job. Regular backups of the database file ts3server.sqlitedb, the license file licensekey.dat, and the configuration file ts3server.ini protect you from having to start over completely after a server failure.
127.0.0.1For monitoring, a simple process check that verifies whether ts3server is still running is often enough, combined with monitoring of upload bandwidth. As a recovery checklist, it helps to define in advance: restore the backup, restart the service, retest the ports, check the license status.
Pro tip: Never store backups exclusively on the same VPS. A second storage location protects you even if the entire server goes down.
Most connection problems can be narrowed down in a few minutes before deeper troubleshooting is needed.
nc -zv IP 9987.If these steps don't solve the problem or you simply lack the time for ongoing administration, a managed hosting offering with technical support becomes a real alternative to hours of research on your own.
TeamSpeak itself scales well vertically: more bandwidth and a larger VPS package are enough for most communities, even when the member count grows considerably. Unlike a game server with increasing game load, pure voice operation stays computationally cheap as long as enough network capacity is available.
For truly large communities with several hundred concurrent users, it is worth moving to a larger VPS or even a dedicated server instead of constantly upgrading the existing package. A dedicated server offers guaranteed resources without noisy-neighbor effects from other VPS instances on the same hardware.
An often overlooked scaling lever is the server structure itself: many small channels with active voice connections generate more traffic than a few large channels. If you organize your community into clearly structured areas and merge inactive channels, you reduce unnecessary load without spending a single extra cent.
Licensing also becomes relevant as you grow: slots and license tier must grow along with the member count, otherwise the license limits the community long before the server itself reaches its technical limits. If you expect steady growth, it is better to plan for the next license tier in advance rather than reacting only once the limit is reached.
For communities that also run a game server in parallel, for example for Minecraft or Rust, it is worth considering whether both services should run on separate resources so that game load and voice operation don't slow each other down.
Not every VPS is equally well suited for continuous TeamSpeak operation, even if the raw resource requirements look low. Three things are decisive: guaranteed rather than shared bandwidth, working DDoS protection, and support that is actually reachable when network problems occur.
Budget VPS offers often advertise low prices but throttle the network connection during load peaks, exactly when many users are speaking at the same time. For a small private community this may hardly be noticeable, but for an active gaming community with several voice channels it quickly becomes a problem.
When comparing support, the biggest difference between providers rarely shows in raw server performance but in response time during incidents. A provider located in Germany usually offers shorter latencies for German-speaking users and a more direct communication channel in support cases than distant international providers.
If you're unsure whether a plain VPS or a preconfigured managed solution makes more sense, you should assess your own time realistically: self-hosting saves money but continually costs time for updates, backups, and troubleshooting. A VPS offering with prepared templates reduces this effort considerably without giving up control of the server entirely.
The widespread assumption that TeamSpeak is technically more demanding to host than a modern game server is not accurate. The actual server process is lean, and with the right steps the installation takes barely longer than twenty minutes. What is really underestimated is continuous operation: updates, backup discipline, and port rules are quickly done once, but they come back, month after month, as soon as new users join or a security vulnerability is reported.
Many guides online focus too much on the one-time installation and too little on what happens afterward. This is exactly where a stable server is separated from one that produces outages after three months because nobody set up log rotation or the backup has been failing for weeks without anyone noticing.
A second blind spot: bandwidth. If you look only at CPU and RAM and ignore the actual network connection, you will later be surprised by voice dropouts with twenty concurrent users, even though the server could on paper handle considerably more. If you take these two points seriously from the start, operation and bandwidth instead of just installation, you spare yourself most of the problems that end up in forums as “TeamSpeak runs unstably.”
Setting it up yourself saves money but costs time for port rules, backup routines, and security updates that never quite stop. If you don't have that time, or want to secure public operation with DDoS protection from the start, you are better served by a prepared VPS from Nexthosting than by hours of self-configuration on a bare system. You'll find technical specifications, available resource tiers, and details on backups directly on the product page. If you also run a game server in parallel, for example for Garry’s Mod or FiveM, you can set up both services independently of each other without getting in each other's way during load peaks. Take a look at the matching VPS tier and start setting it up right away.
You rent a VPS with root access, download the server archive from the official download center, open ports 9987, 10011, and 30033 in the firewall, and start the service via script or systemd unit.
The TeamSpeak software itself is free for small communities; larger slot counts require a Gamer or Commercial license. On top of that come the ongoing costs for the VPS, whose price depends on the resource tier and provider.
It depends on the purpose: TeamSpeak offers full control over your own environment, high audio quality, and does not require user accounts, whereas Discord focuses more on central administration and a broader range of additional features.
Yes, with the free license and your own server or an inexpensive VPS, you can run a small TeamSpeak server without any additional software costs, limited only by the maximum slot count of the free license.