CS2 server visibility: Auto, Public, and Direct-connect

Counter-Strike 2 server visibility explained: what Auto, Public, and Direct-connect mean, what each one does at boot, and which one fits your setup.

Counter-Strike 2 server visibility on Hostd is the setting that decides whether your server shows up in the public CS2 browser and whether it runs VAC secure. There are three modes, and the right one depends on what kind of server you're running.

The three modes

These are the exact labels you'll see in Settings → Server visibility on every CS2 server.

Auto

Try Public; fall back to Direct-connect after 60s if Steam never confirms the GSLT.

This is the default on every freshly provisioned CS2 server. Auto attempts Public first. If a valid GSLT is saved and Steam confirms the login within 60 seconds, the server runs in Public mode (browser-listed, VAC secure). If Steam never confirms (no token saved, token rejected, Valve refuses the IP), the server falls back to Direct-connect so your players can still join.

Public

Uses your Steam Game Server Token. Server appears in the public CS2 browser, VAC secure.

Pin the server to Public mode. Requires a saved GSLT. If you switch to Public without a token, the panel nudges you to either add one or pick Auto / Direct-connect.

Direct-connect

Anonymous Steam login. Not listed in the public browser; players join via Favourites or the developer console. No VAC.

Pin the server to Direct-connect. The server logs into Steam anonymously, doesn't appear in the browser, and runs without VAC. Players connect by IP or by the connect string.

What "Auto" actually does

Auto is the safe default for a reason: it tries the better mode first and gracefully falls back. Specifically:

  1. At boot, if a GSLT is saved, Auto writes sv_setsteamaccount and starts CS2 as a public, VAC-secure server.
  2. The entrypoint watches the server log for up to 60 seconds, looking for Gameserver logged on to Steam.
  3. If that line shows up, Auto stays in Public. The console prints [Hostd] Steam auth confirmed. Server is operating in Public mode.
  4. If it doesn't, Auto flips to Direct-connect for that boot, writes a fallback state file, and logs [Hostd] Steam did not confirm gameserver login within 60 seconds. Falling back to Direct-connect mode so your players can join. The server stays in fallback until you click Retry public mode in Settings (which clears the state file) and restart.

A freshly provisioned CS2 server that hasn't had a token added yet is the most common case: Auto sees no token, prints Auto mode: no Steam Game Server Token set, so Public is not viable. Booting in Direct-connect., and boots straight into Direct-connect without burning the 60-second timer. Add a token, restart, and you'll be in the browser.

When to use Public

Pin Public when you know you want browser visibility and you've got a working token:

  • Pug nights you want strangers to find.
  • Community servers (retake, surf, bhop, deathmatch, MGE).
  • Anything where being listed in Community Servers → Internet is part of the value.

You also get VAC, which keeps casual cheaters off the server with no extra config.

When to use Direct-connect

Pin Direct-connect when browser presence isn't the point:

  • Friends-only and private scrim servers.
  • Servers running plugins that brush against Valve's narrower automated rules where a GSLT ban would be a hassle (the ban lands on your account, not Hostd's).
  • Anywhere you don't want strangers in the browser stumbling onto the server.

The trade-offs are as follows:

  • No VAC. Valve won't ban cheaters from this server. If you need protection, run a CounterStrikeSharp anti-cheat plugin.
  • Not in the public browser. Share the connect string yourself or have players favourite the server by address.
  • Anonymous server identity. The server's SteamID changes on every restart. Anything that pins to a stable SteamID (stat-tracking services, some Discord integrations) sees a fresh server each boot.
  • Some plugins require a GSLT. A few CounterStrikeSharp plugins refuse to run without a valid token and silently no-op in Direct-connect.

When to use Auto

Auto is the default, and it's the right call for most customers:

  • You're new and not sure whether your token will authenticate yet.
  • Your server / colo range occasionally has Valve gameserver-auth issues (Valve has discretion to refuse auth from IP ranges it classifies as risky; some ranges sit on undocumented blocklists), and you want the server to still be reachable when that happens.
  • You'd rather your players land on a working server than a failed boot.

Auto means the worst case is "server is reachable, just not browser-listed," which is usually fine.

How players connect in Direct-connect

Whether you've pinned Direct-connect or Auto fell back to it, players connect the same way:

Add the server to the Favourites tab in Steam (View → Servers → Favourites → Add a Server), or open the CS2 developer console (~ key, enable it under Game Settings → Enable Developer Console) and run: connect <address>:<port>

Your stored Steam token is preserved when you switch modes. Flipping back to Public or Auto reuses it; no need to re-paste anything.

Don't forget to restart

The visibility mode is read once when the server boots. The dashboard says it plainly: "Restart the server after switching modes." Switching modes in Settings updates the saved value, but the running container still has the old mode until you restart.

Where to next

Last updated 2026-05-20. Notice a mistake? Tell us.

Cookies

We use a few cookies that are strictly necessary to sign you in and keep your account secure. We do not load any advertising or third-party trackers. We would also like to run our own cookieless analytics so we can understand which pages are useful. See our Cookie Policy for the full list.