steamclient.so Not Found" on a Linux Game Server: How to Fix It

When a Linux dedicated server prints dlopen failed trying to load: /home/steam/.steam/sdk64/steamclient.so or SteamAPI_Init() failed, it is looking for Steam's client library in a fixed place and not finding it there. SteamCMD ships the file, it is just in SteamCMD's folder instead. Create ~/.steam/sdk64 (and sdk32 for 32 bit servers) for the user that runs the server, and link steamclient.so from SteamCMD's linux64 and linux32 folders into them. The server then starts and talks to Steam normally.

What the errors look like

You may see one or several of these near the top of the server log:

dlopen failed trying to load:
/home/steam/.steam/sdk64/steamclient.so
with error:
/home/steam/.steam/sdk64/steamclient.so: cannot open shared object file: No such file or directory
[S_API] SteamAPI_Init(): Sys_LoadModule failed to load: /home/steam/.steam/sdk64/steamclient.so
[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.

Some servers keep running after this and simply never appear in the server browser or reject logins. Others, like many Unreal Engine and Unity servers, exit straight away.

Why it happens

steamclient.so is the piece of Steam that lets a server register with Steam, check player tickets and show up in the server list. The Steamworks API in the game server looks for it in ~/.steam/sdk64/ (64 bit) or ~/.steam/sdk32/ (32 bit), relative to the home folder of the user running the server. A full Steam client creates those folders. A machine with only SteamCMD does not.

Fix 1: link the files from SteamCMD

Run these as the user that runs the server, not root. Adjust the path if SteamCMD lives somewhere other than ~/steamcmd.

mkdir -p ~/.steam/sdk64 ~/.steam/sdk32
ln -sf ~/steamcmd/linux64/steamclient.so ~/.steam/sdk64/steamclient.so
ln -sf ~/steamcmd/linux32/steamclient.so ~/.steam/sdk32/steamclient.so

If you installed the Ubuntu or Debian steamcmd package, SteamCMD unpacks itself under the user's home instead. Find the files with:

find ~ -name steamclient.so 2>/dev/null

Then link whichever linux64/steamclient.so and linux32/steamclient.so it finds.

A symlink is better than a copy, because SteamCMD updates the file and the link follows it. A stale copy can cause odd problems after Steam updates.

Fix 2: the server expects the file next to itself

Some games look in their own folder or in a folder set by LD_LIBRARY_PATH first. Many servers ship their own copy, for example in a linux64 folder inside the install. If the error persists:

1. Look for steamclient.so in the server folder: find /home/steam/server -name steamclient.so.
2. If there is one, start the server with that folder in the library path:

export LD_LIBRARY_PATH=/home/steam/server/linux64:$LD_LIBRARY_PATH
./server_binary

Valheim's official Linux start script does exactly this with its own linux64 folder. 7 Days to Die and several Unity based servers behave the same way.

3. If there is none, copy SteamCMD's linux64/steamclient.so next to the server binary.

Fix 3: wrong ELF class

steamclient.so: wrong ELF class: ELFCLASS32

A 64 bit server found the 32 bit library, usually because the linux32 file was linked into sdk64. Point sdk64 at linux64/steamclient.so and sdk32 at linux32/steamclient.so. Check with:

file -L ~/.steam/sdk64/steamclient.so

It should say ELF 64-bit.

Fix 4: the server runs as a different user

The ~/.steam folder is per user. If you created the links as yourself but the server runs as steam through systemd or a panel, the server still cannot find them. Create them in the server user's home, or set HOME correctly in the service file. A missing HOME in a systemd unit can make the server look under /. Add this to the [Service] section if needed:

Environment=HOME=/home/steam

Fix 5: missing 32 bit libraries

32 bit servers (older Source games like Left 4 Dead 2, and SteamCMD itself) also need the 32 bit C library. On Debian and Ubuntu:

sudo dpkg --add-architecture i386
sudo apt update
sudo apt install lib32gcc-s1 lib32stdc++6

Without them you see errors like error while loading shared libraries: libstdc++.so.6 alongside or instead of the steamclient one.

Harmless messages you can ignore

Not every Steam line in the log is a problem:

• Setting breakpad minidump AppID = ... is crash reporting setup.
• Steam_SetMinidumpSteamID: Caching Steam ID is normal.
• [S_API FAIL] Tried to access Steam interface ... before SteamAPI_Init succeeded sometimes appears once at startup on servers that initialize Steam late, and can be ignored if the server then shows in the browser and players can join.

If the server starts and players can join, a one off warning is not worth chasing.

Checklist

1. Find the files with find ~ -name steamclient.so.
2. Link linux64 to ~/.steam/sdk64 and linux32 to ~/.steam/sdk32 for the server's user.
3. Check file -L reports the right bitness.
4. Set HOME and LD_LIBRARY_PATH in service files.
5. Install 32 bit libraries for 32 bit servers.

For a full walk through of a fresh Linux setup, see how to install SteamCMD on Linux.

No library hunting on a hosted server

A GamezServers server comes with the game installed and its Steam libraries in place, so you start from a working server with settings from the game's server template in the control panel and a live console to watch it boot. That goes for Source games like Team Fortress 2 and Garry's Mod as well as newer survival games.

FAQ

Where should steamclient.so be on Linux?

In ~/.steam/sdk64/steamclient.so for 64 bit servers and ~/.steam/sdk32/steamclient.so for 32 bit ones, in the home folder of the user that runs the server. Link them from SteamCMD's linux64 and linux32 folders.

Do I need the full Steam client on a Linux server?

No. SteamCMD includes steamclient.so. You only need to put it where the server looks.

Why does my server start but not show in the server list?

If Steam failed to initialize, the server may run without registering with Steam. Fix the steamclient error first, then check the query port.

Should I copy or symlink steamclient.so?

Symlink. SteamCMD updates its copy, and a link always points to the current file.