Error index

The Call of Duty Linux dedicated server is a 32-bit binary and needs i386 runtime libraries, including the long-obsolete libstdc++5, on a modern 64-bit host.

The client sent a connection request and got nothing back. Almost always a UDP reachability problem between client and server, not a game configuration problem.

The server runs and is directly joinable, but does not show in the master list. Usually the master server itself, dedicated mode, or a NAT that rewrites the heartbeat source address.

The client and server are on different patch levels. Call of Duty patch versions use different network protocol numbers and cannot cross-connect.

The key check failed at connect. On the classic Call of Duty titles this is usually key authentication infrastructure rather than the key itself.

The engine cannot find the stock game paks. Nearly always fs_basepath pointing at the wrong directory, or paks missing from the gamedir.

The engine found the paks but could not load the game module. Missing 32-bit libraries, a missing game.mp.i386.so, or a mismatched patch level.

The server's sv_pure checksum audit rejected the client's loaded paks. On Call of Duty 1 patch 1.1 this fires against innocent clients because of an engine bug.

PunkBuster drops legitimate players on the classic Call of Duty titles because its master infrastructure is unmaintained. On CoD4 the answer is to run CoD4X and disable PunkBuster.

The client stopped receiving snapshots. Packet loss, rate limits, or a server hitching hard enough to miss its send window.

Usually flood protection rather than a wrong password. Two rcon commands within about 500 ms collapse and the second returns this, indistinguishable from an authentication failure.

A mod exhausted the per-player HUD element pool. Call of Duty 1 allows 31 HUD entities per player.

A GSC script failed to compile and the server shut down. The line above the banner names the file and the reason.