CS:S Server Not Showing in the Server List? How to Fix It

A Counter-Strike: Source server that runs but does not appear in the Internet tab almost always has one of five problems: no valid Steam login token for app 240, sv_lan set to 1, port 27015 UDP blocked or forwarded to the wrong machine, a server that is out of date after a Valve patch, or filters in the player's browser hiding it. Work through them in that order. The quickest test is to connect directly with connect ip:port in the console: if that works, the server is fine and only the listing is broken.

This guide walks through each cause with the exact place to look. If you are still installing the server, start with how to host a Counter-Strike: Source server and come back here if it does not list.

First, split "can't find it" from "can't join it"

Open the developer console (enable it in Options, Keyboard, Advanced) and type:

connect 203.0.113.10:27015

Use your public IP and the game port, not a LAN address.

• You join fine. The server works and the network path is open. The problem is listing: the token, sv_lan, the master server or filters. Read the next three sections.
• It times out. Nothing reaches the server. Skip to the port section.
• You get rejected with a message. Read it. A version message means the server needs an update, a password prompt means sv_password is set, and "Server is full" means exactly that.

A second free check is Valve's own API. Open this in a browser with your IP:

https://api.steampowered.com/ISteamApps/GetServersAtAddress/v1/?addr=203.0.113.10

If your server is in the answer, Steam knows about it and players' filters are the likely culprit. If the list is empty, Steam has not accepted it, which points at the token or the network.

Cause 1: the Steam login token is missing, wrong or dead

Community servers register with Steam through a Game Server Login Token passed with +sv_setsteamaccount on the start line. Without one, the server runs as an anonymous server and does not list reliably.

Check these in turn on Steam's game server account page:

1. The App ID is 240. That is Counter-Strike: Source. A token made for 232330 (the dedicated server tool) is the most common mistake there is, since 232330 is the number you used to install.
2. The token is still there. Tokens get deleted, and they stop working if the Steam account that made them is limited, banned or has had its phone number removed. If the page shows a last logon date that is old while your server is running, the server is not using it.
3. One token per server. Two servers with the same token knock each other off the list. Make a new one for each server, even on the same machine.
4. The token reaches the server. It must be on the command line as +sv_setsteamaccount TOKEN. Putting it in server.cfg is too late, because the server has already logged in to Steam by the time the config runs.

Watch the server console as it boots. You want to see it connect to Steam without errors around the logon lines. A rejected or invalid token shows up there before any player tries to join.

Cause 2: sv_lan is set to 1

sv_lan 1 tells the server it is on a local network only. It still runs, people on your own network can still see it under LAN, and nobody outside can see or join it. Open cstrike/cfg/server.cfg, make sure it says:

sv_lan 0

Then look for a second sv_lan line further down, or in another config that gets executed after server.cfg. The last value wins. Restart the server after changing it, a map change is not always enough for listing to recover.

Cause 3: the port is blocked or forwarded wrong

If direct connect timed out, the packets are not getting through. CS:S needs:

Things that go wrong at home:

• Forwarded to the wrong local IP. The PC got a new address from the router after a restart. Give it a reserved address and forward to that.
• Windows Firewall. Allow srcds.exe on public and private networks, or open 27015 UDP inbound.
• Wrong port in the rule. You started with -port 27016 for a second server but only forwarded 27015.
• CGNAT. Some providers, especially mobile and fixed wireless, share one public IP between many customers. If the WAN address in your router does not match what a "what is my IP" site shows, you are behind CGNAT and forwarding cannot work. You need a public IP from your provider or a server that already has one.
• Two network cards or a VPN. The server can bind to the wrong interface. Add +ip 0.0.0.0 or your machine's LAN address to the start line.

In the server console, status prints the address and port the server is using. Make sure it matches what you forwarded.

Cause 4: the server is out of date

After a Valve update, clients run the new build and an old server stops being useful: it may drop off the list or reject players with a version message. Stop the server, run your SteamCMD update line again:

steamcmd +force_install_dir ./css +login anonymous +app_update 232330 validate +quit

and start it. The February 2025 update that brought 64-bit builds to CS:S broke a lot of community servers until their owners updated the server files, Metamod:Source and SourceMod. If listing stopped right after a patch, this is your first suspect. Plugin framework problems after an update are covered in installing SourceMod on CS:S.

Cause 5: the player's filters hide it

The Steam browser applies filters on the client side. Your friend may have Not full, Has users playing, Anti-cheat, a map name, a latency limit or a region set. An empty server fails "has users playing" every time.

The reliable workaround for a small group: in the Steam client open View, Game Servers, Favorites, click Add a server and enter ip:port. The server then stays in their favorites whether the Internet tab shows it or not. Setting sv_region in server.cfg also matters if players filter by region; 255 means world.

A server with a password still lists, it just shows a lock. If you want it hidden from strangers, the password is the right tool, not sv_lan.

A short checklist

1. connect ip:port works from outside your network.
2. Token made for App ID 240, one per server, on the start line.
3. sv_lan 0, with no later config overriding it.
4. Port 27015 UDP forwarded to the right machine and allowed in the firewall.
5. Server files updated after the latest patch.
6. Valve's GetServersAtAddress API returns your server.
7. Friends add it under Favorites if the Internet tab still misbehaves.

Skipping the whole problem

Most of this list is home hosting trouble: tokens, router rules, CGNAT and remembering to update. A Counter-Strike: Source server from GamezServers gets its Steam token created by us at setup, so it lists from the first start, it has its own public address so there is nothing to forward, and auto update is a toggle in the control panel. You keep full access to server.cfg and your map folder, and it is live within minutes of ordering.

FAQ

Why does my CS:S server only show under LAN?

sv_lan is set to 1 somewhere in your configs, or the server has no working Steam token. Set sv_lan 0, check the token is for App ID 240, and restart.

Which App ID do I use for a Counter-Strike: Source server token?

240. The 232330 ID is only for installing the dedicated server with SteamCMD. A token made with 232330 does not work.

Can friends join if the server is not in the list?

Yes. Listing and joining are separate. If the port is open they can type connect ip:port in the console or add the server to their Steam favorites.

Does a password hide my server from the list?

No. A passworded server still lists with a lock icon. Players need to type the password in the console before they connect.