Counter-Strike 2 Updated April 26, 2026

How to Fix Your CS2 Server Not Appearing in the Community Browser

If your CS2 server isn't showing up in the community server browser, here are the most common causes and how to fix each one.

CS2TroubleshootingServer BrowserGSLTFirewall

Quick Checklist

Server not in the browser? Run through these in order. Most issues are one of the first three.

1. Missing or Invalid GSLT

Game Server Login Token is required for your server to be listed publicly. Without it, the server runs but won't appear in the community browser.

Get your token here: https://steamcommunity.com/dev/managegameservers

  • Log in with your Steam account
  • Select App ID 730 (CS2)
  • Create a new token — give it a memorable memo
  • Copy the token

Add it to your server launch parameters:

+sv_setsteamaccount YOUR_TOKEN_HERE

If you already have a token, check whether it's been invalidated. Tokens get invalidated if:

  • You've created too many tokens on one account (Steam limits this)
  • The account associated with the token received a VAC ban
  • You manually revoked it

Create a new token if yours is invalidated.

2. Server Isn't Fully Started Yet

The server is only registered with Steam's server browser once it completes its startup sequence. Look in your console for:

VAC secure mode is activated.

That line confirms the server has fully registered. If you check the browser before this appears, the server won't be listed yet.

Wait for that message before troubleshooting further.

3. Firewall Blocking the Query Port

CS2 uses UDP port 27015 for both game traffic and Steam server queries. Both directions need to be open:

  • Inbound UDP 27015 — game traffic and server queries
  • Outbound UDP — server responding to Steam master server

If you've changed the default port, update accordingly. Check your server's firewall rules and any network-level firewall between the server and the internet.

You can test whether your server is responding to queries using a tool like steamquery or by using the Steam server browser directly:

steam://connect/YOUR_IP:27015

4. Missing sv_tags

Some community browser filters require specific tags. Set tags in your server.cfg:

sv_tags "competitive,custom"

Tags help players find your server through the filter system. Not having them won't hide your server from everyone, but it might hide it from players using tag filters.

5. Browser Propagation Delay

The first time a server comes online, it can take 5–15 minutes to propagate to the Steam master server list. This is normal. Don't panic-restart the server repeatedly — each restart resets the timer.

Let it run for 15 minutes, then check again.

6. Browser Filters Hiding Your Server

CS2's in-game community browser has filters that are sticky — they save between sessions. A player might have filters set that exclude your server:

  • Map filter not matching your current map
  • Player count filter (min/max players)
  • Tag filter excluding your tags
  • Ping filter set too low

Tell players to clear all filters when looking for your server. In the browser: click the filter icon and reset to defaults.

Direct Connect While Troubleshooting

You can always connect directly while diagnosing browser issues. Open the CS2 developer console with ~ and type:

connect YOUR_SERVER_IP:27015

If direct connect works but the browser doesn't show it, the server is running fine — it's a registration or propagation issue.