Prêt à jouer ?
Ton serveur est
à un clic.
Choisis ton jeu, sélectionne un plan et joue en moins de 60 secondes. Zéro lag, zéro excuse.
Wouf ! C'est parti !
Nouveau : Profitez de 20 % de réduction le premier mois — Code BRUCE20
Prêt à jouer ?
Choisis ton jeu, sélectionne un plan et joue en moins de 60 secondes. Zéro lag, zéro excuse.
Wouf ! C'est parti !
Your panel says Installing. It has said Installing for twenty minutes, maybe an hour, maybe since last night. Nothing in the console, no error, no progress bar that means anything. If your CS2 server is stuck on installing, the cause is almost always disk space, and the reason it is so hard to diagnose is that nothing actually tells you that.
Here is what is happening under the hood, how to confirm it in about two minutes, and what to do about it.
When you deploy a CS2 server on Pelican, Pterodactyl, or most panel-based hosts, provisioning happens in two stages. The container is created in seconds. Then an install script runs, and that script calls SteamCMD to download app 730, the Counter-Strike 2 dedicated server.
That second stage is the one you are staring at. The panel has no visibility into SteamCMD's progress, so it displays a single flat status for the entire download. A container that spins up in under a minute can then sit in Installing for a long time, and that is normal on a first install.
What is not normal is Installing that never ends.
This is where most people get burned, and the published numbers do not agree with each other:
| Source | Figure |
|---|---|
| K4ryuu CS2-Egg documentation | 40 GB or more recommended |
| joedwards32 CS2 Docker image | 60 GB minimum for the container |
| Our own measurement, live customer server | 68 to 70 GB after a completed install |
We put our own number in that table because we went and looked at a real server rather than repeating a figure. After a completed install, CS2 occupies roughly 70 GB. Not 40.
The spread exists partly because the game keeps growing, partly because some counts exclude workshop content and logs, and partly because people quote the client install size rather than the server one. Treat any single figure you find online with suspicion, including this one. Measure your own.
Here is the part that catches people who did the arithmetic and still ran out of space.
SteamCMD does not write files neatly into their final position as it goes. Downloaded chunks land in a staging directory first, then get moved into place. For part of the process you are holding staged data and placed data at the same time, so the peak disk usage during the install is higher than the size of the finished installation.
The practical consequence: a container sized at exactly 70 GB, which is precisely the size of the finished server, can still fail partway through. The quota is not measured against the end state, it is measured continuously, and the middle of the process is the expensive part.
This is why "how big is CS2" is the wrong question to size a plan on. The right question is how much room the download needs at its peak.
Two minutes, in this order:
1. Look at the disk meter in your panel. If it is pinned at 100 percent, or sitting exactly at your plan's limit, you have your answer. A quota reading 30 GB of 30 GB is not a coincidence during a 70 GB download.
2. Read the install log, not the console. Most panels keep install output separate from the game console. You are looking for one of these:
Error! App '730' state is 0x202 after update job.
ERROR! Failed to install app '730' (Disk write failure)
No space left on device
That first line is the one most people end up searching for. State 0x202 is SteamCMD telling you the app failed to reach a valid installed state, and on a size-capped container the reason is almost always that it ran out of room.
3. Check whether the status ever changes. A genuine download progresses, even slowly. A container sitting at Installing for several hours with a full disk meter is not downloading, it is failing and retrying.
If you control the allocation: raise the disk limit with real headroom over the finished size, then trigger a reinstall. Do not simply restart. A partial download needs to be cleared or completed, and a reinstall handles that.
If you are on a plan with a hard disk cap: this is the uncomfortable one. If your host allocates 30 GB or 50 GB and will not raise it, no amount of troubleshooting fixes it. The files do not fit. You need a larger plan or a different host.
Before you reinstall, save your configs. Your server.cfg, your workshop collection ID, your RCON password, and any plugin configuration should come off the server first. A reinstall re-downloads game files, and it is easy to lose an evening of setup you did not back up.
Mind your auto-update behaviour. Most CS2 eggs expose a variable that controls whether the server checks for updates on every boot. The exact name varies by egg, so check your own panel rather than copying one from a guide. Ours is AUTO_UPDATE. Leaving update checks on is usually correct, but on a disk that is already tight it gives you one more chance to run out of room at exactly the wrong moment.
Disk is the common answer, not the only one. If your meter looks healthy:
If your CS2 server is stuck on installing, check the disk meter before anything else. The finished files run around 70 GB, the download peaks higher than that, and a container sized for a Minecraft world will never finish no matter how many times you restart it.
Once it is up and you want the rest of the picture, tick rate, workshop collections, GOTV and the like, our CS2 server hosting guide covers it. And if you would rather not think about disk quotas at all, our CS2 plans ship with 85 GB of NVMe as standard, roughly 70 GB of game files plus 15 GB of working room, on every tier including the cheapest.
Related posts on BruceNode: