RE:NODE

CS2 server 'running an older version' after update: fix

By RE:NODE Team
15 min read


After a Counter-Strike 2 update, players join your server and get a message along the lines of "the server is running an older version" (the wording shifts between client builds), and the server console may print "Your server needs to be restarted in order to receive the latest update." The fix: stop the server, update its files with steamcmd +force_install_dir <your server folder> +login anonymous +app_update 730 validate +quit, start it again, and check that the version it reports matches the current game. On a panel host the same thing usually means restarting with the update step switched on. Nothing is corrupted and no config is lost; Valve's patch simply reached every player's game within hours, and your server is still on the previous build until something tells it to update.

The rest of this post is for the case where that one command does not work, which is where most of the pain is: SteamCMD that says everything is up to date while the server is still old, an update run against the wrong folder, a server that updated but is still not accepted, and a restart routine so the next patch day costs you two minutes instead of an evening. For the wider set of reasons people cannot join, see CS2 players cannot connect and disconnect reasons; for the general patch-day routine across games, see the game server update day checklist. This post stays on one question: why does a CS2 server stay on an old build, and how do you prove it is fixed.

Why a CS2 server falls behind#

The game and the dedicated server are installed and updated separately. Players have the game from the Steam library, and Steam updates it on its own, usually before they next open the game. Your server is a different install, often a copy under a folder like /home/cs2/server, and it only changes when SteamCMD (or something that runs SteamCMD for you) updates that folder. Valve ships CS2 updates frequently, so a server left running for a week or two is regularly behind.

Joining requires the client and server to agree on the build. When they do not, the server side refuses the connection. Two directions are possible:

  • The server is older than the client. By far the common case after a patch. Players who updated cannot join.
  • The client is older than the server. Rare, because Steam updates games automatically, but a player with updates paused or a stuck download can see the same refusal. The fix is on their side: let Steam finish, or use "Verify integrity of game files" in the game's properties.

A third pattern is easy to misread. Some updates change only the client (UI, cosmetics, anti-cheat), and some change both. You cannot tell from outside which sort a given update was, so the working rule is the same every time: after any CS2 update, assume the server needs to update too and check, rather than waiting to see whether someone complains.

Confirm it is a version problem first#

Before running anything, spend a minute proving the diagnosis. A server that is simply unreachable looks the same from the player's side as an out-of-date one, and the fixes are completely different.

  1. Look at the server console while a player tries to join. If the server prints a line about needing a restart for the latest update, you have your answer. If nothing at all appears when they try, packets are not arriving and this is a network problem, covered in the connect-errors post linked above.
  2. Check what the server says its version is. Type version into the server console. It prints the server's own build information. Exact fields differ between builds, so read it as "which build am I on", not as a fixed format.
  3. Check what the current build is. Valve's Counter-Strike news page and the update notes for CS2 on Steam give the date and the version of the latest patch. Compare the date of your server's last update with the date of the latest patch.
  4. Ask an affected player for their version. In the game, the version is shown in the settings or the console version output on the client. If theirs is newer than the server's, the server is behind.

There is also a file on disk that records the build. In a CS2 install the folder game/csgo/ contains steam.inf, a plain text file holding the build and patch version the install believes it is on. Opening it is the quickest offline check, and it is how you tell later whether SteamCMD really changed anything:

bash
$ cat /home/cs2/server/game/csgo/steam.inf

The exact keys in that file have changed between Valve releases, so do not script against one specific line. What you want is a before-and-after comparison: look at the version fields before the update and after, and they should differ if there was an update to apply.

The fix: update the install and restart#

On your own Linux machine, with the server stopped, the update is the install command run again. SteamCMD compares the installed build with the current one and downloads only what changed.

bash
$ sudo systemctl stop cs2$ steamcmd +force_install_dir /home/cs2/server \    +login anonymous +app_update 730 validate +quit$ sudo systemctl start cs2

Four details decide whether this works:

  • Stop the server first. Updating files under a running server is how installs end up half-patched. A clean stop also lets plugins write their data.
  • Put `+force_install_dir` before `+login`. In current SteamCMD builds an +force_install_dir placed after +login can be ignored with a warning, and SteamCMD then installs a fresh copy in its default location while your service keeps starting the old folder. This is the single most common reason for "I updated and nothing changed".
  • Use the same folder every time. A typo in the path gives you a second, perfectly current install that nobody runs.
  • Run it as the user that owns the files. SteamCMD run as root against files owned by a cs2 user leaves root-owned files the server cannot overwrite next time, and a later update fails half-way. If you ever did this, fix ownership with chown -R before the next run.

App id 730 is the one used for the CS2 dedicated server at the time of writing, and anonymous login works for it. Valve has changed things around this before (early in CS2's life the server needed a different login), so if SteamCMD prints a login or app error, check Valve's current dedicated server documentation before debugging anything else. The install itself is described in Counter-Strike 2 server setup and config, and SteamCMD explained covers app ids and branches.

Once started, check the result in three places: the version command in the console, the steam.inf file from earlier, and, decisively, a real client joining by connect <ip>:27015.

What validate does here

validate checks every installed file against Valve's manifest and redownloads anything different. For a game install of this size that is slow, and it is not needed on every routine update. But it is the right tool when an update was interrupted, the disk filled up halfway, or the server will not start after patching. It also overwrites files you changed inside the install folder that are part of the game's manifest, so keep your own edits (such as server.cfg and anything under addons/) in files that are not Valve's. Those two folders are not overwritten by a normal update, but a script you edited in place inside Valve's own directories is.

If you take one habit from this section: use plain +app_update 730 for routine updates and +app_update 730 validate when something looks wrong. Automating game server updates goes into that trade-off in more detail.

SteamCMD says "up to date" but the server is still old#

This is the genuinely confusing case, and it has a short list of real causes.

SymptomWhat is going on
"Already up to date" but players are refusedYou updated a different folder than the one that runs
Update ran, version unchangedThe service starts an older copy or a different launcher
Update fails or stallsDisk full, or interrupted download
Server updated, players still refusedPlayers are on a different branch, or plugins failed

Take them in turn.

The wrong folder. Find out which binary is actually running before trusting any path. On Linux, ps aux | grep cs2 shows the command line and the working directory can be read from /proc/<pid>/cwd. If that path is not the one in your +force_install_dir, you have two installs. Update the one that runs, or change the service to start the current one and remove the stale copy.

A wrapper or egg that overrides the update. Many setups start the server through a script that decides whether to run SteamCMD. If that script has its own update switch turned off, the command you ran by hand updated the files, but the next start of the wrapper may validate or restore something else. Read the start script rather than guessing.

Content servers lag behind the announcement. Occasionally the news post appears before every Steam content server has the new build. SteamCMD then reports no update available even though players have one. This usually clears within a short time; run the update again later, and use app_info_print if you want to see what Steam currently offers for the public branch:

bash
$ steamcmd +login anonymous +app_info_update 1 +app_info_print 730 +quit

That prints a long block of data; look for the public branch and its buildid. Treat it as a way to compare two numbers, not as something to parse.

A cached or stale app info. SteamCMD keeps local app information. Running with +app_info_update 1 as above, or deleting the app manifest for the app inside the install's steamapps folder and running the update again, forces a fresh look. Only do the manifest deletion with the server stopped, and expect the next run to take as long as a validate.

Disk space. An update needs room to download before it replaces files. A server on a nearly full disk can fail partway and leave an install that cannot start, as the setup post warns. Free some space and run the update again with validate. On a panel host the disk graph on the Console tab shows how close you are to the limit of the plan.

A beta branch. If you ever installed with -beta <name>, SteamCMD keeps following that branch, and the server will not match players on the public build. Check what you used and, if you want the normal release, run the update without a -beta argument. CS2 has had opt-in test branches on the client side too, so a small group of players on a test build and everyone else on the release build is a real possibility; ask the person who cannot join which branch their game is on.

Updating on a panel host#

On a panel such as Pterodactyl the SteamCMD step is not something you type; it is part of how the server starts, and the details depend on the template the host uses. Two things are common. Some templates run an update every time the server starts if a variable allows it, in which case a plain restart after a patch is the update. Others install once and update only on a reinstall or when you trigger an update yourself. Look at the Startup tab for a variable named something like auto update; if it exists and is off, switching it on and restarting is the fix. If you find nothing there, ask your host.

On RE:NODE, the Counter-Strike 2 server plans use the panel's usual tabs: the Console tab shows the live unfiltered output, so you can watch the update run and read the version line; the Startup tab holds the launch variables; Restart sends a clean stop before the start. The install waits on the Setup tab for your Steam game-server token, so a brand-new server will not be running until that is entered. We cannot say in advance which Startup variable controls the update step on the CS2 template, so check the Startup tab on your own server, and if you cannot see how to force an update, open a ticket from the panel and ask; support reaches all staff and you can attach a screenshot of the console.

Your token is not affected by an update. The game server login token stays tied to the account that created it, so you do not need a new one after a patch. If the server also starts to misbehave on registration after updating, the cause is a separate one, and CS2 server not showing in browser walks through it.

When the server is current but players still cannot join#

You updated, version shows the new build, and people are still refused or kicked. Work through these before blaming the update again.

  1. Plugins failed to load. Metamod and CounterStrikeSharp hook into engine internals, and a CS2 patch can break them until their authors release a fix. A server that starts, then crashes or kicks players in a loop, is usually a plugin problem on patch day. Disable the plugins to test, as described in CS2 plugins with Metamod and CounterStrikeSharp, and see what to do when a mod update breaks for the general routine. Metamod in particular is often patched into gameinfo.gi, and a Valve update can overwrite that file, which silently switches Metamod off. If your plugins vanished after an update, check game/csgo/gameinfo.gi first.
  2. The client is the older side. Ask the player to restart Steam, let it finish any pending download and verify game files.
  3. Workshop maps need updating too. A workshop map that was updated by its author after the patch may fail to load or differ between the server and clients. CS2 workshop maps and collections covers that side.
  4. You are not reaching the server at all. The message looks like a version problem only if the server answered. "Connection failed" with nothing in the server console is a network problem.
  5. Master server and listing delays. After a restart a server can take a while to reappear in the community browser; joining by IP works sooner. Test with connect before concluding the update did not work.

Make the next patch painless#

The goal is that nobody has to notice. A routine of four parts is enough for most servers.

Update on a restart, restart on a schedule. If your setup updates whenever the server starts, a daily restart at a quiet hour turns every patch into an overnight non-event. On a self-run Linux box that is a cron entry that stops the service, runs the update and starts it. On a panel host it is a schedule: the Schedules tab on RE:NODE takes a cron expression and ordered tasks with delays, and the tasks can be a console command, a backup or a power action.

bash
# crontab -e, 05:00 daily: stop, update, start0 5 * * * systemctl stop cs2 && \  sudo -u cs2 steamcmd +force_install_dir /home/cs2/server \  +login anonymous +app_update 730 +quit && systemctl start cs2

That example assumes a cs2 systemd unit and SteamCMD on the path; adapt names to your own layout and test it by hand once before trusting it at 05:00.

Back up before the update, not after. A patch can change what a config does, and an update that goes wrong is much easier to undo with a copy of cfg/ and addons/ from the day before. On a panel, put a backup task ahead of the restart in the same schedule, so the order is backup, then restart. Backup slots on every plan are limited, so rotate rather than collecting them; game server backup strategy covers a sensible rhythm.

Do not auto-update a server that depends on plugins. If you run Metamod and CounterStrikeSharp plugins, an update on every restart means an update the moment a patch lands, before plugin authors have had time to respond. For those servers, update by hand after you have checked that your plugins have a compatible release, and accept that players on the new build cannot join in the meantime. It is a real cost, and it is the price of a modded server.

Keep a person responsible. Somebody, whether that is you or a co-admin, looks at the server version after each Valve update. Five minutes after the news post is cheaper than a Discord full of complaints.

What not to do#

A few habits make this worse and are worth naming:

  • Do not delete the whole install and start from scratch as the first move. The configs and plugins you set up are in that folder, and a validated update fixes the same problem without losing them.
  • Do not copy the `game` folder from a friend's server. Mixed builds produce exactly the mismatch you are trying to fix, plus file ownership problems.
  • Do not rely on `-autoupdate`. That launch option comes from CS:GO and older Source servers. Whether CS2 honours an equivalent is something to confirm against Valve's current dedicated server documentation, and the safe approach is a routine that does not need it.
  • Do not change the port to "fix" it. A version refusal has nothing to do with the port, and moving it only breaks the address everyone saved.
  • Do not run SteamCMD against a running server to save thirty seconds. The saving disappears the first time it half-patches.

FAQ#

Why does my CS2 server say it needs to be restarted for the latest update?

Valve released a patch, and the game on players' machines is newer than the server's files. The message means the server noticed the mismatch. Stop it, update with SteamCMD app 730 (or restart with the update switch on, on a panel), and start it again.

How do I update a CS2 dedicated server?

Stop it, run steamcmd +force_install_dir <folder> +login anonymous +app_update 730 validate +quit as the user that owns the folder, then start it. Put +force_install_dir before +login, and use the same folder as the one your service runs.

Why does SteamCMD say the server is up to date when players cannot join?

Usually it updated a different folder from the one that is running, or Steam's content servers have not caught up with the announcement yet. Check which folder the running process uses, compare steam.inf before and after, and try again after a short wait.

Do I need a new game server login token after an update?

No. The token stays valid across game updates. It is only replaced if it was revoked or you made it for the wrong app.

Can I stop my server updating so I can keep my plugins?

You can leave it on its current build, but then players who have updated cannot join it, because their game updates whether you like it or not. There is no supported way for players to stay on an old build, so the realistic options are to update the server when plugins are ready or to accept that the server is closed to updated players until they are.

Will an update wipe my config or plugins?

A normal update replaces Valve's files and leaves server.cfg and the plugin folders you added. The exception is a file inside Valve's own directories that you edited in place, such as gameinfo.gi when Metamod is installed; check it after each patch.

Was this helpful?