How to Join a Left 4 Dead 2 Dedicated Server
Got an IP but can’t get your group onto it? This is how joining a Left 4 Dead 2 dedicated server really works: direct connect, favourites, forcing a lobby onto your server, why the invite button goes grey and why a fifth player gets locked out.
The server address is IP:port. The default game port is 27015. 27005 is your own client’s local port, not the server.
connect, favourites, the server browser and steam://connect all rely on the server allowing non-lobby joins with sv_allow_lobby_connect_only 0.
If the first player joins by IP or browser, there is no lobby behind that session, so the in-game invite button is greyed out.
For a group, choose one method and have everyone use it for that session. Mixing lobby and direct methods is what causes most “it worked yesterday” confusion.
What you need before you try to join
You need the server’s IP:port from the host panel or dashboard. On a rented server, that is where the game address is shown; some panels also give a hostname that works the same way. The default Left 4 Dead 2 game port is 27015, and L4D2 uses that same port for game traffic and server queries.
The common mistake is using 27005. That is the local client port of your own game, so it will never be the server address you hand to friends.
You also want the developer console enabled, because every reliable join method becomes easier once you can type commands directly.
- Open Options > Keyboard/Mouse.
- Set Allow Developer Console to Enabled.
- Open the console with the ~ key under Esc.
- If you prefer, the Steam launch option
-consoleopens it at start.
Pick one join route for the whole group
Before anyone starts clicking around, decide how this session will be joined. L4D2 has direct server joins and lobby-led joins, and they are not the same thing under the hood. Direct methods talk straight to the server. Lobby methods ask matchmaking to place that lobby onto a dedicated server, which then becomes reserved for it.
Rule for groups: pick one method for the whole group per session. If the first player direct-connects and the rest expect lobby invites, someone is going to hit a greyed-out invite button. If the leader starts a reserved lobby game and later tries to cram in extra people beyond the mode’s lobby limit, someone is going to be locked out.
| Join route | Needs lobby-only off | Invites work | Reserves server |
|---|---|---|---|
| Console connect | Yes | No | No |
| Favourites or server browser | Yes | No | No |
| steam://connect link | Yes | No | No |
| Forced lobby | No | Yes | Yes |
sv_allow_lobby_connect_only 0. A forced lobby uses mm_dedicated_force_servers.| Method | What you need | Works with invites? | Best for |
|---|---|---|---|
| Direct connect | IP:port, console, sv_allow_lobby_connect_only 0 | No in-game lobby invites | Known server address, quick manual joins, multi-slot servers using direct IP joins |
Favourites / server browser / steam://connect | IP:port, browser or Steam client, sv_allow_lobby_connect_only 0 | No in-game lobby invites | Repeat joins, easy rejoining, sending friends a joinable address |
| Lobby forced onto your server | Leader console, mm_dedicated_force_servers, Best Available Dedicated | Yes | Private group sessions where invites must keep working |
| Quick Match | Nothing beyond normal matchmaking | Yes | Public matchmaking, not targeting one known server |
Method 1: direct connect by IP
This is the most dependable route when you know the exact address. It skips matchmaking entirely and tells your game to connect straight to that server, which also makes it the quickest way to find out whether the server is reachable at all.
- Enable the console if you have not already.
- Open the console at the main menu.
- Type the server address and press Enter.
connect 203.0.113.10:27015
If it works, the menu gives way to the normal loading process and you arrive on that server. If nothing happens, or the connection is refused, the first thing to check is not your typing but the server setting sv_allow_lobby_connect_only.
That cvar defaults to 1, which means “only allow players to connect to your server from the matchmaking lobby”. With the default in place, direct joins such as connect, favourites and browser connects will fail because the server is refusing non-lobby entry points. The owner must set it to 0 for this method to work.
The trade-off is simple: direct connect gets you onto the box, but it does not create a lobby. That is why this method is good for manual joins and bad for anyone expecting the in-game invite system afterwards.
Method 2: favourites, server browser and steam://connect
These are different front ends for the same basic idea: join the server directly rather than through a lobby. Because of that, they also need sv_allow_lobby_connect_only 0.
Steam favourites
- In the Steam client, open View > Game Servers.
- Open the Favorites tab.
- Click + to add a server.
- Enter the server’s
IP:port. - Use Connect.
Once added, the server also appears in the in-game favourites. This is useful when your group joins the same box regularly, because it removes mistyped addresses from the equation.
In-game server browser
If you want the browser from inside L4D2, use the console command openserverbrowser. That opens the game’s server browser, which again is still a direct join path.
steam://connect
A steam://connect/IP:port link, such as one dropped into chat, launches the game and attempts the same sort of direct connection. It is handy for getting a whole group onto an unreserved server fast, but it does not solve the missing-lobby problem. If the group wants invites to stay active inside the game, use the lobby method instead.
Method 3: force a lobby onto your own server
This is the method to use when you want the session to behave like normal L4D2 matchmaking, but land on your own dedicated server instead of a random one. The key difference is that you are not joining the server first. You are creating a lobby first, then telling matchmaking which dedicated server to use when that lobby starts.
- The lobby leader goes to the main menu and opens the console.
- Enter the server address with
mm_dedicated_force_servers. - Create the lobby for the mode you want.
- Set server type to Best Available Dedicated.
- Invite friends into the lobby.
- Start the game.
mm_dedicated_force_servers 203.0.113.10:27015
If it works, starting the lobby puts that whole lobby on your server. The big advantage is obvious: invites keep working because the lobby still exists as the organising layer for the session.
For a private group, a search key is often cleaner than a traditional password. The server sets a key, and the lobby leader sets the same key locally before hosting a Best Available Dedicated lobby. Matchmaking then only picks a server with the matching key.
server: sv_search_key <key> client lobby leader: sv_search_key <same key>
This is not the same job as sv_allow_lobby_connect_only. A search key helps a lobby find the right server. sv_allow_lobby_connect_only 0 allows non-lobby join methods. Use the one that matches your route.
Why the invite button is greyed out
The in-game invite option is tied to lobbies, not to raw server sessions. If the first player gets into the server with connect, the Steam server browser or favourites, there is no lobby behind that game. L4D2 therefore has nowhere to send a lobby invite, so the button is disabled. In practice, a session that starts with a direct join behaves like a private game: nobody can be pulled in through the lobby system.
There are only two clean fixes:
- Keep it as a direct-join session. Everyone joins the same way:
connect IP:port, favourites, browser or asteam://connectlink. - Reset and use the lobby route. Everyone leaves, the leader runs
mm_dedicated_force_servers, creates a lobby with Best Available Dedicated, invites friends, then starts.
On some community servers, especially in versus setups, the admin may also need sb_all_bot_game 1 so the server keeps running with bots when a team is not full. That does not create invites by itself; it just stops the session from collapsing while players are still trying to get in.
Reserved vs unreserved: the state that explains most join limits
When a game is started from a lobby, the server becomes reserved for that lobby. When players join directly without a lobby, the server is unreserved. This is the single most useful distinction to understand, because it explains why one night friends can pile in and the next night nobody extra can join.
The server console shows the state in status output.
(reserved xxxxxxx) (unreserved)
| Server state | Lobby | Connect | Browser | Friends |
|---|---|---|---|---|
| Reserved, not full | Yes | Yes | Yes | Yes |
| Reserved and full for the mode (4 in co-op, 8 in versus) | No | No | No | No |
| Unreserved | No | Yes | Yes | Yes |
status in the server console: it shows (reserved xxxxxxx) or (unreserved).- Reserved and not full: lobby and Quick Match players can join, and direct join methods can also work.
- Reserved and full for the mode: nobody else can join by any method, even if the server itself has more slots available.
- Unreserved: Quick Match and lobby matchmaking will not send players there, but direct joins, friend joins and the server browser work.
The important cap is the lobby cap, not the server slot count. In vanilla co-op, a Steam lobby caps co-op at 4 humans. In versus and scavenge, a reserved lobby game caps at 8. If you want more than 4 humans in co-op, that needs server-side plugins such as SourceMod with L4DToolZ and a multi-slot plugin, and those extra players join by direct IP methods rather than through the standard lobby path.
That is also why “it worked yesterday” happens. Yesterday, someone may have direct-connected first and created an unreserved session. Today, the leader may have started from a lobby, which reserved the server, and once the mode hit its lobby limit, every other join path stopped working.
Passwords and private servers
If a password prompt appears and rejects the right password, the problem may be the server’s built-in sv_password. In Left 4 Dead 2 it is widely reported as unreliable: the prompt can appear, the correct password can still be rejected, and some admins avoid it entirely because it can interfere with Steam registration.
That is why many private servers leave sv_password empty and use one of these instead:
- A whitelist plugin so only approved users can get in.
- A plugin password with the exact command supplied by the admin.
sv_search_keyfor private lobby-led groups.
Steam group settings are not a dependable replacement. A server can use sv_steamgroup and sv_steamgroup_exclusive 1, but that exclusivity is widely reported not to stop direct connects. If the owner wants controlled access, search keys, whitelists or a plugin password are the safer choices.
Other things that stop a join
Once the lobby/direct-connect side is understood, the remaining join failures are usually simpler.
- Game updated but server not: clients cannot join until the server is updated.
- Custom campaign or addon missing: if the server is on a custom map, you need the same Workshop item installed on your client.
sv_pureorsv_consistencykick: modified client files can make the server reject you, so remove mods that change core files.- Server hidden from lobby searches: if the server uses
sv_region 255, it will not appear to lobby searches, though direct connect can still work. - Home-hosted server only works on the local network: port
27015UDP and TCP must be forwarded, and if the connection is behind CGNAT it cannot work from outside.
If the problem is on a home-hosted box rather than a rental panel, our Left 4 Dead 2 dedicated server setup guide covers the server-side steps.
Still can’t get in? Match the symptom to the cause
Start from what you actually see, then work back to the mechanism behind it. That is much quicker than toggling random settings.
| What you see | Likely cause | Fix |
|---|---|---|
connect does nothing or gets refused | Wrong address, often 27005, or sv_allow_lobby_connect_only 1 | Use the panel’s IP:port, usually 27015, and ask the owner to set sv_allow_lobby_connect_only 0 for direct joins |
| Invite button is greyed out | First player direct-connected, so there is no lobby | Have everyone join directly as well, or leave and restart as a forced dedicated lobby |
| Lobby lands on a random server | mm_dedicated_force_servers was not used correctly, or the wrong server type was chosen | Enter the command at the main menu, create a new lobby, set Best Available Dedicated, then start again |
| Friends cannot get in once four are playing | Reserved co-op lobby is full for the mode | That cap is normal for a lobby-led vanilla co-op session; extra humans need server-side multi-slot support and direct joins |
| Password prompt rejects the right password | sv_password behaviour | Owner should clear it and use a search key, whitelist or plugin password instead |
| Server not listed publicly | It is hidden from public or lobby listing | Use direct connect, favourites or steam://connect |
| Kicked while loading a custom map | Missing campaign files or modified core files | Install the exact Workshop item the admin names and remove client mods that trip sv_pure or sv_consistency |
| Home-hosted server works locally but not for friends outside | No 27015 forwarding or CGNAT | Forward 27015 UDP and TCP; if the line is behind CGNAT, outside joins cannot work |
- Check the address first: panel IP and game port, not
27005. - Decide which route you are using: direct join or lobby join.
- If it is a direct route, confirm the owner has
sv_allow_lobby_connect_only 0. - If invites matter, stop direct-connecting and rebuild the session as a lobby with
mm_dedicated_force_servers. - If extra players are blocked, check whether the server is reserved and full for that mode.
- Only then move on to password, update, addon and home-network checks.
For the server owner: settings that make joining easy
If your aim is simple joining with the fewest support messages, set the server up to allow both direct access and a clean private lobby route. These two lines cover the most common cases:
sv_allow_lobby_connect_only 0 sv_search_key <key>
The first line allows non-lobby joins such as connect, favourites and browser connects. The second gives you a clean way to steer a private lobby to the right machine without relying on sv_password. They solve different problems, so do not treat one as a substitute for the other.
Then tell the group one rule: use one join method per session. If the evening starts as a lobby-led private game, keep it that way. If it starts as a direct-IP community session, tell everyone to join by address or favourites and not expect the lobby invite button to wake up halfway through.
Also be deliberate about discoverability. If you expect lobbies to find the server, do not hide it from lobby searches with sv_region 255. If you use custom campaigns, name the exact Workshop item players need. And after a game update, update the server before you invite anyone in.
If you are still choosing where to host, our Left 4 Dead 2 server hosting comparison shows which hosts give you direct access to server.cfg, a clear IP and port in the panel and a one-click update, which are the three things that decide how often your group gets stuck at the menu.
If joining problems keep coming back, the real issue is often awkward panel access to the cvars and update tools that matter. A better host will not change L4D2’s lobby rules, but it does make those rules much easier to work with.
Compare Left 4 Dead 2 server hostsLeft 4 Dead 2 server FAQ
How do I join a Left 4 Dead 2 dedicated server with an IP?
Enable the developer console, open it at the main menu, and type connect IP:port. The usual default game port is 27015, not 27005. This only works if the server owner has set sv_allow_lobby_connect_only 0.
Why is the invite button greyed out on my L4D2 server?
Because the session was started as a direct server join, not as a lobby. In-game invites belong to lobbies, so if the first player joined with connect, favourites or the browser, there is no lobby to invite into. Either have everyone join directly, or leave and restart the session through a forced dedicated lobby.
Why can’t a fifth player join my Left 4 Dead 2 server?
If the current game was started from a co-op lobby, the server is reserved and that lobby caps co-op at 4 humans. Once that reserved game is full for the mode, nobody else can join by any method. More than 4 humans in co-op needs server-side multi-slot support and direct IP joins.
How do I make a lobby use my own dedicated server?
The lobby leader should open the console at the main menu and enter mm_dedicated_force_servers IP:port. Then create the lobby, choose Best Available Dedicated, invite friends and start the game. For private groups, matching sv_search_key values on the server and the lobby leader help make sure the right server is picked.
Does sv_password work in Left 4 Dead 2?
It is widely reported as unreliable, especially when the correct password is still rejected at the prompt. Many private servers leave it empty and use a whitelist plugin, a plugin password or sv_search_key instead. If your group keeps getting rejected by the password box, the fix is usually on the server side, not the client side.
More Left 4 Dead 2 server help
Set up your own server, or compare hosts that make the settings above easy to reach.
Menu names, console commands and cvars reflect Left 4 Dead 2 as of November 2026. Host panels label the IP, port and server.cfg editor differently, so use your host’s panel for those details; the join rules themselves stay the same.