CS2 Server Not Showing in the Community Server Browser? Fixes

Your CS2 server runs but nobody can find it in the Community Server Browser. Check the GSLT, sv_lan, ports, filters and listing delay.

Updated Oct 7, 2026 · 5 min read

On this page

A CS2 server that runs fine but does not show in the Community Server Browser is almost always missing a valid Game Server Login Token (GSLT), running with sv_lan 1, or blocked on port 27015. Fix those three and it normally appears within a few minutes. Browser filters on the player's side hide plenty of servers too. While you sort it out, players can always join directly with connect <ip>:27015 in the console.

How the listing works

When a CS2 server starts with a GSLT and internet access, it registers with Valve's master server. The Community Server Browser asks the master server for the list, then pings each server directly on its game port. If any of those steps fails, the server is missing from the list even though it is running and joinable by IP.

Check 1: A valid GSLT

Without a GSLT, a CS2 server can only be reached on a local network and is not listed. Get a token at the Steam game server account management page (steamcommunity.com/dev/managegameservers) for app ID 730, and pass it on the start line:

+sv_setsteamaccount YOUR_32_CHARACTER_TOKEN

Then look at the console during start up. Healthy output includes the server logging on to Steam and showing its public IP. Messages about a token being invalid, already in use or banned mean the server is not listed. The GSLT token error guide explains each message, including reason code 5005.

Each server needs its own token. Using one token on two servers knocks one of them off.

Check 2: sv_lan is 0

sv_lan 1 makes the server LAN only: it does not register with Steam and remote players cannot join. Check it in the server console:

sv_lan

If it says 1, find where it is set. Look in game/csgo/cfg/server.cfg, the start line, and any config a plugin or tutorial added. Set it to 0 and restart.

Check 3: Ports reach the server

The browser pings the server on its game port. These ports must be open on a self hosted server, both in the operating system firewall and as forwards on the router:

Port Protocol Used for
27015 UDP Game traffic and server queries
27015 TCP RCON
27020 UDP SourceTV, only if you use it

If you start the server with a different -port, open that one instead. A server behind CGNAT (common on mobile and some fiber or satellite connections) cannot be reached from outside at all, and will never list. The guide to port forwarding a game server covers router steps and how to spot CGNAT.

To test from outside, ask a friend to join with connect <your public ip>:27015. If that fails, the problem is network reachability, not the browser.

A CS2 match on a classic map

Check 4: The server is not hidden on purpose

A few settings keep a working server out of public view:

  • A join password (sv_password). Password protected servers still list, but players who filter out locked servers will not see them.
  • -insecure on the start line. It disables VAC, and players filtering for secure servers will not see it. Remove it unless you need it for testing.
  • A hostname nobody searches for. Set a clear hostname in server.cfg so players can find it with the name filter.

Check 5: The player's browser filters

The Community Server Browser has filters that hide more than people expect. Ask the player to open Play > Community Server Browser, go to the Internet tab, clear every filter, and search for part of the server name. Common culprits:

  • Has users playing hides empty servers, including your new one.
  • Server not full and Is not password protected.
  • Latency limits that cut off servers a bit further away.
  • A specific map filter left over from a previous search.

Once it shows, players can add it to Favorites so they never need to search again. They can also add it straight to Favorites by IP and port.

Check 6: Give it a few minutes

A freshly started server can take several minutes to appear in the list. Restarting it over and over resets that wait. Start it once, check the console says it connected to Steam, and wait before testing again.

Quick join while you troubleshoot

Players do not need the browser to join:

connect 203.0.113.10:27015

Type it in the CS2 developer console (enable it in Settings > Game > Enable Developer Console, open it with the ~ key). Add ; password yourpassword if the server has one. Steam links in the form steam://connect/203.0.113.10:27015 also work and are handy to share in Discord.

A server that lists itself

On a GamezServers CS2 server, the token goes in the Steam server token (GSLT) setting, the server has its own address with the game port already open and DDoS protection on, and there is no router or CGNAT in the way, so checks 1 to 3 come down to pasting a valid token. The live console shows the Steam login as it happens. If you want your scrim or retakes server up without the network fight, see the CS2 game page.

Players in a CS2 firefight

FAQ

Why can I join my CS2 server by IP but not see it in the browser?

The server is reachable but not registered with Steam, usually because of a missing or invalid GSLT, or sv_lan 1. Check the console at start up for Steam login messages.

Do I need a GSLT for my CS2 server to show up?

Yes. Without a valid GSLT for app 730, the server is not listed and players outside your network cannot join.

How long does a new CS2 server take to show in the list?

Usually a few minutes after it starts. Restarting it repeatedly makes the wait longer.

Which ports does a CS2 server need?

UDP 27015 for the game, TCP 27015 for RCON, and UDP 27020 if you use SourceTV. Use your own port if you changed -port.

Skip the setup. Your own CS2 server.

$4.99USD first month

Then $9.99/mo. Just trying it? $2.50 for 3 days

Keep reading