TeamSpeak 3 is one of the platforms VoIP more used and appreciated to communicate in real time, thanks to its exceptional stability and high audio quality. The configuration of a TeamSpeak server allows you to manage your team or community communications autonomously, ensuring flexibility, privacy and total permission control.
This detailed guide will explain how to create a TeamSpeak 3 server on different operating platforms, providing you with clear and simple instructions to be online in a few minutes.
System Requirements to Configure a TeamSpeak Server
Before starting a TeamSpeak server configuration, make sure you meet the following technical requirements:
- A computer or server with at least 1 GB of RAM and a modern processor.
- A stable internet connection (better if wired or hosted in data center).
- Access to the router admin panel to run the Port Forwarding. You can consult teamSpeak official documentation for complete details. Here are the key doors to unlock:
- 9987 (UDP) for incoming audio traffic.
- 30033 (TCP) to transfer files between users.
- 10011 (TCP) for server queries (ServerQuery).
Configuration TeamSpeak Server on Windows
- Download the server software directly from TeamSpeak's official website, choosing the 64-bit version for Windows.
- Configure ports in Windows firewall: Access advanced firewall settings and add network exceptions for required ports. In case of doubt, consult the microsoft official guide on firewall management.
- Launch the server running the downloaded file. At the first opening, copy and save in a safe place the Token Admin (Privilege Key). This exclusive code will allow you to claim absolute administrator privileges (Server Admin).
- Using the normal TeamSpeak client, connect to your new server by entering
127.0.0.1(if you connect from the same PC) or the public IP address of the host machine.
Configuration TeamSpeak Server on Linux (Debian/Ubuntu)
For Linux system administrators, we recommend operating via terminal to ensure greater security. Follow these essential steps:
- Update system repository with command:
sudo apt-get update && sudo apt-get upgrade - Create a dedicated system user to avoid security risks ( never run the server as root):
adduser --disabled-login teamspeak - Download the archive from the official website, extract the content in the created user directory and start the main script.
- To ensure that the server automatically starts rebooting the machine, create a dedicated service file (e.g.
teamspeak.service) in/etc/systemd/system/.
Configuration TeamSpeak Server on macOS
Apple users can configure a local server in few simple steps:
- Download the package from the TeamSpeak website. To accept the terminal license, make sure you create an empty file called
.ts3server_license_acceptedwithin the server folder. - Launch the server executable by double-clicking or by command line.
- Connect via the client by entering the token of administration received.
Frequently Asked Questions (FAQ) About Server Creation
Is creating a TeamSpeak 3 server free?
Yes, basic hosting is completely free for non-commercial uses. The default free license allows you to have an active server with a maximum limit 32 slots (users connected simultaneously). If you have a larger community or business purpose, you will need to purchase an official Gamer or Commercial license from TeamSpeak website.
Can I host the server on my home PC or need a VPS?
You can safely host the server on your personal PC, which is perfect for occasional gaming sessions between friends. However, the server will turn off when you turn off your computer. To have a community always active 24/7 and an optimal latency (ping), it is highly recommended to rent a VPS (Virtual Private Server) cheap on which to install the Linux version of the software.
What should I do if my friends can't connect to the server?
If you can enter (using 127.0.0.1) but your friends receive a timeout error, the problem almost always lies in Port Forwarding or in the firewall. Make sure you open the door 9987 (UDP) in your router and to have it addressed to the local PC IP that hosts the server. Also check that the Windows firewall is not blocking incoming connections for that application.
