STEAM GROUP
Steam Client Beta SteamBeta
STEAM GROUP
Steam Client Beta SteamBeta
27,124
IN-GAME
103,750
ONLINE
Founded
January 8, 2013
BDK Aug 20, 2014 @ 6:22am
Error -105 when trying to play youtube videos
And here's a youtube video for you showing the problem.
Nothing wrong with my internet connection, in fact, it's awesome.

https://www.youtube.com/watch?v=8lvf8o-O7XM
Last edited by BDK; Aug 20, 2014 @ 6:22am
< >
Showing 1-15 of 22 comments
Cyber-Freak Aug 20, 2014 @ 1:10pm 
doesn't appear to be effecting anything on my end
Cyber-Freak Aug 20, 2014 @ 1:11pm 
in order to not be completely useless... check this link... http://www.sevenforums.com/gaming/322195-steam-error-105-a.html
BDK Aug 20, 2014 @ 1:20pm 
Funny thing, watching the video I posted I get no errors. So it must be because it's trying to connect to googles ad service which I have blocked. So this new update is far too sensitive to that sort of thing it seems. Shame.
Darko Aug 21, 2014 @ 8:49am 
I'm having this same issue, both in the overlay and in the client itself. The weird part is that it starts loading the page, it may even start playing a bit of the video sometimes and then suddenly I get redirected to an error page
alfred Aug 21, 2014 @ 10:10am 
Error -105 is a DNS resolution error, it means you tried to request a url and the domain name of the host failed to resolve. Try changing your DNS servers on your machine to the public google ones, perhaps your local ISP's dns is having intermittent issues?
Darko Aug 21, 2014 @ 11:37am 
But the thing is that in a regular browser like firefox or chrome I have no problems at all, it only happens on the Steam client (and particularly, in the beta client, doesn't happen in the normal one)
BDK Aug 21, 2014 @ 9:00pm 
Originally posted by alfred:
Error -105 is a DNS resolution error, it means you tried to request a url and the domain name of the host failed to resolve. Try changing your DNS servers on your machine to the public google ones, perhaps your local ISP's dns is having intermittent issues?
I use OpenDNS. Anyway as Darko already mentioned, only the browser in steam will completely kill the connection if it cant reach an ad server (instead of just moving on like a regular browser).
Avy Sep 1, 2014 @ 8:06am 
Originally posted by Darko:
I'm having this same issue, both in the overlay and in the client itself. The weird part is that it starts loading the page, it may even start playing a bit of the video sometimes and then suddenly I get redirected to an error page
Same here. Only i'm not using beta, i'm using normal client. Firefox and other apps outside Steam work fine :/
sereal Sep 6, 2014 @ 11:08am 
yep having the same issue wiht multiple sites. youtube, 9gag, gamefaqs,...
username Sep 7, 2014 @ 7:04am 
Same here.. i have Google's DNS server inserted with no results so far.. it is annoying.
sereal Sep 13, 2014 @ 3:06pm 
noone else having this issue? come on...
works flawlessly outside steam. just not in the overlay browser..
Avy Sep 13, 2014 @ 4:45pm 
Today suddenly it started to work. No Steam update, nothing :/
sereal Sep 15, 2014 @ 11:10am 
ah ok solved it. I'm using a hostfile with a fair amount of advert sites being redirected to 127.0.0.1 -> less anoying banner spam on websites.
apparently (now) steam browser does not like this and goes "blarg!" (in rochelle terms)

I think this should be fixed tho. No other browser cancels loading the rest of the page and just presents you a "one-liner".
Last edited by sereal; Sep 15, 2014 @ 11:16am
BDK Sep 15, 2014 @ 11:46am 
Yep. Not chaning my adblocker as the issue is clearly with steam.
If you have HOSTS file entries redirecting ad servers to 127.0.0.1, you can fix the error -105 by simply running a private HTTP server on port 80 of your computer when you play (don't open it up to the public network, just your private). This will stop Chrome's internal 404 errors and will display local server displayed 404 errors instead. So on pages you will see the 404 errors where the ads are supposed to be, instead of having the whole page replaced with the -105 error code.

One way to do is to install XAMPP or something similar, or just the barebones apache HTTPD server and let it serve proper 404 messages.

Alternatively you can run a python script to do this for you:

import SimpleHTTPServer
import SocketServer

PORT = 80

class MyHandler(SimpleHTTPServer.SimpleHTTPRequestHandler):

def MyHandler(self):
self.error_message_format = ""

httpd = SocketServer.TCPServer(("", PORT), MyHandler)

print "serving at port", PORT
httpd.serve_forever()
Last edited by Lee Harvey Awpwald; Sep 26, 2014 @ 11:43pm
< >
Showing 1-15 of 22 comments
Per page: 1530 50

Date Posted: Aug 20, 2014 @ 6:22am
Posts: 22