CS2 Server GSLT Token Error? How to Fix It (Code 5005)

Fix CS2 server GSLT token errors like "Cert request for invalid failed with reason code 5005" and "LAN only": create, regenerate and set your token.

Updated Sep 30, 2026 · 5 min read

On this page

A CS2 server GSLT token error means the server could not log in to Steam with a valid Game Server Login Token, so it falls back to LAN only: friends cannot connect over the internet and the server does not show in the browser. The fix is almost always to create or regenerate a token at steamcommunity.com/dev/managegameservers with app ID 730, set it with +sv_setsteamaccount, and restart. This guide covers every error message, what causes it and how to fix it.

The error messages

These are the lines people see in the CS2 server console. Search this page for yours:

Cert request for invalid failed with reason code 5005. We're not logged into Steam
No Steam account token was specified.
Logging into anonymous game server account.
Connections will be restricted to LAN only.
Unable to determine local identity, and auth required. Not logged in?

They all mean the same thing: the server has no working token. On the player side it usually shows up as the connection timing out or the server simply not appearing in the Community Server Browser.

Quick fix

  1. Go to steamcommunity.com/dev/managegameservers.
  2. Find your token in the list. If it is marked expired, click Regenerate. If there is none, create one with app ID 730.
  3. Copy the token exactly, with no spaces.
  4. Set it on the server with +sv_setsteamaccount YOURTOKEN in the launch line (or paste it in the panel on a hosted server).
  5. Restart the server and check the console. The token errors should be gone.

Cause 1: No token at all

CS2 needs a token for internet play. Without one, the server logs into an anonymous account and restricts connections to LAN. That is fine for a LAN party, but nobody outside your network can join.

Create a token:

  1. Sign in at steamcommunity.com/dev/managegameservers.
  2. Enter App ID 730 (Counter-Strike 2) and a memo such as "my cs2 server".
  3. Click Create and copy the token.

Cause 2: The token is in the wrong place

The token has to be set when the server starts, in the launch line:

./game/bin/linuxsteamrt64/cs2 -dedicated +map de_mirage +sv_setsteamaccount YOURTOKEN

Putting sv_setsteamaccount in server.cfg does not work reliably, because the server logs in to Steam before that file runs. On a GamezServers CS2 server, paste the token in the panel and restart, and we handle the rest.

Cause 3: Typo, spaces or the wrong ID

  • An extra space or a missing character breaks the token. Copy it again from the Steam page.
  • The token must be created for app ID 730. Tokens made for another game do not work.
  • Do not wrap it in extra quotes or add brackets from an example.

Cause 4: The token expired

Valve expires tokens that go unused for a long time (the server never logs in with it). The token still shows on the page, marked as expired. Click Regenerate next to it, copy the new value and update your server. The old value stops working as soon as you regenerate.

Changing your Steam password also regenerates every token on your account, so after a password reset, update all your servers.

Cause 5: The same token on two servers

Each running server needs its own token. If you start a second server with the same one, one of them gets kicked off Steam. Create a second token for the second server, it is free and each account can have up to 1000.

Cause 6: Your account cannot create or keep tokens

Valve only allows tokens from accounts that:

  • are not community banned or locked,
  • are not limited (a limited account is one that has not spent at least 5 USD on Steam),
  • have a qualifying phone number registered,
  • own the game, which for free to play CS2 simply means it is in your library.

If you cannot create a token, check these first. A brand new Steam account is often limited.

Cause 7: The token was banned

Valve can ban a token, or the account behind it, when a server breaks its rules for community servers, for example plugins that let players use skins or items they do not own. The manage page shows when a token is banned. Remove the plugin that caused it, and note that a new token on the same account can be banned again if the server keeps breaking the rules.

How to check it worked

After restarting, the console should no longer show the anonymous login or reason code 5005 lines. Then:

  1. Connect from another network with connect youraddress:27015.
  2. Open the Community Server Browser in CS2 and search your hostname. New servers can take a few minutes to appear.

If connecting still times out from outside with a valid token, the problem is the port rather than the token. Self hosters need UDP 27015 forwarded, see how to port forward a game server. A hosted server has the ports open already, so the token is the only thing to sort out.

Keep your token private

Anyone with your token can run a server under your Steam account, and if their server breaks the rules, your token gets banned. Do not post it in Discord or screenshots. If it leaks, regenerate it.

FAQ

Do I need a GSLT for a CS2 server?

Yes, for anything beyond LAN. Without one, CS2 logs in anonymously and restricts connections to your local network.

What does reason code 5005 mean in CS2?

The server tried to log in to Steam with an invalid or missing token. Create or regenerate the token and set it with +sv_setsteamaccount.

Is a GSLT free?

Yes. Tokens are free from steamcommunity.com/dev/managegameservers. Your account just needs to meet Valve's requirements, including not being limited.

Can I use one GSLT for two servers?

No. Each server running at the same time needs its own token.

Where do I put the GSLT on a hosted server?

On GamezServers, paste it in the panel and restart. For every other setup detail, see how to host a CS2 server.

Skip the setup. Your CS2 server, live in 60 seconds.

Plans first month from $4.99. No command line, cancel any time.

Deploy CS2

Keep reading