How to Make a Team Fortress 2 Server with SteamCMD

Requirements and backup

Prepare a dedicated system account, SteamCMD, firewall access and a fixed private address when self-hosting. If replacing an instance, stop srcds and back up tf/cfg, custom maps, tf/addons, ban lists and launch scripts.

Create a GSLT for AppID 440 and treat it as a password. The TF2 GSLT and server.cfg guide covers creation and rotation.

Install and start srcds

1. Install SteamCMD.
2. Select the server directory and run app_update 232250 validate, using anonymous login while Valve supports it.
3. On Windows run srcds.exe -console -game tf +map cp_badlands +maxplayers 24.
4. On Linux use ./srcds_run -game tf +map cp_badlands +maxplayers 24 from the server directory.
5. Add +sv_setsteamaccount YOUR_GSLT from secret storage and -port 27015 when explicitly fixing the port.

The first launch should leave a stable console on the official map. Do not install SourceMod, MetaMod or FastDL until a player can join.

Configure network and server

Put persistent settings in tf/cfg/server.cfg. Start with hostname, required passwords, player count and essential rules. Do not expose RCON without network restrictions; use a secret different from the GSLT and join password.

The common game port is 27015. Allow the selected port through the firewall and forward it to the correct machine behind a router. Multiple instances need distinct ports. Test on the LAN and then externally; public discovery and direct IP are separate checks.

Validate and maintain

Join with connect IP:PORT, select a team, complete a round and change map. Restart and verify name, rules, bans and GSLT. Preserve the vanilla console log as a baseline.

Before updates: stop gracefully, back up, run app_update 232250 validate, test vanilla, then restore plugins. If joins fail, check process, map and build before firewall changes; do not open a large port range at random.

For managed systems and networking, compare Team Fortress 2 hosts.

Quick questions

Does the machine need the TF2 client? No. SteamCMD installs the separate dedicated-server application through AppID 232250.

Why test an official map first? It removes custom-map downloads and FastDL from the diagnosis, leaving the process, network and Steam authentication.

What should be backed up first? Preserve tf/cfg, bans, custom content, addons and launch parameters after a clean stop; test that the archive can be restored.