How to Set Up a Left 4 Dead 2 Dedicated Server
Run your own Left 4 Dead 2 dedicated server at home or rent one: what each route really involves, why location matters for 4v4 Versus, the correct SteamCMD install, a starter server.cfg explained line by line, ports and how your group joins.
The dedicated server for Left 4 Dead 2 is SteamCMD app 222860. App 222840 is for the original Left 4 Dead and is a common mistake.
If no map is loaded, the server does not answer queries properly and may not appear at all. Add +map from the start.
With 4v4 teams, uneven latency is much easier to feel in pounces, clears, shoves and tank play. A UK or London location keeps a UK and nearby European group on more similar footing.
By default, players are expected to come through a lobby. Set sv_allow_lobby_connect_only 0 if you want console connect IP:port to work.
Should you self-host or rent?
For Left 4 Dead 2, the real choice is not “can it start” but “what do you want to manage every week”. Self-hosting means your own PC and line become the service: you handle port forwarding, any ISP quirks, every game update, and the security of your RCON password. Renting removes most of that admin friction and gives you a fixed address, a control panel and a location choice, but it also means paying for convenience and for a machine that stays online whether you are there or not.
The table below is the honest version of that trade-off. Focus on the parts that affect server availability and fairness, not just the initial setup.
| Self-hosted at home | Rented server | |
|---|---|---|
| Runs without any player’s PC switched on | No | Yes |
| Works if your ISP uses CGNAT | No | Yes |
| No router or port forwarding work | No | Yes |
| Pick the server location, e.g. London | No | Yes |
| No monthly bill | Yes | No |
| Leaves your home upload free | No | Yes |
| Point | Self-hosted at home | Rented server | Why it matters |
|---|---|---|---|
| Address and uptime | Your home line, your PC, your router | Fixed server address, always on | If the host machine sleeps, reboots or leaves the game closed, nobody plays. A rented server exists independently of any player’s PC. |
| Port forwarding | You must open and test ports on your own router | Usually already handled in the service | SRCDS needs traffic to reach it from the internet. If the route stops at your router, the server can be alive locally and invisible to everyone else. |
| CGNAT risk | Can make hosting impossible | Not your problem | If your ISP uses carrier-grade NAT, you may not have a true public address to forward to, so no amount of local tweaking fixes reachability. |
| Upload bandwidth | Comes from your residential line | Handled by datacentre networking | L4D2 is not a huge persistent world, but it still needs steady upstream traffic for every connected player. Home upload is often the first hard limit, not RAM. |
| Updates after patches | You must stop the server and run app_update again | Still needed, but easier from a panel or managed environment | After a game update, players cannot join until the dedicated server matches it. This is one of the most common “it worked yesterday” failures. |
| Location choice | Where your house is | You choose a region, commonly including London | For Versus, equal travel time to the server matters more than raw hardware. Better location often improves fairness more than adding resources. |
| RCON security | You secure it yourself | You still secure it, but the server is not your whole home PC | RCON uses TCP on the game port and gives admin control. A weak rcon_password is a real risk because it is an exposed remote control path. |
Hardware is rarely the problem. Valve’s own baseline for a Source dedicated server is modest, and L4D2 server operators work on roughly one CPU core and 1 GB of RAM per server instance on a modern processor. Per-core speed matters more than core count, because the match runs on one main thread. SourceMod plugins, custom campaigns and multislot setups push memory up, but none of this needs a powerful machine. What decides whether self-hosting works is your connection, not your PC.
If you are weighing providers rather than self-hosting, our Left 4 Dead 2 server hosting comparison is the sensible place to compare locations and control options after you decide what you actually need.
For this game, the practical questions are location, easy updating, straightforward file access for cfg and addons, and a server that stays online without one player acting as host. If you already know self-hosting is more hassle than you want, compare on that basis rather than generic marketing.
Compare the best Left 4 Dead 2 server hostsWhy location matters so much in Versus
Coop can hide a lot of network roughness because everyone is fighting the AI together. Versus cannot. It is 8 players split into two teams, and the moments that decide rounds are short, contested interactions: pounces, skeets, deadstops, shoves, clears, smoker pulls and tank movement. Source lag compensation helps, but it does not erase distance. It mainly tries to reconcile what the attacker saw with what the server knows happened.
That is why one far-away player, or one far-away server, can make fights feel unfair rather than merely delayed. If the server sits well outside the centre of your group, the game spends more time smoothing disagreement between what different clients think just happened. The result is not just “lag”; it is arguments over hits, timing and control that felt clean on one screen and wrong on another.
For a UK group, a London or wider UK location usually makes the most sense because it keeps travel paths short and broadly similar for players in the UK and nearby Europe. The aim is not a magic latency number. The aim is that both teams are playing on roughly comparable delay, so special infected timing and tank control are decided more by play than by geography.
Install the correct dedicated server on Windows or Linux
The dedicated server you want is SteamCMD app 222860. A lot of old guides still point people at 222840, which is the original Left 4 Dead dedicated server, not Left 4 Dead 2. The game client itself is app 550, which is another easy source of confusion. If the app ID is wrong, everything after that becomes wasted effort.
One important SteamCMD detail: force_install_dir must come before login. If you put it after login, files may land in the wrong place or the update step may not target the directory you expect.
steamcmd +force_install_dir /home/steam/l4d2 +login anonymous +app_update 222860 validate +quit
On Windows the same line works from the SteamCMD folder, with a Windows path:
steamcmd.exe +force_install_dir C:\l4d2server +login anonymous +app_update 222860 validate +quit
Linux notes that matter
L4D2 runs as a 32-bit Source server, so a 64-bit Debian or Ubuntu host commonly needs the i386 compatibility packages. Run the server as its own non-root user, such as steam. That limits the damage if you make a mistake with scripts or admin tools, and it keeps game files separated from the rest of the system.
dpkg --add-architecture i386 apt-get update apt-get install libc6:i386 lib32z1 screen adduser steam
The dedicated user matters for more than tidiness. Game servers are network-facing processes by design. Running SRCDS as root gives it more access than it needs, which is poor practice for something that accepts remote traffic and admin commands.
Windows notes that matter
On Windows, the process is the same in principle: install SteamCMD, choose the install directory first, log in anonymously, then update app 222860. The main difference is where you store the files and how you keep the process running when you log out of the machine. If this is your own gaming PC, remember that server uptime still depends on that PC being switched on and not interrupted by restarts or game sessions.
If a Linux install comes down incomplete, SteamCMD’s documented @sSteamCmdForcePlatformType setting can help. Install once with the platform forced to Windows, then again with Linux, both using app_update 222860 validate:
./steamcmd.sh +force_install_dir /home/steam/l4d2 +login anonymous +@sSteamCmdForcePlatformType windows +app_update 222860 validate +quit ./steamcmd.sh +force_install_dir /home/steam/l4d2 +login anonymous +@sSteamCmdForcePlatformType linux +app_update 222860 validate +quit
Run the server inside screen so it keeps going after you close your SSH session.
Launch the server properly: every part of the command explained
SRCDS for L4D2 is not complicated to launch, but two details cause a lot of false troubleshooting: using the wrong game folder and forgetting to load a map. If no map is active, the server does not answer queries properly and may not appear in the server browser or respond as expected. So always include +map.
./srcds_run -game left4dead2 -port 27015 +map c1m1_hotel srcds.exe -console -game left4dead2 -port 27015 +map c1m1_hotel
- -game left4dead2: tells SRCDS which game content and ruleset to load. Without this, you are not starting the L4D2 server you think you are.
- -port 27015: binds the game server to the default SRCDS port. This is the port you forward through your router and the one players usually connect to.
- +map c1m1_hotel: loads the first map of Dead Center and makes the server actually become queryable and joinable.
- -console on Windows: opens the SRCDS console so you can see errors and enter commands directly.
If the host has more than one address, +ip can bind the server to a specific one. That matters on boxes with multiple interfaces or unusual routing. On a normal home setup, you usually leave this alone unless the server is binding to the wrong local address.
Do not waste time on -tickrate for stock L4D2. It is disabled, so the game runs at its fixed default unless a plugin changes it. People often add the flag because it works in other Source games, then assume they have tuned the server when they have not changed anything at all.
Also keep sv_lan 1 for actual LAN-only use. It disables the public heartbeat and Steam authentication path, so it is the wrong setting for an internet server even if everything else looks right.
A starter server.cfg that makes sense
Your main config is left4dead2/cfg/server.cfg. It runs on map load, which means it is the right place for your name, passwords, lobby behaviour and steady server rules. You can also split settings into separate files and call them with exec <file> if you want one config for Coop and another for Versus.
// Basic identity hostname "My Left 4 Dead 2 Dedicated Server" // Join password: leave empty for public, set one for private groups sv_password "" // RCON password: make this long and unique rcon_password "CHANGE_THIS_TO_A_LONG_UNIQUE_PASSWORD" // Allow direct console joins as well as lobby-based joins sv_allow_lobby_connect_only 0 // Optional Steam group integration sv_steamgroup "" sv_steamgroup_exclusive 0 // Optional lobby search key for sending a lobby to this server sv_search_key "" // Basic game rules z_difficulty "Normal" sv_alltalk 0 // Discovery and housekeeping sv_tags "l4d2,coop,versus,uk" sv_consistency 1 motd_enabled 1 sv_visiblemaxplayers -1 sv_vote_kick_ban_duration 5
What each setting is actually doing
- hostname: purely identification, but it matters in practice because players use it to confirm they have reached the right box. Clear naming reduces “wrong server” confusion when friends have several favourites saved.
- sv_password: gate for joining. This costs almost nothing in server resources because it is just access control, but the trade-off is admin overhead: you must distribute it and change it if it leaks.
- rcon_password: remote console control. Keep it strong and unique because RCON is powerful and exposed over TCP on the game port. A weak password is not a gameplay inconvenience; it is a security problem.
- sv_allow_lobby_connect_only 0: the default is 1, which means players may only arrive via matchmaking lobby. Setting 0 allows
connect IP:port. Use this if you want simple direct joins or if you troubleshoot by bypassing the lobby. The trade-off is that your server becomes easier to reach directly, so your access controls need to be intentional. - sv_steamgroup and sv_steamgroup_exclusive: useful if your group already organises through Steam groups. The group ID is shown on the group’s admin profile page in the Steam Community. With exclusive set to 1, only group members can join while the server is empty; once populated, public players can still get in. That is good for community seeding, but not a true private lock.
- sv_search_key: when a lobby searches for a dedicated server, this restricts the search to servers with the same key. It makes lobby-to-server matching predictable, which cuts down on “we started a dedicated game and landed somewhere else”.
- z_difficulty: affects infected pressure in Coop-style modes. Harder settings do not cost much in hardware by themselves, but they change how punishing the session feels, so set it deliberately.
- sv_alltalk: with 0, teams stay separated in modes where that matters. In Versus, that preserves team communication and stops dead players feeding information freely. Turning it on is a social choice, not a performance tweak.
- sv_tags: helps identify the server’s purpose, such as mode or region. This is about discoverability and expectation-setting rather than resources.
To switch into Versus, use the map command with the mode at the end, for example map c5m5_bridge versus. That works because L4D2 changes mode as part of loading the map, rather than relying on a disconnected menu setting. If lobby-based mode selection behaves oddly, check that your launch-time sv_gametypes allows the mode you want.
Ports to forward, and why each one exists
The main port is simple: forward 27015 UDP and TCP to the machine running SRCDS. Valve lists 27015 as the port for game traffic, server queries and RCON, and RCON runs over TCP. If you change -port on launch, forward the new port instead.
- 27015 UDP: gameplay traffic and server queries.
- 27015 TCP: RCON, the remote admin console.
- 27020 UDP: only if you use SourceTV with
+tv_port. - 27005 UDP and 26900 UDP: client and Steam outgoing traffic. These normally do not need forwarding because they are outbound.
If players on your own LAN can connect but friends on the internet cannot, this is usually the first place to look. The server process can be healthy and still be unreachable because the router is not passing incoming traffic through to it.
CGNAT is the exception that catches people out. If your broadband or mobile provider puts you behind carrier-grade NAT, you may have no real public address to forward from. In that case, the problem is not your SRCDS config at all; the internet simply cannot open a path back to your machine in the usual way.
How players actually join: direct connect, lobby forcing, public and private setups
There are two practical ways in: direct console connect, or a lobby that is pointed at your dedicated server. Direct connect is the simpler diagnostic path because it removes matchmaking from the equation, but it only works if sv_allow_lobby_connect_only is set to 0.
connect IP:27015 mm_dedicated_force_servers 203.0.113.10:27015
For direct join, players enable the developer console in the game options, press ~, then use connect IP:27015. This is the cleanest method for a private regular group because it talks straight to the server and immediately shows whether the network path is working.
For lobby-based joining, the lobby leader sets mm_dedicated_force_servers to the server address, then starts the lobby game with dedicated server chosen. This is useful if your group prefers the game’s lobby flow, but it adds one more moving part: the lobby has to match the right server and the right mode.
Three sensible access patterns
- Private direct-connect server: set
sv_password, keepsv_allow_lobby_connect_only 0, share the address privately. Best for a fixed group that just wants to get in and play. - Private lobby-led server: use
sv_search_keyor force the server withmm_dedicated_force_servers. Good if your group always assembles in lobby first. - Community server with group preference: set
sv_steamgroup, and optionallysv_steamgroup_exclusive 1if you want members to have first shot while the server is empty.
Public visibility is not the same as good access control. If you truly want a private server, use a join password and do not rely on tags or group settings alone.
Keeping it running: updates, hibernation, backups, and when tuning is enough
Left 4 Dead 2 has no persistent world save to protect, which makes maintenance easier than in survival sandboxes. Your important assets are the cfg folder, any addons such as SourceMod or custom campaigns, and the launch line you use to start the server. Back those up. If the server machine dies, you can rebuild the instance quickly as long as those pieces are preserved.
After every game patch, stop the server and run app_update 222860 validate again. This is not optional if clients have already updated. Mismatched versions are a hard join blocker, so the symptom looks like a network failure even though the route is fine.
Leave sv_hibernate_when_empty at its default of 1 unless you have a specific reason not to. Hibernation drops CPU use when nobody is connected, which is sensible because the server’s main thread does not need to simulate a live match for an empty box. The trade-off is simply that the server wakes up when needed rather than burning cycles continuously.
| Situation | Tune first | Why this is the first move | When renting or relocating helps more |
|---|---|---|---|
| Friends cannot join right after a patch | Update app 222860 again | This is usually a version mismatch, not a lack of hardware. | It does not. This is a maintenance task either way. |
| Coop feels fine, but 8-player Versus feels inconsistent for most of the group | Check server location and who is far away | Versus fairness depends heavily on network path equality. Extra RAM does not fix geography. | A rented London or UK node often helps because it places the server nearer the middle of the group. |
| Problems start after adding plugins or custom campaigns | Trim or separate addons | Addons can add CPU work on the main thread, more memory use, and extra disk reads on map load. | If you need a heavily modded setup to stay available all the time, a stronger plan is easier to manage. |
| The server works, but only while one player keeps a PC running | Decide if that is acceptable admin burden | This is an uptime problem, not a config problem. | Renting helps because the server is independent of any player’s home machine. |
| Only one player complains, everyone else is fine | Check that player’s route and location first | If the rest of the group is stable, the bottleneck is unlikely to be server memory or CPU. | Relocating the server only makes sense if several players are disadvantaged in the same direction. |
Troubleshooting when people cannot connect
Work from the outside in. First confirm the server is running on a map, then confirm the right port is open, then confirm your join method matches your cvars. Most L4D2 dedicated server problems come from one of those three layers, not from obscure engine behaviour.
| Symptom | Likely cause | First fix |
|---|---|---|
| Server does not appear or answer queries | No map loaded, or wrong launch line | Restart with -game left4dead2 and a real +map. |
| Friends on the internet cannot join, but LAN clients can | Port forwarding missing or wrong machine targeted | Forward 27015 UDP and TCP to the SRCDS host and confirm the host’s local address. |
| No one outside your home can ever reach it despite correct router rules | CGNAT on the ISP connection | Check whether you actually have a public address; if not, self-hosting may not be possible on that line. |
connect IP:27015 fails, but the server itself is running | sv_allow_lobby_connect_only left at default 1 | Set it to 0 in server.cfg and load the map again. |
| Lobby starts, but does not use your dedicated server | No matching search key, wrong forced address, or mode mismatch | Recheck mm_dedicated_force_servers, sv_search_key, and that the desired mode is allowed. |
| Players cannot join after a game update | Dedicated server version is behind the clients | Stop SRCDS and run app_update 222860 validate again. |
| RCON is refused or flaky | Wrong password, weak password changed, or TCP path not reaching the server | Set a fresh strong rcon_password and confirm 27015 TCP is open to the server. |
| The install looks wrong for L4D2 | Used app 222840 instead of 222860 | Reinstall the correct dedicated server app. |
In the server console, status is your friend. It tells you the active map and current connections, which helps separate “nobody can reach it” from “they are joining a different server” or “the process is up but not actually on a playable map”.
Left 4 Dead 2 server FAQ
Can I host a Left 4 Dead 2 dedicated server for free?
Yes, in the sense that the dedicated server software itself is available through SteamCMD with anonymous login. The real cost is your own hardware, power, connection quality and time spent keeping it updated and reachable. Free works best when your line supports port forwarding and your group accepts that the server depends on one home machine staying on.
Which port does a Left 4 Dead 2 server use?
By default, it uses 27015, and for internet hosting you should forward both UDP and TCP on that port to the server machine. UDP carries the game traffic, while TCP also matters because RCON uses it. 27020 UDP is only needed if you use SourceTV.
How do I make my Left 4 Dead 2 server private?
The simplest method is to set sv_password in server.cfg and only share the address with your group. If you want players to join by console as well, keep sv_allow_lobby_connect_only 0. Steam group settings are useful for community preference, but they are not a full privacy control on their own.
Can more than 8 players join a Versus server?
Stock L4D2 Versus is 8 players, split 4v4. More than that needs SourceMod multislot plugins, which turns the server into a modded setup with more moving parts and usually more CPU and memory overhead. For a regular private group, staying within the game’s intended player counts is usually the cleaner choice.
Why can’t my friends join after a game update?
Because the client and dedicated server versions must match. When the game updates, stop the server and run app_update 222860 validate again before reopening it. This is one of the most common causes of sudden join failure on otherwise unchanged servers.
More Left 4 Dead 2 server help
Compare UK Left 4 Dead 2 hosts with London locations.
Written for the current Steam version of Left 4 Dead 2. The IP address 203.0.113.10 and the passwords in the examples are placeholders. On a rented server, the same settings usually sit in the host’s panel or in server.cfg in the file manager.
