How to Install a TeamSpeak Server on AlmaLinux 9, Debian 13 and Ubuntu 26.04
Run the stable TeamSpeak 3 server as a systemd service on the RHEL 9 family, Debian 13 or Ubuntu 26.04, with licence, firewall and update steps, plus the TeamSpeak 6 beta.
This guide installs a self-hosted TeamSpeak server on AlmaLinux 9, Rocky Linux 9, CentOS Stream 9, Debian 13 or Ubuntu 26.04 (the steps are the same on Debian 12 and Ubuntu 24.04). You will run the stable TeamSpeak 3 server under its own account as a systemd service, accept the licence the way TeamSpeak documents, open the right ports and claim administrator rights with the privilege key. A final section shows how to try the TeamSpeak 6 server, which is still in beta. CentOS 6 reached end of life in November 2020 and cannot run current software safely.
Which TeamSpeak server to install
| TeamSpeak 3 server | TeamSpeak 6 server | |
|---|---|---|
| Status | Stable, version 3.13.9 on the official downloads page | Beta (v6.0.0-beta13.1, September 2026), not feature-complete |
| Free use | Without a licence key: 1 virtual server, 32 slots | Built-in 32-slot beta licence, renewed every two months |
| Larger licences | Available from TeamSpeak | Not available yet |
| Distribution | Archive from teamspeak.com, official teamspeak Docker image | GitHub releases, teamspeaksystems/teamspeak6-server Docker image |
TeamSpeak states that TeamSpeak 3 licences do not work with the TeamSpeak 6 server and that there is currently no migration path between the two. For a server people depend on, install TeamSpeak 3. The server is proprietary software: you may run it only under TeamSpeak's licence agreement, which you have to accept before it starts.
Requirements
- A 64-bit (x86-64) server with one of the systems above and a user with
sudorights. - A public IP address. The examples use
203.0.113.10. - The TeamSpeak client on your own computer to connect and claim admin rights.
Step 1: Install tools and create a service account
On AlmaLinux, Rocky Linux and CentOS Stream:
sudo dnf install -y curl tar bzip2On Debian and Ubuntu:
sudo apt update
sudo apt install -y curl ca-certificates tar bzip2Never run the server as root. Create a system account without a login shell:
sudo useradd --system --home-dir /opt/teamspeak --shell /usr/sbin/nologin teamspeakStep 2: Download and unpack the server
Take the current Linux 64-bit link from the official downloads page; at the time of writing it is version 3.13.9:
cd /tmp
curl -fLO https://files.teamspeak-services.com/releases/server/3.13.9/teamspeak3-server_linux_amd64-3.13.9.tar.bz2
sha256sum teamspeak3-server_linux_amd64-3.13.9.tar.bz2Compare the checksum with the SHA256 value shown next to the download on teamspeak.com. If it matches, unpack the archive into /opt/teamspeak and hand the directory to the service account:
sudo mkdir -p /opt/teamspeak
sudo tar -xjf teamspeak3-server_linux_amd64-3.13.9.tar.bz2 -C /opt/teamspeak --strip-components=1
sudo chown -R teamspeak:teamspeak /opt/teamspeakStep 3: Read and accept the licence
The server refuses to start until you accept the licence agreement. Read it first; the text ships with the server:
less /opt/teamspeak/LICENSETeamSpeak documents three ways to accept it. Use one:
- create an empty file named
.ts3server_license_acceptedin the server's working directory; - start the server with the parameter
license_accepted=1; - set the environment variable
TS3SERVER_LICENSE=accept(the valueviewprints the licence instead).
The marker file survives updates of the unit file, so this guide uses it:
sudo -u teamspeak touch /opt/teamspeak/.ts3server_license_acceptedStep 4: Create the systemd service
sudo nano /etc/systemd/system/teamspeak.service[Unit]
Description=TeamSpeak 3 server
After=network-online.target
Wants=network-online.target
[Service]
User=teamspeak
Group=teamspeak
WorkingDirectory=/opt/teamspeak
Environment=LD_LIBRARY_PATH=/opt/teamspeak
ExecStart=/opt/teamspeak/ts3server
Restart=on-failure
RestartSec=10
[Install]
WantedBy=multi-user.targetLD_LIBRARY_PATH lets the binary find the database and SSH libraries that ship in the same directory. Start the server and enable it at boot:
sudo systemctl daemon-reload
sudo systemctl enable --now teamspeak
systemctl status teamspeakStep 5: Save the admin credentials
On its very first start the server creates its database and prints two things exactly once: the password of the serveradmin ServerQuery account and a ServerAdmin privilege key (a line starting with token=). With systemd they land in the journal:
sudo journalctl -u teamspeak --no-pager | grep -iE "loginname|token="Store both in a password manager. The privilege key is also written to the server log:
sudo grep -rh "token=" /opt/teamspeak/logs/Step 6: Open the firewall
| Port | Purpose | Open to the internet? |
|---|---|---|
| 9987/udp | Voice | Yes |
| 30033/tcp | File transfer (avatars, icons, channel files) | Yes |
| 10011/tcp | ServerQuery, raw and unencrypted | No |
| 10022/tcp | ServerQuery over SSH | Only for your own address, if you need it |
With firewalld on the RHEL family:
sudo firewall-cmd --permanent --add-port=9987/udp
sudo firewall-cmd --permanent --add-port=30033/tcp
sudo firewall-cmd --reloadWith ufw on Debian or Ubuntu:
sudo ufw allow 9987/udp
sudo ufw allow 30033/tcpServerQuery gives full control over the server. Use it locally over an SSH session to the machine rather than exposing it.
Step 7: Connect and claim admin rights
Open the TeamSpeak client, connect to 203.0.113.10 (the default port 9987 needs no suffix) and paste the privilege key when the client asks for it, or enter it later through the client's "use privilege key" menu item. Your identity is now in the Server Admin group and the key is used up. From the client you can rename the server, set a password, and create channels and groups.
Updating and backups
An update replaces the program files and keeps your data. Stop the service, back up the directory, unpack the new release over the old one and start again:
sudo systemctl stop teamspeak
sudo tar -czf /root/teamspeak-backup-$(date +%F).tar.gz -C /opt teamspeak
cd /tmp
curl -fLO https://files.teamspeak-services.com/releases/server/NEW_VERSION/teamspeak3-server_linux_amd64-NEW_VERSION.tar.bz2
sudo tar -xjf teamspeak3-server_linux_amd64-NEW_VERSION.tar.bz2 -C /opt/teamspeak --strip-components=1
sudo chown -R teamspeak:teamspeak /opt/teamspeak
sudo systemctl start teamspeakReplace NEW_VERSION with the version number from the downloads page and verify the checksum as before. The state that matters is the SQLite database ts3server.sqlitedb, the files/ directory and, if you bought one, licensekey.dat; the backup archive above contains all of them.
Troubleshooting
- The service exits immediately with a licence message: the marker file is missing or in the wrong place. It must be in
/opt/teamspeak, the unit'sWorkingDirectory. - Status
203/EXECon AlmaLinux or Rocky Linux: SELinux blocked systemd from executing the binary. Confirm withsudo ausearch -m avc -ts recent, then runsudo semanage fcontext -a -t bin_t '/opt/teamspeak/ts3server'andsudo restorecon -v /opt/teamspeak/ts3server(semanageis inpolicycoreutils-python-utils). - Clients time out: check that 9987 is open as UDP, not TCP, on the host firewall and on any firewall in your provider's control panel.
sudo ss -ulnp | grep 9987shows whether the server is listening. - Voice works but avatars and file uploads fail: 30033/tcp is closed.
Trying the TeamSpeak 6 server beta
TeamSpeak publishes the TeamSpeak 6 server on GitHub and labels it a beta for testing and feedback. It is a separate program with its own data, uses the same default ports (9987/udp for voice, 30033/tcp for file transfer), and therefore cannot run next to a TeamSpeak 3 server on the same ports. Use a different machine or stop the TeamSpeak 3 service first.
TeamSpeak recommends Docker for it. With Docker installed:
docker run -d \
--name teamspeak-server \
-p 9987:9987/udp \
-p 30033:30033 \
-e TSSERVER_LICENSE_ACCEPTED=accept \
-v teamspeak-data:/var/tsserver/ \
teamspeaksystems/teamspeak6-server:latest
docker logs -f teamspeak-serverSetting TSSERVER_LICENSE_ACCEPTED=accept declares that you have read and accepted the server licence agreement. The log shows the ServerAdmin privilege key on first start. Without Docker, download teamspeak6-server-linux-amd64.tar.xz (or the arm64 build) from the project's releases page, unpack it, and run the binary as an unprivileged user:
chmod +x tsserver
./tsserver --accept-licensePersistent settings go in a tsserver.yaml file; ./tsserver --write-config-file generates one with the defaults and ./tsserver --help lists every option. The project README and its CONFIG.md are the reference while the beta changes.
Frequently asked questions
How many people can use a server without a licence?
A TeamSpeak 3 server without a licence key runs one virtual server with 32 slots. For more slots or more virtual servers you buy a licence from TeamSpeak and place the licensekey.dat file you receive in the server directory, then restart the service. The TeamSpeak 6 beta has a fixed 32-slot beta licence and no way to extend it yet.
I lost the privilege key. How do I become admin?
If the key was never used, it is still in the first log file under /opt/teamspeak/logs/. If it was used or the logs are gone, log in to ServerQuery as serveradmin and create a new key for the Server Admin group. If the ServerQuery password is lost as well, the server accepts a serveradmin_password= start parameter that sets a new one; add it to ExecStart for a single start and remove it afterwards.
Can TeamSpeak 3 clients connect to a TeamSpeak 6 server, or the other way round?
The TeamSpeak 6 client can connect to TeamSpeak 3 servers, which is one more reason the stable server remains a safe choice. Check TeamSpeak's own announcements for the current state of client compatibility with the TeamSpeak 6 server, because it changes between beta releases.
Should I use the official Docker image instead?
It is a supported alternative for TeamSpeak 3: the official teamspeak image takes TS3SERVER_LICENSE=accept as an environment variable and needs the same ports published. The native install in this guide has fewer moving parts on a server that runs nothing else in containers.