actually, in the movie…the response was ‘did you see a body? assumption is the mother of all frakkups’ 8)
Ensure that you have updated the virus definitions and possibly clear your browser cache.
My definitions are updated to the latest (as of this posting, 210621-2), and the problem occurred on multiple browsers (with cache cleared on all). Besides, as I stated in a related post, Avast confirmed this morning that this was a false positive.
I was simply pointing out that just because some users aren’t experiencing the problem, this doesn’t mean there isn’t a problem.
how does the web shield function anyways? whats the exact operating method…
@ Muad’Dib
I honestly can’t see if it has been confirmed as an False Positive (I reported it also even though I never got the alert) and as the reply email states.
“With URLs this change should be instant, but it might take up to 24 hours with files.”
So I can’t understand why you are still getting the alert and is it the same (e.g. the xxxxxxxx.cloudfront.com one) ?
Bob–
Obviously something is going on since I and others are being blocked.
Others in this case are a very small group so the question is what are you running that’s causing it that the rest of us are not?
the differences here come down to individual software environments I suspect, which is why some were, and some were not, seeing this problem.
Bob–
You don’t know the exact number of people involved. But I doubt it’s one or two. Just because it’s not happening to you doesn’t make it wrong.
Just gave it a test and I could log in. So thanks to either the Amazon or Avast teams for clearing it up!
Sorry I’m not Bob, nor trying to justify his post.
I don’t think Bob or any of the other volunteer helpers in the forums could answer this with a definitive number. However, in false positive instances like this, with hundreds of millions of users, if this were really widespread this forum would be on fire with it.
The actual numbers reporting it in the forums are relatively small (not that it doesn’t warrant resolution and for those impacted very serious), but by comparison to false positive events over the many years I have been helping in the forums, very small.
as I could see by threads, seem a CDN block, and as you say a relaltivelly small number, maybe is because b lock a CDN used to access to Amazon from (some) countries far from USA
Big or small–and just I would imagine there are many, many Avast users who have no idea that such a forum as this exists or who would know where to report a problem (for example, people have been reporting the problem on Reddit and I’m sure many other Internet sites–doesn’t matter. There’s no point in denying that it happened just because it didn’t happen to you.
I just received a message from Avast saying that their team has fixed the issue.
What issue? It would be nice to know what issued that only affected a select few was resolved.
the cloud front issue that was killing any attempt to connect to amazon.
the very same issue we(the affected) kept trying to explain, that certain select individuals keep refusing to acknowledge was a problem because ‘if I’m not affected there must not be a problem’
and frankly, I’m tired of trying to explain it to someone who just refuses to admit…that just because they aren’t affected, doesn’t mean it wont be affecting others.
please see attached response from avast’s technical support team, not only confirming the issue, but also that it has been fixed.
if you still believe the problem didn’t exist, well then, thats on you then isn’t it?
and on that note, I’m walking away from this thread.
No one here said the problem didn’t exist. It would still be nice to know exactly what that problem was since it didn’t effect most users.
It would be nice if Avast offered an explanation. Unless you aren’t interested in exactly what caused the problem?
I certainly am.
Hi,
Maybe you could try to change DNS and/or delete the DNS cache (“ipconfig /flushdns” in command prompt),in addition to emptying the cache of your browser.
On the other hand, for a few days I’ve had problems with sites blocked by my ad blocker (ublockorigin), because of the “akamaiedge” filter…Try (if you have one) to temporarily disable your ad blocker.