SteamAPI_Init(): Sys_LoadModule failed to load: [path]

There was an issue with dedicated servers not having the binaries necessary. This should now be fixed, but if you get this issue:

On Linux, copy /home/steam/.local/share/Steam/steamcmd/linux64/steamclient.so to /home/steam/.steam/sdk64/steamclient.so.

On Windows, copy steam_api64.dll from below into VeinServerDirectory/Vein/Binaries/Win64.

steam_api64.dll

You can find this file in any Steam install directory in Windows if you don’t want to trust this dll.

Log spam from LogOnlineSession EOS

Add the following to Engine.ini above:

[Core.Log]
LogOnlineSession=Warning
LogOnline=Warning

dlopen failed trying to load: (…)/.steam/sdk64/steamclient.so

This .so is in your steamcmd install directory. Mine was in ~/.local/share/Steam/steamcmd/linux64. Link them using:

ln -s /home/steam/.local/share/Steam/steamcmd/linux64 /home/steam/.steam/sdk64

dlopen failed trying to load:
/home/steam/.steam/sdk64/steamclient.so

Windows server doesn’t show up in the server browser, Steam Dedicated Server API failed to initialize in logs

You may need to run the server with elevated/admin permissions. We’re working on a fix.

Failed to get connection string for heartbeat: no IP & not running Steam Sockets P2P

This may not be an actual error. Make sure you see Gameserver logged on to Steam later, as well as some lines about a certificate at the bottom. If you see this, the error is inconsequential.

If you see this after Steam is done initializing, it means that Steam is failing to determine your game server’s IP.