Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Просто жди, от нас ничего не зависит.
i checked:
steam artwork -> worked
gamehub artwork -> worked
screenshot -> worked
guide images -> worked
in-client and in-browser.
discovered issue while testing: wrong dns cache
my dns cache is fully self-controlled and everything is highly up2date and gets purged on a regular basis to a backup dns for emergency. the backup contained the garbage everyone is talking about. so there was a wrong resolve in the past.
solutions:
1.
set 1.1.1.1 as your primary dns or the one of google, everywhere, not just on your computer and then power cycle everything.
if "DNS" are just some letters in an alphabet soup for you, leave that part out and just power cycle everything. power cycle means you unplug the power from everything and then you plug everything back in. for end devices a reboot is enough. but modems, routers, switches, hubs, the "wifi-thing" power off, power on.
2.
hosts file[en.wikipedia.org] add:
208.64.201.119 ufs0099 dot steamcontent dot com (replace dot with .)
208.64.201.119 steam-0298
one of these should do it. i couldn't discover if "steam-0298" was a wrong relay resolve for "ufs0099 dot steamcontent dot com" which is the current name for the ugc upload server.
the IP is well known, you will find it in years old posts, it never changed.
this solution might need a reboot of the device.
only the first solution can be done and left alone, unlikely that the big dns will shut down.
the 2nd one should be reverted as soon as possible when the main consensus on this problem is considered being fixed.
if anything in this post requires you to have a detailed step-by-step instruction, keep your fiddles away and wait until it fixes itself.
https://vk.com/moshcelt?w=wall315117085_4278