Fixing SteamCMD 0x2 Errors

While trying to set up a 7 Days to Die dedicated server to play with friends, I hit a weird error in Steam. I was trying to run a command like this:

/usr/games/steamcmd +force_install_dir /home/steam/games/7dtd +login anonymous +app_update 294420 -validate +quit

That command is basically a one-liner to set a directory to install the game into, log in as the anonymous user and install the 7 Days To Die dedicated server (app ID 294420).

After running for a second trying to find the files to download from Steam's CDN, it would emit this message and then quit:

Error! App '294420' state is 0x2 after update job.

If you just want the TLDR, disable IPv6 on your server. Steam's update servers don't play nicely with IPv6.

To investigate, I went digging in Steam's logs with:

less ~/.steam/root/logs/content_log.txt

That log showed messages like this:

[2026-01-20 19:04:23] HTTPS (SteamCache,441) - cache2-den-iwst.steamcontent.com ([2607:dc0::5]:443 / [2607:dc0::5]:443, h
ost: cache2-den-iwst.steamcontent.com): cache2-den-iwst.steamcontent.com/depot/294422/manifest/8017012783762826089/5/8789
043405968245559 - received 0 (Invalid) HTTP response
[2026-01-20 19:04:23] HTTPS (SteamCache,441) - cache2-den-iwst.steamcontent.com ([2607:dc0::5]:443 / [2607:dc0::5]:443, h
ost: cache2-den-iwst.steamcontent.com): Closing connection
[2026-01-20 19:04:23] AppID 294420 update canceled : Failed downloading 1 manifests (Connection timeout)

After digging through Google on that error, I tracked down this bug report on a Valve GitHub repo. The short version of that bug is that the Valve update servers don't like IPv6, and they haven't done much with it.

I don't need IPv6 on my server, so I just disabled it globally with:

sudo sysctl --write net.ipv6.conf.all.disable_ipv6=1

If I wanted IPv6, I could re-enable it after Steam is done with:

sudo sysctl --write net.ipv6.conf.all.disable_ipv6=0

And Bob's your uncle, you're ready to roll.