This guide covers common Counter-Strike 2 server issues and how to fix them. For initial server setup, see CS2 Server Setup Guide. For admin commands and competitive configuration, see CS2 Admin Setup.
GSLT / Steam Authentication Errors
Your server needs a valid Game Server Login Token (GSLT) to appear in the server browser and run with VAC protection. The table below covers the most common GSLT-related errors.
| Error / Symptom | Cause | Fix |
|---|---|---|
No account token specified |
GSLT not set in startup parameters | In GPanel, open the Startup tab and paste your token into the GSLT field |
GSLT is expired or invalid |
Token was regenerated or revoked | Visit Steam game server management, regenerate the token, then update it in GPanel |
Game server login token banned |
Account associated with the token received a ban | The ban is permanent per-token. Generate a new token on a clean Steam account |
| Server starts in insecure mode | GSLT missing or Steam connection failed | Verify the token is set, check that your assigned game port (see GPanel's Network tab) is reachable, and wait 60 seconds for the Steam handshake |
Server Not Showing in Browser
- Ensure
sv_lan 0is set inserver.cfg. LAN mode hides your server from the internet browser. - Confirm your GSLT is valid and the server console shows Connection to Steam servers successful.
- Server browser listings can take up to 5 minutes to propagate. Use Favourites or direct connect in the meantime.
- Some ISPs and regions have trouble with Steam's server browser UDP queries. Direct connect via console always works if the port is reachable.
Check your server's IP and assigned ports on the Network tab in GPanel. See How to Find Your Server IP and Port for a detailed walkthrough.
VAC / Anti-Cheat Issues
- VAC requires a valid GSLT and
sv_cheats 0. - If you are testing with
sv_cheats 1, VAC is automatically disabled for that session. Restart your server and ensure cheats are off before opening to the public. - Running unsigned or outdated plugins can cause VAC to flag the server as insecure. Keep MetaMod and CounterStrikeSharp up to date after every CS2 game update.
Server Crashes on Startup
- Check the Console tab in GPanel for error messages immediately after the crash.
- The most common cause is an outdated MetaMod or CounterStrikeSharp build after a CS2 update. Remove or update the plugin framework and try again.
- Corrupted game files can also cause crashes. Use GPanel's Reinstall option to verify and restore game files.
Back up first: Before reinstalling, download your
game/csgo/cfg/ folder via SFTP so you do not lose your configuration files. See How to Upload Files via SFTP.
Players Cannot Connect
- Confirm the server is fully started and shows Connection to Steam servers successful in the console.
- Make sure players are using the correct IP and port from GPanel's Network tab.
- If
sv_passwordis set, players must enter the password before joining. Share it directly or use a Steam connect link that includes it:steam://connect/YOUR.SERVER.IP:PORT/YourPassword - Players on the same LAN as the server should connect directly by IP. The Steam server browser may not show LAN-local servers correctly.
Workshop Maps Not Loading
- Ensure you have set a Steam Web API key in your startup parameters. Get one from steamcommunity.com/dev/apikey.
- Verify the workshop map ID is correct (the numeric ID from the Steam Workshop URL).
- Check the console for download errors. Large workshop maps may take several minutes to download on first load.
- If the map fails to load, try restarting the server. Some workshop downloads require a clean restart to complete.
MetaMod / CounterStrikeSharp Not Loading
- Verify the
gameinfo.gifile has the MetaMod search path entry. The lineGame csgo/addons/metamodmust appear in theSearchPathsblock above the firstGameentry. - Run
meta listin the GPanel console. If MetaMod is not listed, re-check the file path:game/csgo/addons/metamod/must exist. - For CounterStrikeSharp, ensure you downloaded the with-runtime package. Without the .NET runtime the plugin will silently fail to load.
- After every CS2 game update, check the MetaMod and CounterStrikeSharp pages for updated builds. Outdated builds are the number one cause of plugin failures.
Do not mix versions: Always update MetaMod and CounterStrikeSharp together. A mismatch between the two can cause crashes or silent failures.
High Latency / Lag
- Check if the server is running out of its allocated RAM in GPanel. CS2 servers with many plugins or workshop maps can use significant memory.
- Review your rate settings in
server.cfg. The modern CS2 defaults (sv_maxrate 0,sv_maxupdaterate 128) work well for most setups. - If players from a specific region experience high ping, the issue is network routing rather than server configuration. There is no server-side fix for geographic distance.
- Disable any unused plugins. Each loaded plugin adds processing overhead per tick.
Related Articles
- CS2 Server Setup Guide — GSLT, server.cfg, game modes, connecting
- CS2 Admin Setup — RCON, commands, competitive config
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
Need help? If you cannot resolve an issue after following this guide, open a support ticket at legionhosting.net/submitticket.php and include your server's GPanel ID, the exact error message, and any recent changes you made to the server.
