You've launched a Counter-Strike 2 dedicated server, you can join it locally, but it never shows up in the public community server browser. Before you start tearing apart port forwarding rules, check a common culprit: a missing or invalid Game Server Login Token (GSLT).
This guide walks you through generating a valid GSLT and attaching it to your CS2 server.
Why the GSLT matters
A GSLT ties a dedicated server to a Steam account. A CS2 server running without a valid token may not show up in the public server list and may not be able to use VAC protection. If your ports are open and your firewall is fine but the server is invisible to the public browser, the token is the first thing to check.
Note that each simultaneously running server needs its own unique GSLT — you cannot run two servers on one token at the same time.
Step 1: Make sure your Steam account qualifies
Valve enforces account requirements before you can create game server accounts. The Steam account you use:
- Must not be limited.
- Must not be community banned or locked.
- Must have a qualifying registered phone attached to it.
- Must own the game you're creating the token for — in this case, CS2.
Step 2: Create the token in Steam Game Server Account Management
- Sign in to the Steam Game Server Account Management page with the qualifying account.
- Create a new game server account using the App ID for Counter-Strike 2: 730.
- Copy the generated login token and treat it like a password from the moment it exists.
Add the token to your CS2 dedicated server's launch command line:
Code: Select all
+sv_setsteamaccount YOUR_GSLT_TOKENCode: Select all
./cs2 -dedicated -port 27015 +map de_dust2 +sv_setsteamaccount YOUR_GSLT_TOKENRestart the server after adding the token, then verify from outside your network — have a friend connect via connect your.ip:27015 (27015 is the commonly used default port), or check whether the server appears in the community browser.
Step 4: Protect and maintain the token
A GSLT is a credential, not a config value you can share casually:
- Never publish it — don't paste it into forum posts, screenshots, public config repos, or Discord messages.
- Regenerate it if exposed. If a token leaks, go back to the management page and regenerate or delete it immediately.
- Expect it to expire if unused. A token that goes unused for a long period of time (the game server never logs in) will expire; regenerate it from the same management page.
- Check tokens after a Steam password reset. If you reset your Steam password via the Steam help site, or Steam Support resets it, all your GSLTs are regenerated — the old token values stop working until you update your launch parameters with the new ones. If your server drops off the public browser right after a password change, this is likely why.
| Symptom | Likely token issue |
|---|---|
| Server missing from public browser | No token set, or token invalid, expired, or wrong App ID used |
| Worked yesterday, gone today | Token expired from disuse, deleted, or regenerated by a password reset |
| Token page refuses to create tokens | Account limited, locked/banned, missing qualifying phone, or doesn't own CS2 |
If the token checks out and the server is still unreachable, move on to the usual network suspects: port forwarding for your server port (27015 by default in most setups), firewall rules on the host, and your hosting provider's network settings.
Summary
A CS2 dedicated server needs a valid GSLT to be listed in the public community server browser and to use VAC. Confirm your Steam account is unrestricted, phone-verified, and owns CS2; create a token for App ID 730 on the Steam Game Server Account Management page; add it to your launch parameters with +sv_setsteamaccount (one unique token per running server); and guard it like any other credential — regenerating it whenever it's exposed, expired, or reset along with your account password.