Teeworlds Server Port Forwarding
Teeworlds uses a single port for all traffic — game data, server browser registration, and RCON all share UDP 8303. No TCP port is required.
Required Port
| Port | Protocol | Purpose |
|---|---|---|
| 8303 | UDP | All game traffic, server browser, RCON |
Only one port, only UDP.
Changing the Default Port
Set a different port in autoexec.cfg:
sv_port 8304
Forward whichever port you choose; the setting and the forwarding rule must match.
Opening the Port with UFW (Ubuntu/Debian)
sudo ufw allow 8303/udp
sudo ufw reload
sudo ufw status
8303/udp should show ALLOW.
Opening the Port with firewalld (CentOS/RHEL/Fedora)
sudo firewall-cmd --permanent --add-port=8303/udp
sudo firewall-cmd --reload
Windows Firewall (PowerShell)
New-NetFirewallRule -DisplayName "Teeworlds Server" -Direction Inbound -Protocol UDP -LocalPort 8303 -Action Allow
Router Port Forwarding
If hosting at home, forward the port on your router:
- Log into your router admin panel (usually
192.168.1.1) - Navigate to Port Forwarding or Virtual Servers
- Add a rule: UDP 8303 → your server's local IP
Cloud / VPS Provider Firewall
Providers like AWS, DigitalOcean, Hetzner, and Vultr have an additional cloud-level firewall (security groups or cloud firewalls) separate from the OS. Make sure UDP 8303 is allowed there as well.
Multiple Servers on One Machine
Each instance needs its own port. Assign a unique port to each config:
| Instance | Config file | Port |
|---|---|---|
| Server 1 | autoexec.cfg |
8303 |
| Server 2 | dm_server.cfg |
8304 |
| Server 3 | ctf_server.cfg |
8305 |
Open each port in the firewall and start each instance with -f:
./teeworlds_srv -f dm_server.cfg &
./teeworlds_srv -f ctf_server.cfg &
Testing the Port
From an external machine:
nmap -sU -p 8303 YOUR_SERVER_IP
If the port is open you'll see 8303/udp open.
