AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Cannot access steam store12/15/2023 It was illustrated that the problem indeed is on Akamai's and Valve's end, as Akamai's own DNS servers were earlier today found to be handing out the bad IP addresses in question.Ĭonfiguring an alternate DNS server may offer some solace, but do keep in mind: the above will have a trickle down effect on other DNS servers that honor Akamai's DNS and you may find the issue cropping up when using OpenDNS Google DNS etc now as well. Ziggo for their part has checked the DNS settings on their end and it all checks out OK. Not only that Valve's talking to one user that finally managed to punch a ticket through and the replies on it are signed off "Thanks, Gabe" which means the big boss himself may actually be involved this time. They need Valve to work with them on this.Īkamai and Valve apparantly are contacting one another to get this sorted. Akamai is not at liberty to disclose information or make changes without authorization by their client, i.e. The short of it is that several old IP addresses are being referred to, which are no longer in use by Steam. Valve and Akamai are responsible and they have to fix it.įor those capable of reading Dutch: here's the relevant thread on the ISP's community forums: Don't bother contacting them they cannot help. Yes the primary area affected is the Netherlands specifically Dutch ISP Ziggo. Originally posted by damiandimitri:I have the same since yesterday ( NEtherlands) Which, given their tendency to avoid admitting their own screw-ups, will likely never happen. This problem has been going on for about a month now and Valve has yet to give a public explanation. It has also been reported directly to Akamai itself, who have replied back that they cannot directly do anything without authorization by Valve. It has been reported to local ISPs, who point back at Valve stating that its their responsibility. This problem has been reported numerous times to Valve, who points at local ISPs having broken configuration. The reason you're no longer seeing this problem after updating the client, is because you were given a new session, which was load-balanced onto a different server that does not suffer from broken configuration. Firefox will occasionally give you an error page with code SSL_ERROR_INTERNAL_ERROR_ALERT. You can actually get this error from any browser as well. If your session gets load balanced onto such a broken server it results in error code 107, which is the numerical value of the ERR_SSL_PROTOCOL_ERROR error code in Chrome. The problem is one or more misconfigured servers in the Akamai CDN on which the Steam store relies. This problem has nothing to do with the Steam client. Originally posted by damiandimitri:i update to the beta of steam and now it is working again
0 Comments
Read More
Leave a Reply. |