Is SteamCMD down? Cant update files.

[Dragonvarine]

I'm trying to make a server with friends (Ark server). But running steamcmd.exe comes up with "keyvalues error: loadfrombuffer: missing". At the end it says "[----] !!! Fatal Error: Steam needs to be online to update. Please confirm your network connection and try again." Tried everything and cannot find a single thing related to this error and steamcmd.

Note: I'm talking about SteamCMD, not Steam itself.

[Lesona]

Check what version it is - I'm having a similar issue.

[aiusepsi]

This might sound daft, but change your DNS server from the default to another one, for example 1.1.1.1 or 8.8.8.8.

It looks like SteamCMD first tries to get the update manifest from a misspelled URL, cdn.akamai.steamstaticcom[cdn.akamai.steamstaticcom] rather than cdn.akamai.steamstatic.com, and a proper DNS server at this point would say "that doesn't exist" and then SteamCMD would try a different URL.

The default Virgin Media DNS server instead reports that it does exist, and sends the IP of a webserver belonging to Virgin, so that it can send you a search page. SteamCMD is not expecting this so it falls over.

Using a different DNS server fixes this. What's blowing my mind is that the SteamCMD installer has a timestamp from 2013, so this first install experience has been broken for years. Wow.

[76561199144859448]

^^

[Dragonvarine]

aiusepsi の投稿を引用：

This might sound daft, but change your DNS server from the default to another one, for example 1.1.1.1 or 8.8.8.8.

It looks like SteamCMD first tries to get the update manifest from a misspelled URL, cdn.akamai.steamstaticcom[cdn.akamai.steamstaticcom] rather than cdn.akamai.steamstatic.com, and a proper DNS server at this point would say "that doesn't exist" and then SteamCMD would try a different URL.

The default Virgin Media DNS server instead reports that it does exist, and sends the IP of a webserver belonging to Virgin, so that it can send you a search page. SteamCMD is not expecting this so it falls over.

Using a different DNS server fixes this. What's blowing my mind is that the SteamCMD installer has a timestamp from 2013, so this first install experience has been broken for years. Wow.

Wow, I will try this now then. Sounds ridiculous

[aiusepsi]

Ah, I was slightly wrong in a detail, the bad URL isn't baked into the application, which means this hasn't been broken for years.

SteamCMD first tries to grab the update manifest from: http://client-download.steampowered.com/client/steam_cmd_win32 but is HTTP-redirected to http://cdn.akamai.steamstaticcom/client/steam_cmd_win32 which is typo'd, and so should fail. That typo is probably a recent mistake.

If it does fail, it tries again with http://media.steampowered.com/client/steam_cmd_win32 which does work.

But, Virgin Media's DNS servers hijack the typo'd cdn.akamai.steamstaticcom URL, and reply with a web page with a 200 OK status code, which is only supposed to be used when the request was properly replied to. SteamCMD then thinks everything is fine, and tries to interpret the webpage as the client update manifest, and blows up.

So yeh: two things at fault here:

1. client-download.steampowered.com redirected to a typo'd URL
2. Virgin Media hijacking typo'd URLs and replying with a HTTP 200 OK status code.

The last one is pretty staggering. Like, at least reply with a 404 code, bloody hell, Virgin. Anyway, using a different DNS server works around it because it means you get around Virgin squatting typo'd URLs.

[Dragonvarine]

aiusepsi の投稿を引用：

Ah, I was slightly wrong in a detail, the bad URL isn't baked into the application, which means this hasn't been broken for years.

SteamCMD first tries to grab the update manifest from: http://client-download.steampowered.com/client/steam_cmd_win32 but is HTTP-redirected to http://cdn.akamai.steamstaticcom/client/steam_cmd_win32 which is typo'd, and so should fail. That typo is probably a recent mistake.

If it does fail, it tries again with http://media.steampowered.com/client/steam_cmd_win32 which does work.

But, Virgin Media's DNS servers hijack the typo'd cdn.akamai.steamstaticcom URL, and reply with a web page with a 200 OK status code, which is only supposed to be used when the request was properly replied to. SteamCMD then thinks everything is fine, and tries to interpret the webpage as the client update manifest, and blows up.

So yeh: two things at fault here:

1. client-download.steampowered.com redirected to a typo'd URL
2. Virgin Media hijacking typo'd URLs and replying with a HTTP 200 OK status code.

The last one is pretty staggering. Like, at least reply with a 404 code, bloody hell, Virgin. Anyway, using a different DNS server works around it because it means you get around Virgin squatting typo'd URLs.

Yeah because SteamCMD worked before, this seemed recent (2021 type recent). However Im still getting an error. The second link does work when I type it in, and I get a file called steam_cmd_win32 (literally type file). But not sure what to do with it. But I changed the DNS and still get the virgin media http 200 "error".

[Nangz]

I'm also having this issue. Steamcmd comes up with various errors a previously mentioned instead of updating and installing correctly. Any workaround as yet?

[SilentPantz]

Same here. Changed my DNS to google's (8.8.8.8). Would be nice if there was a way to manually change which URL is used for updates.

[benhough1]

Is there a solution yet?

[Dragonvarine]

benhough1 の投稿を引用：

Is there a solution yet?

Sadly nope

[Merlyn]

It is also possible to fix this issue by modifying your hosts file and add the following line:

23.202.229.179 client-download.steampowered.com

This will makes your computer use the IP for media.steampowered.com when trying to reach client-download.steampowered.com. I've tested and it works, but I don't know if this will introduce unintended consequences with anything else, try at your own risk.

[Dragonvarine]

Merlyn の投稿を引用：

It is also possible to fix this issue by modifying your hosts file and add the following line:

23.202.229.179 client-download.steampowered.com

This will makes your computer use the IP for media.steampowered.com when trying to reach client-download.steampowered.com. I've tested and it works, but I don't know if this will introduce unintended consequences with anything else, try at your own risk.

Thanks for the solution even despite how old this post is. I will try it out.

[zzz]

Merlyn の投稿を引用：

It is also possible to fix this issue by modifying your hosts file and add the following line:

23.202.229.179 client-download.steampowered.com

This will makes your computer use the IP for media.steampowered.com when trying to reach client-download.steampowered.com. I've tested and it works, but I don't know if this will introduce unintended consequences with anything else, try at your own risk.

THIS WORKS! thank you

[wel85]

I have the same error steam cmd to create conan server could someone explain better?

[cinemind]

Dragonvarine の投稿を引用：

Merlyn の投稿を引用：

It is also possible to fix this issue by modifying your hosts file and add the following line:

23.202.229.179 client-download.steampowered.com

This will makes your computer use the IP for media.steampowered.com when trying to reach client-download.steampowered.com. I've tested and it works, but I don't know if this will introduce unintended consequences with anything else, try at your own risk.

Thanks for the solution even despite how old this post is. I will try it out.

this also worked for me, thank you so much!!