Shooter · Lightweight
Host a Left 4 Dead 2 Server
Run a Left 4 Dead 2 server with persistent configuration, Source-query readiness, private RCON actions, and TCP and UDP game access.
Left 4 Dead 2 uses a shared TCP/UDP Source-engine game port. Swarm Hosts stores persistent configuration under /server/left4dead2/cfg and waits for a Source-query response before marking the server ready.
- Server Actions
- Guided settings
- Backups
Validated public launch
Hardware and runtime
What Left 4 Dead 2 needs
Catalog minimums are a starting point. World size, player count, content, and game settings can require more resources.
- CPU
- 2+ cores
- Memory
- 2+ GiB
- Player traffic
- UDP
- Persistent backup scope
- 1 catalog-declared path
- Persistent configuration: /server/left4dead2/cfg
- Network: assigned UDP game/query port; RCON remains container-local
- Readiness: Source-query response
- Server Actions: private, authenticated Source RCON; no public RCON port
- Runtime compatibility: the pinned 32-bit Source binary needs its legacy socket syscall. Swarm Hosts applies Docker's pinned seccomp/v0.2.1 compatibility profile only to this non-root container; it does not disable seccomp, add capabilities, or publish RCON.
Launch workflow
From host to running server
Use Settings → Left 4 Dead 2 Settings for managed values after launch. Upload trusted addons or configuration through Files & Backups, and create a backup before replacing working files.
- Choose Left 4 Dead 2.
- Review the server parameters for map, maximum players, and mode.
- Set CPU and memory limits.
- Set a 16–128 character Server Actions password using letters, numbers, underscores, or hyphens.
- Launch and wait for the Source readiness check.
Networking
How players connect
Players can connect with the published host and assigned UDP port shown on the Swarm Server. Share that endpoint rather than the container's default port.
Managed shared relay when the game, host, and current relay path support it.
Catalog-backed Server Actions
Tools Swarm Hosts exposes for Left 4 Dead 2
Availability comes from the production catalog and verified game guide. Controls stay typed and bounded to the workflow the game supports.
Server status
Read the current map and player summary.
List players
Refresh the verified connected-player list.
List installed maps
Refresh maps installed in the pinned runtime.
List bans
Refresh identities currently banned by the Source server.
Broadcast message
Send a server-authored chat message.
Change map
Change immediately to a freshly verified installed map.
Kick player
Disconnect a freshly verified connected player.
Ban player
Ban and disconnect a freshly verified connected player, then persist the ban list.
Remove ban
Remove a freshly verified Source identity ban and persist the ban list.
Mods & Content status
Manifest Only
Left 4 Dead 2 addons are usually installed as VPKs or Workshop content. Track ids here, then manage files under the server data directory.
Addon ids may be tracked in Mods & Content, while VPK installation remains a file-management workflow. Back up the persisted cfg directory before changing server configuration, and validate readiness and client connectivity after each addon change.
See Server Actions for the availability matrix.
Know before launch
Current boundaries
- Production hosting supports Windows 10/11 or Linux with Docker Desktop in Linux-container mode on Windows, or Docker Engine or rootful Podman on Linux.
- Managed shared relay when the game, host, and current relay path support it.
- Allowed on public launch surfaces after focused Swarm Server validation.
Windows 10/11 + Linux
Ready to host Left 4 Dead 2?
Connect the Windows or Linux computer you already own, then follow the game-specific launch path.