This guide owns one job: the base configuration intent. Your CS2 server already exists and you want to set up server.cfg, access and RCON in a traceable way. Use Counter-Strike 2 server hosting for plans and pricing. For GSLT, fixed match rules and the competitive map pool, continue with the CS2 competitive server setup.

What this guide covers—and what it does not

This page establishes only the dependable base: server name, private access, RCON, security values and a restart test. Specialist jobs have their own guides:

This separation makes it clear which file owns the base values and which change to roll back when something fails.

Requirements

You need access to the panel, file manager or SFTP, the server console, and the displayed address and port. A publicly listed server also needs a Game Server Login Token. Valve manages GSLTs through Steam Game Server Account Management; CS2 uses App ID 730.

Treat the GSLT and RCON password as credentials. Never place them in screenshots, public repositories or public chat history.

Keep server.cfg as the traceable base

Open the active server.cfg in the panel. Start with a small set of values whose purpose you understand:

hostname "My CS2 Server"
sv_password ""
rcon_password "A_UNIQUE_LONG_PASSWORD"
sv_cheats 0
sv_lan 0

hostname controls the visible name. An empty sv_password permits access without a game password; use a separate password for private practice. rcon_password protects remote administration and must not match the game password. sv_cheats 0 blocks normal cheat commands, while sv_lan 0 is intended for an internet-accessible server.

Do not manage the same value in a panel preset and several cfg files at once. Decide which path is authoritative and document it. Otherwise a later restart can look random when a second configuration simply overwrites the value.

Test access and the admin base

Save the file, restart the server in a controlled way and read the startup log first. Then connect through the CS2 console:

connect IP:PORT

Check these points in order:

  1. The server reaches the ready state without a new cfg error.
  2. The visible hostname is correct.
  3. The game password behaves as intended.
  4. RCON accepts only the new admin password.
  5. A second test client can join normally.

A running process alone does not prove a working join. GSLT, port, password and client/server builds must also agree.

Roll out changes safely

Back up the working server.cfg before each larger change. Change one related group, restart, and record the time and result. When adding plugins or Workshop maps later, verify the unchanged base first. You can then distinguish a base configuration failure from an extension failure.

Current Valve patches, map-pool changes and the reviewed status live in the CS2 update hub. The hub does not replace configuration; it tells you when to recheck the build, maps or extensions.

Troubleshooting

Values do not apply after restart

Verify that you edited the active server.cfg and that a panel preset or match config does not overwrite the same value later. Find the loaded configuration in the startup log and test with one changed value.

The server is not listed publicly

Check the GSLT, App ID 730, server build, port and startup log. Never publish the token. Replace it in Steam management if it was exposed.

Players cannot connect although the process is running

Compare client/server builds, address, port and sv_password. Test without extra plugins and with an official map first; then investigate maps or plugins in their specialist guides.

RCON does not respond

Set a new unique password, restart and check whether another file overwrites it. Do not expose RCON unnecessarily, and share the password only with responsible admins.

Verification, limits and rollback

These values are a minimal operating base, not a universal performance promise. Network path, player count, maps, plugins and concurrent load affect the result. On failure, restore the last working server.cfg, restart, and retest join and RCON.

Primary sources

FAQ

Do I need plugins for a simple CS2 server?

No. Hostname, access and basic rules work without CounterStrikeSharp. Add a plugin only for a concrete extra job.

Do Workshop maps belong in this base guide?

No. server.cfg remains the stable base here; the Workshop guide covers IDs, downloads and rotation.

Where do I configure competitive rules?

GSLT, match cfg, overtime and the map pool belong in the competitive guide, keeping this page separate from match setup.

Must I restart after every change?

For a dependable test, yes—unless you know the exact value can be reloaded safely at runtime. A controlled restart makes the result reproducible.