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

[TheBear]

Originalmente postado por macmach4:

Originalmente postado por TheBear:

Now for the trickier part i have little know-how on : On Reddit they seem to suggest the problem is Chromium, as any error with a negative sign infront of the code, like -107 or -100, points to chromium errors, which the store in the client uses.

I Disagree though, as this happens on different platforms and different browsers.. as far as i know Edge has not updated to chromium yet and i was getting the same error. (TSL/SSL error)

But if like you say it's to do with the Steam client using Chromium, that would be independent of what client you use to approach it with. Right?

Well its someone on Reddit claiming its Chromium.

Me, i still think something is up with DNS records or servers with Steam.
I cant explain why this problem seems to exist mostly with Ziggo.. yet i also see reports of people having switched to google DNS and they still get the error, but less frequently.

Something is just really wrong here and i simply cannot say for certain whether its the ISP or Steam.. or both lol.

[TheBear]

Originalmente postado por Spawk:

Originalmente postado por TheBear:

Well its someone on Reddit claiming its Chromium.

Me, i still think something is up with DNS records or servers with Steam.
I cant explain why this problem seems to exist mostly with Ziggo.. yet i also see reports of people having switched to google DNS and they still get the error, but less frequently.

Something is just really wrong here and i simply cannot say for certain whether its the ISP or Steam.. or both lol.

Not that it would matter, as neither one wants to actually look into it.

Well i think Ziggo is looking into it actually, this isnt the first time they had issues with Steam if i read that ziggo thread correctly.

[Omega]

Also Ziggo here same issue.

[TheBear]

Latest from Ziggo :

Our network specialists have looked at it. There is no misconfiguration, DNS works well. They have indicated that our DNS systems do not come up with IP addresses and that an incorrect IP address must have been supplied by Akamai. We do not arrange manual workarounds to prevent future problems. That is also the essence of how DNS works. The source must pass on the good IP addresses to other DNS servers.

I see 184.50.163.235 coming back in our DNS today. I also see a number of new addresses again. I don't see all of this in the Google DNS. Akamai therefore sends different information to different DNS servers (and that is unusual). Akamai handles this process on behalf of Steam. If your paid service does not work due to incorrect DNS data, the troubleshoot always starts with the service where your customer is with. And that is Steam.

[PowerofWill]

it worked for more than 24 hours..... the error is back
this is sooo annoying.
i kinda hoped they had it fixed. they didnt

[B✪✪tsy]

I haven't changed anything and yesterday I was able to see the store and whishlist again, today I get the same error code again. The weird thing is that this is a 1 year old topic and I never had problems, just suddenly now I get this error. I seriously doubt that the issue lies with Ziggo, because I have UPC/Ziggo for 10 years and never had this issue.

[spykerKonyn]

Originalmente postado por B00tsy:

I haven't changed anything and yesterday I was able to see the store and whishlist again, today I get the same error code again. The weird thing is that this is a 1 year old topic and I never had problems, just suddenly now I get this error. I seriously doubt that the issue lies with Ziggo, because I have UPC/Ziggo for 10 years and never had this issue.

Same for me. Been having this issue for weeks now. Yesterday I changed my host file and everything was fine. Today it's Code 107 again. I do think this is a Ziggo issue since most people here are a Ziggo customer. No clue if it is hardware related or not though. Could be something to do with the old Ziggo routers?

[B✪✪tsy]

Originalmente postado por spykerKonyn:

Originalmente postado por B00tsy:

I haven't changed anything and yesterday I was able to see the store and whishlist again, today I get the same error code again. The weird thing is that this is a 1 year old topic and I never had problems, just suddenly now I get this error. I seriously doubt that the issue lies with Ziggo, because I have UPC/Ziggo for 10 years and never had this issue.

Same for me. Been having this issue for weeks now. Yesterday I changed my host file and everything was fine. Today it's Code 107 again. I do think this is a Ziggo issue since most people here are a Ziggo customer. No clue if it is hardware related or not though. Could be something to do with the old Ziggo routers?

If it really is a Ziggo issue then there is nothing I can do about it. It has been reported to Ziggo by customers, after that it depends on the willingness of Ziggo if it gets solved or not. What would help if Valve contacts Ziggo telling them that a lot of Steam customers can't use their site. Communication between companies is much more effective than a simple ISP customer reporting the problem. Support desks always filters problems away with scripted responses. Ziggo is notorious for bad customer support.

[Bumbefly (we/All)]

I have Ziggo without any such problem. A friend of mine uses XS4All Ziggo and did suffer this.
Clearing Browser Cache in Steam Settings worked for 2 of my friends.

[Edit] Friend is located at a different adress a.t.m..

[TheBear]

Originalmente postado por Bumbefly Sony Test םו:

I have Ziggo without any such problem. A friend of mine uses XS4All and did suffer this.
Clearing Browser Cache in Steam Settings worked for 2 of my friends.

Thats a temporary solution as this is IP related.

I cant translate the following completely, so if you're dutch :

code:
wget store.steampowered.com
--2019-04-15 11:21:56-- http://store.steampowered.com/
Herleiden van store.steampowered.com (store.steampowered.com)... 184.50.163.235
Verbinding maken met store.steampowered.com (store.steampowered.com)|184.50.163.235|:80... verbonden.
HTTP-verzoek is verzonden; wachten op antwoord... 302 Moved Temporarily
Locatie: https://store.steampowered.com/ [volgen...]
--2019-04-15 11:21:56-- https://store.steampowered.com/
Verbinding maken met store.steampowered.com (store.steampowered.com)|184.50.163.235|:443... verbonden.
OpenSSL: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
Kan geen SSL-verbinding maken.

The above shows in a nutshell, that steam needs to FIX-THEIR-SHIIIIIIIII... t.

[Omega]

It can't be a DNS issue, at home I am using 1.1.1.1 and 9.9.9.9 through a stand-alone DHCP server.

I am now on another Ziggo network away from home, it uses the Ziggo DNS.

Both networks have the same issue.

Originalmente postado por TheBear:

Originalmente postado por Bumbefly Sony Test םו:

I have Ziggo without any such problem. A friend of mine uses XS4All and did suffer this.
Clearing Browser Cache in Steam Settings worked for 2 of my friends.

Thats a temporary solution as this is IP related.

I cant translate the following completely, so if you're dutch :

code:
wget store.steampowered.com
--2019-04-15 11:21:56-- http://store.steampowered.com/
Herleiden van store.steampowered.com (store.steampowered.com)... 184.50.163.235
Verbinding maken met store.steampowered.com (store.steampowered.com)|184.50.163.235|:80... verbonden.
HTTP-verzoek is verzonden; wachten op antwoord... 302 Moved Temporarily
Locatie: https://store.steampowered.com/ [volgen...]
--2019-04-15 11:21:56-- https://store.steampowered.com/
Verbinding maken met store.steampowered.com (store.steampowered.com)|184.50.163.235|:443... verbonden.
OpenSSL: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
Kan geen SSL-verbinding maken.

The above shows in a nutshell, that steam needs to FIX-THEIR-SHIIIIIIIII... t.

Linux user?

I also use Linux. Could it be a Linux issue?

Same wget output for me:

 
dennis@solus-laptop ~ $ wget store.steampowered.com
--2019-04-15 12:20:48--  http://store.steampowered.com/
Herleiden van store.steampowered.com... 23.52.51.147
Verbinding maken met store.steampowered.com|23.52.51.147|:80... verbonden.
HTTP-verzoek is verzonden; wachten op antwoord... 302 Moved Temporarily
Locatie: https://store.steampowered.com/ [volgen...]
--2019-04-15 12:20:49--  https://store.steampowered.com/
Verbinding maken met store.steampowered.com|23.52.51.147|:443... verbonden.
OpenSSL: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
Kan geen SSL-verbinding maken.

Translated:

 
dennis@solus-laptop ~ $ wget store.steampowered.com
--2019-04-15 12:20:48--  http://store.steampowered.com/
Tracing store.steampowered.com... 23.52.51.147
Connecting with store.steampowered.com|23.52.51.147|:80... connected.
HTTP- request sent; waiting for answer... 302 Moved Temporarily
Location: https://store.steampowered.com/ [following...]
--2019-04-15 12:20:49--  https://store.steampowered.com/
Connecting with store.steampowered.com|23.52.51.147|:443... connected.
OpenSSL: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
Can not set up a SSL connection. 

[spykerKonyn]

Originalmente postado por TheBear:

The above shows in a nutshell, that steam needs to FIX-THEIR-SHIIIIIIIII... t.

If this is the case. How do we bring this to Steam's attention? Since this is a year old thread obviously the forums are NOT the way to go.

Any suggestions?

Edit: You think this is all ploy by Epic Games to get us to download their launcher? O.O
j/k

[B✪✪tsy]

Originalmente postado por spykerKonyn:

Originalmente postado por TheBear:

The above shows in a nutshell, that steam needs to FIX-THEIR-SHIIIIIIIII... t.

If this is the case. How do we bring this to Steam's attention? Since this is a year old thread obviously the forums are NOT the way to go.

Any suggestions?

Filing a ticket, but we all know how that goes. Maybe a Valve dev at the steam client beta forum can level this issue up as they do actually read and respond on that forum hub.

PS, I am not the right person to report that as I am no techie.

[yoshirules]

Originalmente postado por B00tsy:

Originalmente postado por spykerKonyn:

If this is the case. How do we bring this to Steam's attention? Since this is a year old thread obviously the forums are NOT the way to go.

Any suggestions?

Filing a ticket, but we all know how that goes. Maybe a Valve dev at the steam client beta forum can level this issue up as they do actually read and respond on that forum hub.

I did that 3 times all the time I get the standard reply: It's your provider or your hardware :(

[kkkkk]

check yt