ERROR CODE -107 *SOLVED*

[umop apisdn]

Hello Everyone,

I cannot access the Steam store or My Account without getting this error. I also cannot access this stuff on a regular browser either. I've done quite a bit of googling to see if anyone has found a solution, and one tip I got was to make sure my time was correct on my PC. It is so now I'm stumped. Could anyone offer some advice?

Thanks

[Richard Siegers]

i think they fixed it also no errors in 2 days

[macmach4]

Looks like it fixed itself (knock on wood).

On the Ziggo forum thread, the whole thing concludes with some correspendence with one Gabe (!) of Steam, saying they can't pinpoint it at their end, either. Meanwhile it seems pretty much established it wasn't at Ziggo's or Akamai's end, either.

My guess would be inasmuch as it seems assumed now it had to do with faulty DNS addresses having been cached somewhere down the line, that has indeed fixed itself now.

Here's hoping. Thanks, all. No errors at my end for I guess indeed a few days now.

[$ini$ter-NL]

I fixed it by staring really hard at my screen and praying to Lord Gabe.

[macmach4]

Ursprungligen skrivet av $ini$ter-NL:

I fixed it by staring really hard at my screen and praying to Lord Gabe.

Lol. Where's my like button when I need one

[macmach4]

Oh. Guess what. Opening up Steam again just now, I had a -107 error. No kidding :/

[$ini$ter-NL]

Ursprungligen skrivet av macmach4:

Oh. Guess what. Opening up Steam again just now, I had a -107 error. No kidding :/

Pray more!

[macmach4]

Hmmm. I'd sinfully been enjoying some disrespectful writings over at RPS. Maybe that explains it ;)

[76561198956844776]

lol

[Boeh1701]

yeah, it's back after a couple of days of working flawlessly.

[Skully]

Akamai International BV now screwed up another Dutch Steam proxy.

$ wget -S https://23.52.51.147/
--2019-04-19 09:10:31--  https://23.52.51.147/
Connecting to 23.52.51.147:443... connected.
OpenSSL: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
Unable to establish SSL connection.
 

https://184.50.163.235/ is still borked.
https://23.5.174.107/ is still operational.

It looks like Ziggo is hijacking outgoing DNS calls.
Outside of Ziggo:

$ host store.steampowered.com 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:

store.steampowered.com has address 2.20.128.189

Inside Ziggo:

$ host store.steampowered.com 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:

store.steampowered.com has address 23.5.174.107

[$ini$ter-NL]

Yeah it's broken again.

[spykerKonyn]

Back to square one. And Steam still has its head up its ass. Do they want Epic Game Store to succeed? I'm seriously getting ticked off by this BS.

[B✪✪tsy]

It comes and goes. One moment after some page refreshes I can view the store pages, next moment the error is back.

[Extromal]

Ok, i have been doing some testing (yeah on the Ziggo forum too) and just found out that one of Akamais DNS is giving out the wrong IP
Ziggo's DNS gives out 184.50.163.235 (which isnt the one hosting store.steampowered.com)
Google DNS seems to be ok (for time being)

But when i set a1-164.akam.net (193.108.91.164) as DNS, i instantly get the wrong IP when i do a ping.

So it seems that the problem lies in one of Akamai's DNS servers.

[macmach4]

Just to wrap this up, on the Ziggo forum thread regarding this topic, four days ago Steam was reported to have replied that:

Success! By tracking down your requests in the logs, we were able to identify a sick Akamai DNS server and remove it from service. Thanks for helping us get to the bottom of this.

Hopefully this should resolve the intermittent errors you and others have been experiencing loading https://about:blank, but definitely let me know if you continue to see issues.

( https://community.ziggo.nl/internetverbinding-102/problemen-met-steam-client-en-website-38869/index7.html#post391439 .)

I have indeed not had any issues for some time now. Thanks to those who did get to the bottom of it.

Over & out, happy gaming!