CS2 server not reachableGSLT, connection and visibility in the server list

Published on August 9, 2026 · last updated on November 4, 2026

First clarify: not reachable or not visible?

The two cases have different causes and different solutions:

• Not reachable: even a direct connect IP:port in the console fails. Then the server is not running or the address is wrong.
• Not visible: connect works, but the server appears in no browser. That is almost always a GSLT matter.

So always do the direct test via the console first - it decides which section below applies to you. How to enable the developer console is explained in join a CS2 server.

Four tests that narrow down the cause

Before you tinker with configs, narrow it down. Four tests in this order cleanly separate server, address and player side - and each one rules out a whole area:

1. Status in the web interface. If the server is stopped, the search ends here and everything else is superfluous.
2. Read the server console. A server that starts and drops out again seconds later writes the reason into it. These lines are the most reliable source in the whole process - more reliable than any guess.
3. Connect yourself via connect IP:port. If it works for you, the server is running. Then it is not a reachability problem but a rule on the server or something on the other side.
4. Have someone from outside test it. Ideally from a different network and with the same address. If this person gets in and your fellow player does not, it is their connection.

The distinction matters: how connecting works in the first place, where you find the fixed address made up of IP and port and how you log in with a server password set is explained in join a CS2 server. This page is only about the case in which exactly that way does not work.

No GSLT entered

The most common reason for an invisible CS2 server. A Game Server Login Token is mandatory for the server to register publicly with Steam. Without a valid token, it runs and is reachable via direct connection, but appears in no list.

You create the token via Steam's game server management with app ID 730 and enter it via sv_setsteamaccount. The steps in detail are in create and enter a GSLT.

Two pitfalls: a token is tied to exactly one account and usually to one server - the same token on two servers leads to deregistrations. And Valve makes tokens invalid after longer inactivity; then only a new one helps.

The server is not running or the address is wrong

If even the direct connection attempt fails:

1. Check in the console in the web interface whether the start ran through completely.
2. Compare the server address made up of IP and port in the web interface - the port has to go into the connect command.
3. Enter the command completely: connect 192.0.2.10:27015, with a password set add ; password yourpassword.

If the start itself aborts, the cause is in the console - usually a faulty entry in a config loaded via exec. The basics are in RCON commands.

No longer reachable after a plugin installation

Metamod and CounterStrikeSharp intervene deeply in the server start. Typical errors after setting them up:

• Metamod not entered in the gameinfo.gi - then it is simply not loaded, and everything built on it is missing.
• The entry was overwritten by a game update - after CS2 updates, the file needs checking again.
• The plugin does not match the version of CounterStrikeSharp - then the start aborts.

To narrow it down, remove the most recently installed extension and restart. The correct setup is described in install Metamod & CounterStrikeSharp.

What was changed last

A server that ran yesterday and does not today has rarely broken by itself. The question about the last change leads to the goal faster than any checklist, and the candidates are manageable:

• A game update from Valve. Afterwards, the plugin foundation often briefly no longer fits, and the Metamod entry may have been overwritten.
• An edited config. An unclosed quotation mark makes everything after it ineffective - the load order and the typical stumbling blocks are in server.cfg explained.
• A changed startup line. A duplicate or contradictory map parameter prevents the start completely, see Workshop maps & collections.
• An additional plugin - or one that was updated without the foundation underneath catching up.
• None of these. Then the GSLT has usually silently become invalid: the server keeps running, just invisibly.

If in doubt, roll back in reverse order - undo the last change, restart, check. Only when the server runs again does the change come back piece by piece. Anyone who touches several things at once instead does not know in the end what helped, and is back at square one next time.

For a match day, it is therefore worth backing up the last working version of your configs beforehand - via WebFTP or SFTP, because there are no automatic backups. How this fits into a tournament flow is shown in tournament and LAN setup.

Players cannot get in, but you can

Then the server is fine, and it is a rule or the other side:

• sv_password is set and your fellow players do not know it.
• sv_lan 1 is still active - that makes the server reachable only in the local network.
• The players only received the IP without the port.
• A restrictive network on the player side blocks UDP - see ports & firewall.

Frequently asked questions