Skip to main content

​
General Questions

The TeamSpeak 6 Server is lightweight and can run on minimal hardware:
  • CPU: 1 core (2+ recommended for larger servers)
  • RAM: 512 MB minimum (1 GB+ recommended)
  • Storage: 100 MB for application, plus space for database and logs
  • OS: Linux, Windows, or via Docker
Requirements scale with the number of concurrent users.
Docker is recommended for most users because:
  • Simplified setup and maintenance
  • Isolated environment prevents conflicts
  • Easy updates with new image versions
  • Better portability across systems
Use binary installation if you:
  • Need maximum performance control
  • Have specific system integration requirements
  • Prefer direct system-level management
SQLite (default):
  • No separate database server required
  • Simpler setup
  • Best for small to medium servers (<50 users)
  • File-based database
MariaDB:
  • Requires separate database server
  • Better performance at scale
  • Recommended for large deployments (>50 users)
  • More complex setup and maintenance
See Database Configuration for setup details.

​
Installation & Setup

The ServerAdmin key is displayed in the server logs during first startup:
# For Docker:
docker logs teamspeak-server

# For binary installation, check console output or logs
Look for a line containing ServerAdmin privilege key created followed by the key.
The key is only shown once. Save it immediately and store it securely.
For binary installation:
./tsserver --accept-license
For Docker:
docker run -d \
  -e TSSERVER_LICENSE_ACCEPTED=accept \
  teamspeaksystems/teamspeak6-server:latest
The license must be accepted for the server to start.
Yes! You need to configure different ports for each instance:Docker example:
# Server 1
docker run -d --name ts-server-1 \
  -p 9987:9987/udp -p 30033:30033 \
  teamspeak6-server:latest

# Server 2
docker run -d --name ts-server-2 \
  -p 9988:9987/udp -p 30034:30033 \
  teamspeak6-server:latest
Each instance needs separate data volumes and port mappings.

​
Configuration

  1. Command-Line Arguments - For temporary changes or scripting: 
    ./tsserver --default-voice-port 9987
  2. Environment Variables - Useful for Docker: 
    export TSSERVER_DEFAULT_VOICE_PORT=9987
  3. YAML Configuration File - Recommended for persistent configuration: 
    # Generate default config
./tsserver --write-config-file
Command-line arguments override environment variables, which override the config file.
Default location: tsserver.yaml in the same directory as the server binaryCustom location:
./tsserver --config-file /path/to/custom-config.yaml
For Docker: Mount your config file as a volume:
volumes:
  - ./tsserver.yaml:/var/tsserver/tsserver.yaml
Command-line:
./tsserver --default-voice-port 9988
Environment variable:
export TSSERVER_DEFAULT_VOICE_PORT=9988
Docker:
docker run -d \
  -p 9988:9988/udp \
  -e TSSERVER_DEFAULT_VOICE_PORT=9988 \
  teamspeak6-server:latest
Don’t forget to update your port forwarding and firewall rules.
Required ports:
  • 9987/UDP - Voice communication (can be customized)
  • 30033/TCP - File transfer (can be customized)
Optional ports:
  • 10080/TCP - Web Query API
See Ports & Networking for details.

​
Operations

What to backup:
  • Database file (SQLite) or database dump (MariaDB)
  • Server configuration files
  • File transfer storage directory
Docker volume backup:
# Create backup
docker run --rm \
  -v teamspeak-data:/data \
  -v $(pwd):/backup \
  alpine tar czf /backup/teamspeak-backup.tar.gz /data
See Backup & Restore for comprehensive backup strategies.
Docker (recommended):
docker pull teamspeaksystems/teamspeak6-server:latest
docker stop teamspeak-server
docker rm teamspeak-server
docker run -d --name teamspeak-server \
  -v teamspeak-data:/var/tsserver \
  teamspeaksystems/teamspeak6-server:latest
Your data persists in the volume.Binary installation:
  1. Download the new version
  2. Stop the server
  3. Replace the binary
  4. Start the server with the same configuration
See Updates for detailed instructions.
Docker:
# View logs
docker logs teamspeak-server

# Follow logs in real-time
docker logs -f teamspeak-server

# View last 100 lines
docker logs --tail 100 teamspeak-server
Binary installation: Logs are written to the console by default. You can redirect to a file:
./tsserver > server.log 2>&1
See Logging for log configuration options.
No, there is currently no migration path from TeamSpeak 3 to TeamSpeak 6.
  • TeamSpeak 3 Server licenses are not compatible with TeamSpeak 6
  • Database schemas are different
  • You must set up a new TeamSpeak 6 server
See Beta Information for current limitations.

​
Licensing

The TeamSpeak 6 Server beta includes a 32-slot license that is automatically renewed every two months throughout the beta period.
  • No manual renewal required
  • Valid during beta/evaluation phase
  • Cannot be upgraded to a larger license yet
See Licensing for more details.
Not currently. During the beta period:
  • All servers are limited to the 32-slot beta license
  • License upgrades are not yet available
  • Licensing and pricing will be finalized before stable release
If you need more slots, you can rent official servers at myteamspeak.com/communities.

​
Troubleshooting

Common causes:
  1. Firewall blocking connections
    • Open port 9987/UDP for voice
    • Open port 30033/TCP for file transfer
  2. Port forwarding not configured
    • Forward ports on your router to the server
  3. Wrong IP address
    • Use your public IP for external connections
    • Use 0.0.0.0 for server binding to accept all connections
  4. Server not running
    • Check with docker ps or process manager
See Troubleshooting for detailed solutions.
Reduce logging verbosity: Verbose logging increases resource usage. Use standard log levels for production.Check connection count: Ensure you’re not exceeding your intended capacity.Use MariaDB for large deployments: SQLite is simpler but MariaDB performs better with many concurrent users.Monitor for attacks: Check logs for unusual connection patterns.See Performance Tuning for optimization tips.
Community Forum: community.teamspeak.com/c/teamspeak-6-server/45GitHub Issues: github.com/teamspeak/teamspeak6-server/issuesOfficial Documentation: This documentation site and the CONFIG.md file included with the serverWhen asking for help, provide:
  • Server version and platform
  • Relevant log excerpts
  • Configuration details (redact sensitive info)
  • Steps to reproduce the issue

Build docs developers (and LLMs) love

Get started for freeTalk to us