Work through these in order. The first one accounts for most cases.
1. The game server token
A Counter-Strike server needs a Steam game server token to be listed publicly and to accept players from the internet. Without one the console reports it during boot and the server stays private.
- Create a token on the Steam game server account page using your own Steam account.
- Stop the server and open
csgo/cfg/server.cfg. - Add
sv_setsteamaccount YOURTOKEN. - Save and start the server, then read the console for a line confirming the server logged in to Steam.
The token belongs to your Steam account. Keep it private, and note that Valve can reset tokens on accounts that break their rules.
2. sv_lan must be 0
With sv_lan 1 the server never advertises and rejects internet connections. Set it to 0 in server.cfg and restart.
3. Browser filters
- Look under community servers, not official matchmaking.
- Clear the filters for empty, full and password protected servers.
- Search on part of the hostname.
- Add the server to Steam favourites once found.
4. The server stops or restarts by itself
- Open the Console tab and restart the server.
- Read the first 40 lines. A missing map, a broken
gamemodes_server.txtor a plugin that fails to load will stop the boot. - If you recently added a plugin, move it out of
csgo/addons/sourcemod/pluginsand start again.
5. Players connect and are dropped
- Check the slot count. A server that is full refuses new connections.
- Check
sv_passwordif players report a password prompt they did not expect. - Confirm the client and server are on the same build after an update, and restart the server so it updates.
Open a ticket from Support in the Client Area with the console output from a fresh start if none of this fits.





