When I load a youtube video, this message "We're sorry, this video is
no longer available." keeps on appearing. I can view videos by using
Firefox. What is the problem?
> When I load a youtube video, this message "We're sorry, this video is
> no longer available." keeps on appearing. I can view videos by using
> Firefox. What is the problem?
> Thank god some else is facing the problem...No one seems to take a
> notice of tht....got any workaround for tht???
> On Sep 3, 2:23 pm, sawzz wrote:
> > When I load a youtube video, this message "We're sorry, this video is
> > no longer available." keeps on appearing. I can view videos by using
> > Firefox. What is the problem?
> > yeah...totally weird...btw are u using google web accelarator??trying
> > stopping that and seee
> > paste the link of the video you arent able to c
Accelerator is a Google Ap that is supposed to speed up the loading of
web pages. I was having the same issue. When I stopped the accelerator
from my task bar, the videos worked.
I've got Google Web Accelerator and tried disabling it and it still
will not allow sound for some reason on either Firefox or Chrome, but
when I view through IE7 it works just fine. That's really weird. I'm
with sawzz... Google owns YouTube, Web Accelerator, & Chrome but they
don't work together? odd... Any ideas other than disabling the
Accelerator?
Does the fact that web accelerator hasn't been updated in like 2+
years hold any sway? I don't even see it listed on Google Labs
anymore. That's a hint to uninstall when it not only doesn't graduate
from labs, but gets pushed off of the labs homepage :) I'd say this is
a WA problem, and not a Chrome issue.
> I've got Google Web Accelerator and tried disabling it and it still
> will not allow sound for some reason on either Firefox or Chrome, but
> when I view through IE7 it works just fine. That's really weird. I'm
> with sawzz... Google owns YouTube, Web Accelerator, & Chrome but they
> don't work together? odd... Any ideas other than disabling the
> Accelerator?
Guys... Try disabling your anti-virus and then run the page (Youtube/
Google Video...)
That should work. I was having identical problems. I disabled my
Kaspersky7 for a brief period. Things went ok after that. But once I
re-enabled it, the problem recurred. I dunno if Google should address
this...
> Does the fact that web accelerator hasn't been updated in like 2+
> years hold any sway? I don't even see it listed on Google Labs
> anymore. That's a hint to uninstall when it not only doesn't graduate
> from labs, but gets pushed off of the labs homepage :) I'd say this is
> a WA problem, and not a Chrome issue.
> On Sep 3, 10:08 am, JT2 wrote:
> > I've got Google Web Accelerator and tried disabling it and it still
> > will not allow sound for some reason on either Firefox or Chrome, but
> > when I view through IE7 it works just fine. That's really weird. I'm
> > with sawzz... Google ownsYouTube, Web Accelerator, & Chrome but they
> > don't work together? odd... Any ideas other than disabling the
> > Accelerator?
Hi folks, here is a solution I found after some testing (running
Kaspersky 7.0.0.125).
The problem lies in the "web anti-virus" module.
Fix (avoiding disabling the whole web protection) :
In the "web anti-virus" tab under "protection" main page, click
"configure", then "customize", then replace the "buffering scan"
traffic scan method with the "streaming scan" method, by checking the
appropriate box, then OK.
Close chrome if open, then retry reading a youtube video with chrome.
Should work fine.
I think the issue is the way the HTTP headers are handled by
Kaspersky, that's why I would recommend non Kaspersky users who have
that problem and reading this post to try disabling any software that
can modify traffic in any way (mainly anti virus, software firewalls
and stuff like google web accelerator it seems).
> Guys... Try disabling your anti-virus and then run the page (Youtube/
> Google Video...)
> That should work. I was having identical problems. I disabled my
> Kaspersky7 for a brief period. Things went ok after that. But once I
> re-enabled it, the problem recurred. I dunno if Google should address
> this...
Right on. It worked when I did what you suggested. Its just weird
though that this happens to Chrome and not to the other 3 browsers
(IE, FireFox, Safari) that I use regularly. Does that mean Chrome
accesses URLs differently?
> Hi folks, here is a solution I found after some testing (running
> Kaspersky 7.0.0.125).
> The problem lies in the "web anti-virus" module.
> Fix (avoiding disabling the whole web protection) :
> In the "web anti-virus" tab under "protection" main page, click
> "configure", then "customize", then replace the "buffering scan"
> traffic scan method with the "streaming scan" method, by checking the
> appropriate box, then OK.
> Close chrome if open, then retry reading ayoutubevideo with chrome.
> Should work fine.
> I think the issue is the way the HTTP headers are handled by
> Kaspersky, that's why I would recommend non Kaspersky users who have
> that problem and reading this post to try disabling any software that
> can modify traffic in any way (mainly anti virus, software firewalls
> and stuff like google web accelerator it seems).
> Let me know if it helped, cheers !
> maabaa
> On 3 sep, 23:35, i-Mage wrote:
> > Guys... Try disabling your anti-virus and then run the page (Youtube/
> > Google Video...)
> > That should work. I was having identical problems. I disabled my
> > Kaspersky7 for a brief period. Things went ok after that. But once I
> > re-enabled it, the problem recurred. I dunno if Google should address
> > this...
> Right on. It worked when I did what you suggested. Its just weird
> though that this happens to Chrome and not to the other 3 browsers
> (IE, FireFox, Safari) that I use regularly. Does that mean Chrome
> accesses URLs differently?
> On Sep 4, 9:44 am, maabaa wrote:
> > Hi folks, here is a solution I found after some testing (running
> > Kaspersky 7.0.0.125).
> > The problem lies in the "web anti-virus" module.
> > Fix (avoiding disabling the whole web protection) :
> > In the "web anti-virus" tab under "protection" main page, click
> > "configure", then "customize", then replace the "buffering scan"
> > traffic scan method with the "streaming scan" method, by checking the
> > appropriate box, then OK.
> > Close chrome if open, then retry reading ayoutubevideo with chrome.
> > Should work fine.
> > I think the issue is the way the HTTP headers are handled by
> > Kaspersky, that's why I would recommend non Kaspersky users who have
> > that problem and reading this post to try disabling any software that
> > can modify traffic in any way (mainly anti virus, software firewalls
> > and stuff like google web accelerator it seems).
> > Let me know if it helped, cheers !
> > maabaa
> > On 3 sep, 23:35, i-Mage wrote:
> > > Guys... Try disabling your anti-virus and then run the page (Youtube/
> > > Google Video...)
> > > That should work. I was having identical problems. I disabled my
> > > Kaspersky7 for a brief period. Things went ok after that. But once I
> > > re-enabled it, the problem recurred. I dunno if Google should address
> > > this...
I just downloaded the newset beta for IE 8 and I get exactly the same
problem but w/ a bit more info... in fact, at least in my own
emediaboard app, IE tells me cross scripting is disabled. That's a
security feature in the newest web standards. SOmething to do with
XPP... I am not a specialist in that area... I wonder if the security
softwares mentionned in this thread weren't simply also forbidding
cross scripting? Anyway that's what I found.
> Probably, but that's above my knowledge, I'll let more qualified
> people look into it.
> Glad it helped !
> On Sep 4, 5:12 am, ADL_obap wrote:
> > Right on. It worked when I did what you suggested. Its just weird
> > though that this happens toChromeand not to the other 3 browsers
> > (IE, FireFox, Safari) that I use regularly. Does that meanChrome
> > accesses URLs differently?
> > On Sep 4, 9:44 am, maabaa wrote:
> > > Hi folks, here is a solution I found after some testing (running
> > > Kaspersky 7.0.0.125).
> > > The problem lies in the "web anti-virus" module.
> > > Fix (avoiding disabling the whole web protection) :
> > > In the "web anti-virus" tab under "protection" main page, click
> > > "configure", then "customize", then replace the "buffering scan"
> > > traffic scan method with the "streaming scan" method, by checking the
> > > appropriate box, then OK.
> > > Closechromeif open, then retry reading ayoutubevideo withchrome.
> > > Should work fine.
> > > I think the issue is the way the HTTP headers are handled by
> > > Kaspersky, that's why I would recommend non Kaspersky users who have
> > > that problem and reading this post to try disabling any software that
> > > can modify traffic in any way (mainly anti virus, software firewalls
> > > and stuff like google web accelerator it seems).
> > > Let me know if it helped, cheers !
> > > maabaa
> > > On 3 sep, 23:35, i-Mage wrote:
> > > > Guys... Try disabling your anti-virus and then run the page (Youtube/
> > > > Google Video...)
> > > > That should work. I was having identical problems. I disabled my
> > > > Kaspersky7 for a brief period. Things went ok after that. But once I
> > > > re-enabled it, the problem recurred. I dunno if Google should address
> > > > this...
Well, cross site scripting is a type of web exploit, and the stuff I
changed in Kaspersky is about malware / virus analysis on the fly, so
I don't think the problem, at least on my computer, is related to XSS
protection.
Don't know much about it though.
> I just downloaded the newset beta for IE 8 and I get exactly the same
> problem but w/ a bit more info... in fact, at least in my own
> emediaboard app, IE tells me cross scripting is disabled. That's a
> security feature in the newest web standards. SOmething to do with
> XPP... I am not a specialist in that area... I wonder if the security
> softwares mentionned in this thread weren't simply also forbidding
> cross scripting? Anyway that's what I found.
> Hi folks, here is a solution I found after some testing (running
> Kaspersky 7.0.0.125).
> The problem lies in the "web anti-virus" module.
> Fix (avoiding disabling the whole web protection) :
> In the "web anti-virus" tab under "protection" main page, click
> "configure", then "customize", then replace the "buffering scan"
> traffic scan method with the "streaming scan" method, by checking the
> appropriate box, then OK.
> Close chrome if open, then retry reading ayoutubevideo with chrome.
> Should work fine.
> I think the issue is the way the HTTP headers are handled by
> Kaspersky, that's why I would recommend non Kaspersky users who have
> that problem and reading this post to try disabling any software that
> can modify traffic in any way (mainly anti virus, software firewalls
> and stuff like google web accelerator it seems).
> Let me know if it helped, cheers !
> maabaa
> On 3 sep, 23:35, i-Mage wrote:
> > Guys... Try disabling your anti-virus and then run the page (Youtube/
> > Google Video...)
> > That should work. I was having identical problems. I disabled my
> > Kaspersky7 for a brief period. Things went ok after that. But once I
> > re-enabled it, the problem recurred. I dunno if Google should address
> > this...
> Hi folks, here is a solution I found after some testing (running
> Kaspersky 7.0.0.125).
> The problem lies in the "web anti-virus" module.
> Fix (avoiding disabling the whole web protection) :
> In the "web anti-virus" tab under "protection" main page, click
> "configure", then "customize", then replace the "buffering scan"
> traffic scan method with the "streaming scan" method, by checking the
> appropriate box, then OK.
> Close chrome if open, then retry reading ayoutubevideo with chrome.
> Should work fine.
> I think the issue is the way the HTTP headers are handled by
> Kaspersky, that's why I would recommend non Kaspersky users who have
> that problem and reading this post to try disabling any software that
> can modify traffic in any way (mainly anti virus, software firewalls
> and stuff like google web accelerator it seems).
> Let me know if it helped, cheers !
> maabaa
> On 3 sep, 23:35, i-Mage wrote:
> > Guys... Try disabling your anti-virus and then run the page (Youtube/
> > Google Video...)
> > That should work. I was having identical problems. I disabled my
> > Kaspersky7 for a brief period. Things went ok after that. But once I
> > re-enabled it, the problem recurred. I dunno if Google should address
> > this...
The streaming scan setting will use a reduced database, because it's
real time analysis.
It will look only for current malwares etc... the most expected bad
things that may happen to you when surfing.
The buffering scan setting will use the full database, do a complete
analysis of the datas, taking more time.
Now, the streaming one is enough already, because whatever might come
to your computer without the real time web anti virus noticing, the
full file anti virus on your computer will notice at some point.
So I would say no need to stress, you still are protected ;)
> Hi folks, here is a solution I found after some testing (running
> Kaspersky 7.0.0.125).
> The problem lies in the "web anti-virus" module.
> Fix (avoiding disabling the whole web protection) :
> In the "web anti-virus" tab under "protection" main page, click
> "configure", then "customize", then replace the "buffering scan"
> traffic scan method with the "streaming scan" method, by checking the
> appropriate box, then OK.
> Close chrome if open, then retry reading ayoutubevideo with chrome.
> Should work fine.
> I think the issue is the way the HTTP headers are handled by
> Kaspersky, that's why I would recommend non Kaspersky users who have
> that problem and reading this post to try disabling any software that
> can modify traffic in any way (mainly anti virus, software firewalls
> and stuff like google web accelerator it seems).
> Let me know if it helped, cheers !
> maabaa
> On 3 sep, 23:35, i-Mage wrote:
> > Guys... Try disabling your anti-virus and then run the page (Youtube/
> > Google Video...)
> > That should work. I was having identical problems. I disabled my
> > Kaspersky7 for a brief period. Things went ok after that. But once I
> > re-enabled it, the problem recurred. I dunno if Google should address
> > this...
You the man! Thanks!
It's funny, After I found that disabling Kaspersky solved the problem
(I think) I disabled each module one by one and couldn't fix it that
way.
Anyway, thanks for giving me a second chance with Chrome.
|
