How to Troubleshoot CS 1.6 Server Startup Errors
A direct-lookup guide for the most common CS 1.6 server startup failures — error messages, causes, and exactly how to fix each one.
How to Read Startup Errors
Run the server from a terminal directly (not as a background service) so you see all output. Use hlds_run with -console:
./hlds_run -game cstrike -console -port 27015 +maxplayers 20 +map de_dust2
Read everything the server prints before it stops or crashes. The error is almost always in the last few lines before the process exits.
Error: Segmentation Fault (Crash on Startup)
Cause: Missing 32-bit libraries on a 64-bit Linux system.
Fix:
sudo apt update
sudo apt install lib32gcc-s1 lib32stdc++6
After installing, try launching again. This is the most common startup failure on modern Linux.
Error: FATAL ERROR: Could not establish connection to Steam servers
Cause: Outbound firewall rules are blocking the server from connecting to Steam's authentication servers.
Fix: Ensure these outbound UDP ports are open:
27015— game port27020— HLTV/SourceTV27005— client port26900— Steam auth
Check your cloud provider's security group or host firewall rules. On Linux with UFW:
sudo ufw allow out 27015/udp
sudo ufw allow out 27020/udp
sudo ufw allow out 27005/udp
sudo ufw allow out 26900/udp
Error: Couldn't allocate dedicated server UDP port
Cause: Port 27015 is already in use by another process.
Fix: Find and stop what's using the port:
ss -ulnp | grep 27015
The output shows the process ID. Either stop that process or change your server to a different port with -port 27016 (or any unused port).
Error: Failed to load gamedll or Couldn't find game DLL
Cause: cstrike/liblist.gam has a wrong path for the game DLL. Most commonly happens after installing Metamod — the path to metamod_i386.so is incorrect.
Fix: Open cstrike/liblist.gam and check the gamedll_linux line. Verify:
- The path is relative to the
cstrike/directory - The filename exactly matches the file on disk (case-sensitive)
- The file actually exists at that path
ls -la /home/gameserver/hlds/cstrike/addons/metamod/dlls/
The filename must match exactly, including the .so extension.
Error: [AMXX] Module not found: <name>
Cause: A plugin requires an AMX module that isn't installed or isn't loaded.
Fix: Download the AMX Mod X extras package from amxmodx.org. Extract it and enable the required module in cstrike/addons/amxmodx/configs/modules.ini by uncommenting its line.
Server Not Showing in Server Browser
Cause: sv_lan 1 is set, which hides the server from the internet master server list.
Fix: In cstrike/server.cfg:
sv_lan 0
Reload with exec server.cfg or restart. Also verify that inbound UDP port 27015 is open in your firewall.
All Players Instantly Get "You Have Been Banned"
Cause: cstrike/banned.cfg contains banid 0 0:0:0 which bans everyone including all Steam IDs.
Fix: Open cstrike/banned.cfg in a text editor. Find and delete any line reading:
banid 0 0:0:0
Save the file, then in the server console:
exec banned.cfg
Or restart the server.
VAC Secure Mode Disabled
Cause: The server failed to authenticate with Steam. Usually a firewall issue (see "Could not establish connection to Steam servers" above), or the server is starting faster than it can reach Steam's auth servers.
Fix: Check outbound firewall rules first. If the firewall is open, try restarting — occasionally this resolves on its own. If it persists, check that your game server's IP isn't on a shared hosting range that Steam has flagged.
Metamod Shows (failed) in meta list
Cause: AMX (or another Metamod plugin) failed to load. The actual error is in the AMX log.
Fix: Check cstrike/addons/amxmodx/logs/ for today's log file. The specific load failure with reason will be there.