Left 4 Dead 2 Server Troubleshooting
Fix common L4D2 dedicated server issues: server not in browser (missing GSLT), sv_consistency errors, players unable to connect, server crashes, and VAC security questions.
L4D2 Server Troubleshooting
Server Not Appearing in the Browser
Cause 1: Missing or invalid GSLT token
L4D2 requires a Game Server Login Token to be listed publicly. Without it, the server runs but is invisible to Steam's server browser.
Fix:
- Go to steamcommunity.com/dev/managegameservers
- Generate a token for App ID 222840
- Add to your launch command:
+sv_setsteamaccount YOUR_TOKEN - Restart the server
Cause 2: Firewall blocking UDP 27015
sudo ufw allow 27015/udp
sudo ufw allow 27015/tcp
sudo ufw reload
Also check your cloud provider's security group/firewall panel.
Cause 3: Server was just started
Steam's server browser can take up to 10 minutes to index a newly started server. Try a direct connection first to confirm the server is running:
Open console → connect YOUR_IP:27015
"sv_consistency" Error for Players
"Server is enforcing consistency for this file"
This happens when a player's files don't match what the server expects — usually caused by mismatched add-ons or workshop mods.
Quick fix for custom content servers:
Add to server.cfg:
sv_consistency 0
For players connecting to a vanilla server:
Ask the player to:
- Disable all Steam Workshop subscriptions for L4D2
- Verify game files: Steam → Right-click L4D2 → Properties → Local Files → Verify
- Remove any files from
Steam\steamapps\common\Left 4 Dead 2\left4dead2\addons\
Players Can't Connect
Check 1: Is the server actually running?
sudo systemctl status l4d2server
# or
ps aux | grep srcds
Check 2: Is UDP 27015 reachable?
nmap -sU -p 27015 YOUR_IP
Check 3: Correct port in connection URL?
Default is 27015. If you changed it, players must use IP:YOURPORT.
Server Crashes or Won't Start
Check logs:
journalctl -u l4d2server -n 50
# or
tail -50 /home/steam/l4d2-server/left4dead2/console.log
Common causes:
- Invalid GSLT token — token may have expired or been revoked. Regenerate at the Steam developer page.
- Invalid map name — the
+maplaunch parameter must match an existing map name exactly. - Corrupt server files — run
app_update 222860 validatevia SteamCMD to repair. - Disk space — L4D2 needs ~13 GB free. Check with
df -h.
VAC and sv_cheats Questions
Does using sv_cheats 1 get players VAC banned?
No. VAC only detects external cheat software (DLLs, trainers). Console commands and sv_cheats on your own server do not trigger VAC bans.
Does SourceMod trigger VAC bans?
No. SourceMod and MetaMod are server-side only and do not modify game client files.
My server shows as "Insecure" in the browser:
If you launched with -insecure instead of -secure, VAC is disabled. Relaunch with -secure to re-enable VAC and remove the insecure label.
Game Mode Resets After Map Change
This is a known L4D2 behavior — some cvars reset when changelevel is called. The reliable fix is a SourceMod plugin that re-applies mp_gamemode after every map transition.
With SourceMod installed:
// In cfg/sourcemod/core.cfg or a custom plugin
mp_gamemode "versus"
Or create left4dead2/cfg/server.cfg entries that auto-execute on map start by naming the file after the campaign (e.g., left4dead2/cfg/c1m1_hotel.cfg).