Black Mesa Server Not Showing or Friends Cannot Connect (Fixes)

When a Black Mesa server is missing from the browser or friends cannot get in, the cause is almost always one of five things: sv_lan 1 (or a missing server.cfg) keeping it off Steam's list, UDP port 27015 not reaching the server, the player's developer console still being off so they cannot type connect, the server and client being on different Black Mesa builds, or a custom map the player does not have. Test with a direct connect ip:27015 first. If that works, the server is fine and only the listing is the problem.

Find your symptom

Step zero: test a direct connect

Before changing settings, split the problem in two. From any Black Mesa client, open the console and type:

connect 203.0.113.10:27015

Use the server's real public address and port. If that connects, the network path works and you only have a listing problem. If it times out, the listing is a side effect of a connection problem, so fix that first.

The console is hidden

Black Mesa ships with the developer console turned off, which is why players say "I typed connect and nothing happened". Each player does this once:

1. Open Options from the main menu.
2. Go to Keyboard, then Advanced.
3. Tick Enable developer console, then OK.
4. Press the tilde key (~, the key under Esc on US keyboards).

On some keyboard layouts the tilde key does not open it. In that case add -console to Black Mesa's launch options in Steam (right click the game, Properties, General, Launch Options), and the console opens on start.

Not in the server browser

1. sv_lan is on, or server.cfg is not loading

sv_lan 1 makes the server LAN only: no heartbeat to Steam and no internet players. Open bms/cfg/server.cfg and make sure it has:

sv_lan 0
hostname "Your Server Name"

Then check that the file is actually read. Type sv_lan in the server console: it prints the current value. If it still says 1, the file is in the wrong folder (it must be bms/cfg/server.cfg, not cfg/server.cfg at the server root), the name is wrong (Windows hides extensions, so server.cfg.txt is common), or something later in the file overrides it.

2. The server cannot reach Steam

Watch the startup log for Connection to Steam servers successful. If you see repeated failures instead, the machine is blocking outgoing traffic or Steam is having a bad day. Outbound UDP must be allowed, and on a VPS the provider's firewall must allow it too.

3. Your server is there, but buried

Black Mesa's server list has had a long running problem with fake servers that copy real server names and redirect players elsewhere, which pushes genuine servers out of sight. Do not rely on scrolling the Internet tab. Add your server to Favorites instead: in Steam, open View, Game Servers, the Favorites tab, click the + button, and enter ip:27015. You can connect straight from that list. Community members on the Steam forums also share a server_blacklist.txt for bms/cfg on the client to filter out the fakes.

4. Give it a few minutes

A freshly started server can take a few minutes to appear on Steam's list. If a direct connect works, carry on playing and check again later.

Friends time out

"Connection failed after 4 retries" means the client sent packets and nothing came back.

• Port 27015 UDP is not open. Forward UDP 27015 (and TCP 27015 for remote RCON) on the router to the server PC's local IP, and allow srcds.exe through Windows Defender Firewall. Our port forwarding guide covers the router screens.
• The server moved port. If something else held 27015 at startup, the server quietly binds 27016 or higher. The console prints the port it used. Add -strictportbind to the start line so it fails loudly instead.
• You shared the wrong address. 192.168.x.x and 10.x.x.x addresses only work inside your home. Friends need your public IP. You, on the same network, should use the local one, because many routers do not support connecting to your own public address.
• CGNAT. If your router's WAN address does not match what an IP lookup site shows, your provider shares one public address between customers and port forwarding cannot work. A hosted server avoids this, as covered in hosting without port forwarding.

Version mismatch after a Black Mesa update

Players update automatically through Steam; your dedicated server does not. After a patch, clients on the new build either fail to see the server or get dropped with errors like "Server uses different class tables". Update the server with SteamCMD:

force_install_dir "../Black Mesa Dedicated Server"
login anonymous
app_update 346680 validate
quit

The reverse happens too. A player who opted into a beta branch in Black Mesa's Steam Properties, Betas is on a different build from a normal server. Have them select "None" and let Steam update.

If you run SourceMod plugins, an update can break those even when the server itself is current. SourceCoop in particular needed hotfixes after the 2025 updates, so see Black Mesa co-op on a dedicated server before updating plugins blindly.

Workshop and custom maps

This is the Black Mesa specific trap. Black Mesa's Workshop is client side: the server does not hand Workshop maps to players, and the dedicated server cannot subscribe to items.

On the player side, everyone subscribes to the map on the Workshop and restarts the game before joining. Share the Workshop links in your group chat before the map goes into rotation.

On the server side, copy the files in by hand. Workshop items land on your PC under Steam\steamapps\workshop\content\362890\<item ID>\.

• A loose .bsp goes in bms/maps/.
• A .vpk package goes in bms/addons/workshop/ and must be listed in bms/addonlist.txt:

"AddonList"
{
   "workshop\1234567890.vpk"     "1"
}

Replace 1234567890 with your file's real name; 1 loads it and 0 disables it. Restart the server, then changelevel to the map name.

For plain .bsp maps that are not on the Workshop, sv_allowdownload 1 lets players pull them from the server on join, which is slow for big maps. A web host for compressed copies (sv_downloadurl "https://example.com/bms/", files in maps/name.bsp.bz2) is much faster.

"Your map differs from the server's" means the player has an older or newer file with the same name. They should delete it from bms/download/maps/ in their game folder, or you should rename updated maps instead of overwriting them.

When you just want it to work

A Black Mesa server on GamezServers skips most of this list: it has its own public address and DDoS protection, so there is no router, firewall or CGNAT to fight, and the Auto Update setting in the panel updates the game on start so it keeps pace with Steam patches. You still share Workshop links with your group, and server.cfg and addonlist.txt are a click away in the file manager. If something still refuses to connect, email support@gamezservers.com.

FAQ

Why can I join my Black Mesa server but my friends cannot?

You are connecting over your local network. Your friends need port 27015 UDP forwarded to your PC and your public IP address, and it will not work at all if your provider uses CGNAT.

How do I open the console in Black Mesa?

Enable it in Options, Keyboard, Advanced, tick Enable developer console, then press ~. Or add -console to the game's launch options in Steam.

Why does my Black Mesa server not show in the server list?

Usually sv_lan is 1 or server.cfg is not being read. Set sv_lan 0 in bms/cfg/server.cfg, restart, and add the server to Steam Favorites so the fake listings cannot bury it.

Do players download Workshop maps automatically from a Black Mesa server?

No. Black Mesa does not push Workshop maps to players. Each player subscribes to the map on the Workshop and restarts the game before joining.