Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
they show up like this:
http://cache1-ams1.steamcontent.com/depot/244850/manifest/724930808235308179/5
http://cache4-ams1.steamcontent.com/depot/228983/manifest/8124929965194586177/5
http://cache4-ams1.steamcontent.com/depot/244850/manifest/6188204259757791433/5
all come back as so unauthorized. Should it be looking at those in https instead? why would it be unauthorized? It looks like Steam itself decided to use http instead of https.
edit: nope all steam ones are 401, Ineed glasses
Maybe there's a hint on what's wrong.
A HTTP 401 Unauthorized is certainly one. Maybe your local "Token" (I'm not sure how Steam does authorization) is expired and there are problems when refreshing it :x
// EDIT
Can you see the payload of the requests being sent to steam through Wireshark? There should be some kind of authorization token in it usally in the HTTP Headers, which is mostly just base64 encoded. You could decode it here https://www.base64decode.org/ and maybe there's a expire date in it or smth o.o
FYI: When calling the URLs from a browser or any other HTTP client, you will always get a 401, because you are missing the authentication information.
GET /depot/440901/manifest/4834859109920406060/5 HTTP/1.1
Host: cache1-ams1.steamcontent.com
Accept: text/html,*/*;q=0.9
accept-encoding: gzip,identity,*;q=0
accept-charset: ISO-8859-1,utf-8,*;q=0.7
user-agent: Valve/Steam HTTP Client 1.0
HTTP/1.1 401 Unauthorized
Server: nginx/1.21.5
Date: Sun, 03 Jul 2022 14:01:17 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 98
Connection: keep-alive
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Cache-Control: no-cache,must-revalidate
Pragma: no-cache
<html>
<head>
<title>401 Unauthorized</title>
</head>
<body>
<h1>Unauthorized</h1>
</body>
</html>
*<00><00><00><00><00><00><00><00><00><00><00><00><00><00><00>: type NBSTAT, class IN
netbios? wierd.
You can start Steam with a "-tcp" flag to use TCP instead of UDP. This might help, but can cause some other problems :x
You found this in the log file? This seems like a virtual interface, but my knowledge about this stuff is very rusty and I'll need more context to judge what's going on with that: https://askubuntu.com/questions/862333/what-does-hwaddr-value-of-00-00-00-would-mean
udp query:
Flags: 0x8183 Standard query response, No such name
182.25.185.in-addr.arpa: type SOA, class IN, mname ns1.valvesoftware.com
and thats not a typo, its missing a 4 in front on the querry.
4.182.25.185.in-addr.arpa: type PTR, class IN
oh no I was just watching wireshark as steam tried to auto update some of my games.
Did you try the "-tcp" option yet?
edit: well it does but I never turned it on.
You can add "-tcp" to your Steam Windows link in the properties of it. Tha target should look like this then:
ipconfig /flushdns
cmd /min /C "set __COMPAT_LAYER=RUNASINVOKER && start "" .\steam.exe -tcp -nochatui -nofriendsui -console -no-cef-sandbox -dev -condebug -toconsole -noverifyfiles -nobootstrapupdate -skipinitialbootstrap -norepairfiles -overridepackageurl"
it keeps steam from trying to run as admin.
ok i see some old stuf in there that might be problematic now that I look at it again