Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
Hozzászólási szabályok és irányelvek
Hozzászólás jelentése
Just in case, it violates both Steam SSA and Google TOS:
Source: https://store.steampowered.com/subscriber_agreement
Source: https://policies.google.com/terms
Instead, you might want to try to find an actual issue source and solution, and in such case, is it possible that something local interferes with the process (e.g. security solution like an anti-virus, firewall, browser extension)?
Have you tried reproducing the issue in in both a different general browser (e.g. Google Chrome) and the Steam desktop launcher/client? If so, does the network has any Virtual Private Network (VPN) applied? If it does, have you tried to add an exception or temporarily disable it? Does the same issue appear on another machine if available?
Is it possible that the the issue is associated with the current IP address which is marked suspicious on either Steam or Google end? Have you tried a different network in the same city/region (e.g. cellular or public but trustful enough Wi-Fi) with an actually different IP address? Please try using a general browser with incognito mode enabled if possible in order to try to decrease possible local issues like browser extension malfunctions.
Have you checked out Steam launcher/client and browser network/general logs (e.g. ".../Steam/logs/connection_log.txt" file and browser - DevTools or similar)? Do all captcha related requests succeed?
Have you tested the issue in a new temporary environment (either virtual or not)?
The following web page may be used for verifying a working captcha in your network I believe at least for a short period while investigating: https://google.com/recaptcha/api2/demo
Currently, Steam uses an outsourced challenge–response test service - Google ReCaptcha. The service has various security components applied to the solution in addition to Turing tests, including traffic analyzes, local environment tests, public data references (e.g. spam/VPN/restricted network nodes). Since the actual verification process is not disclosed by Google for security reasons, the issue may be interrelated with various circumstances, and an initial manual search for a solution by a process of elimination should help find the issue source.
Source: https://support.google.com/websearch/thread/121453069 [modified, formatted]
Source: https://developers.google.com/recaptcha/docs/versions
Source: https://cloud.google.com/recaptcha-enterprise/docs/overview
Source: https://services.google.com/fh/files/misc/owasp_handbook_again.pdf
It's worth to mention that some web pages on Steam may include a visually hidden captcha (e.g. Google ReCaptcha v3) as an additional request verification step to eliminate possible automation, hence why network and environment may affect the procedure, too.
Please have a pleasant time and stay safe!
Related:
https://google.com/chrome/cleanup-tool/index.html
https://developers.google.com/recaptcha/docs/v3
https://cloud.google.com/recaptcha-enterprise/docs/compare-versions
The specific issue this topic was opened about has long been fixed. Using alternative browsers didn't help back then. It's possible that there is another issue again affecting chrome specifically, but then there has to be another topic about it, because it's not the same.
I ended up having this issue, and nothing I tried in the comments worked for me. It turned out to be a browser issue. I switched which Browser I was using, and it worked. Not saying peoples solutions didn't work for anyone else, I am just saying what worked for me.
Cool, I'm glad switching browser solved the issue you were having. My point was, that probably a new topic would have been more appropriate as this is an old one, but since you have also found this searching for solutions, I guess it's fine.
Btw the first thing I try if something doesn't work on a page is trying it in incognito mode (because it means a clear cache), then I try another browser. Popularizing this approach can be useful, but when the issue is entirely on server side, there is absolutely nothing you can do about it, and unfortunately that also happens sometime.
Either clear cache and cookies on said browser. Or try using another browser. If using any extension ensure that not causing a problems., and lastly ensure not blocking things for the captcha.
And multiple people with this problem have responded that this does not work. We have tried different browsers (including Edge), different devices, cleared caches and disabled add-ons and more and Steam just isn't interested in accepting the captcha.
- flush your DNS using CMD commands.
- Try using your mobile instead, and use your mobile data instead of your home network.
- Try checking your DNS, if using default use something else like CloudFlare...
These are to try resolve issue on user end, there nothing can do beyond user end because it something can only send request to steam for help but support may not be able to help either as they can't create accounts for others, and only valve has access to back end of servers.