I too am wondering why the forum is down from time to time.
I got this message today : An error occurred while processing your request.
Reference #102.4737655f.1676559351.2b5b5862
Microsoft in it’s advice, says it might take some time before you might go there again without re-triggering that specoific error.
Maybe it was your IP or DNS reported falsely, that triggered it.
So it is just a technical hick-up. The weird ways of the cloud-driven Internet for you.
Don’t forget also cybercriminal forces are active all over the Interwebz
(like noName cybercriminals etc. etc. Russian Business Network etc. etc.).
Blijf veilig zowel offline als online, is de wens van,
I haven’t been able to reach this forum for days, until 20 minutes ago. Same message as Luukjr. IsItDown and similar sites reported that the forum was up.
First I figured it was probably my VPN, but even on my Dutch ISP’s own IP and DNS no access. So that Akamai ban seems rather broad, long, and ham-fisted.
Well I have had about four and a half days of being totally unable to connect to the forums only error messages (attachment 1) which were about a helpful trying to put a fire out with a bucket of petrol.
To make sure I wasn’t going daft, I used my normal tool to check if avasts forum was down or not and low and behold it is still causing issues (attachment 2) in my go too tool to check.
I have no doubt this has something to do with the change to the Akamai distributed network, this would also appear to be further complicated with my browsers (Firefox latest version) DNS over HTTPS setting (which I can’t recall ever setting). This was set to use Cloudflare, now I don’t particularly like Cloudflare and wouldn’t have selected that (if I had changed the setting). So I changed that to NextDNS as the option and I was able to connect o the avast forum.
I will have to monitor this over a few days to see if that completely resolves my connecting to the forums problem. So it’s fingers crossed.
Yep, Amsterdam-Akamai for ye. Re-routing from USA servers meant no blocking whatsoever.
DNS Jumper helped me out and somehow showed where the error (or outside threats resided).
Another lesson well-learnt, and showed me the importance of routing and DNS in order to be secure.
Also shows how important it is to have a good grasp of the English language.
Anyways thanks for affirming my hunches on this for me,
If we consider how world wide DNS propagation works, it could mean you must pause as over 72 hrs between visiting a particular non-resolving website again. That is the normal update time and that meant under normal non-error world-wide conditions.
We stiil see users from Mexico now unable to get to forum dot avast dot com (Monterrey server).
Well I was faced with the usual useless error message (that I attached in Reply #6 above) and this with the NextDNS for DNS over HTTPS that had been working for several hours only to fail the Akamai bull droppings Distributed Network cr4p.
So I changed back to the Cloudflare DNS and restarted Firefox and tried again, same dumbass error message. Changed the DNS over HTTPS, restarted firefox again, that to failed. Changed the DNS over HTTPS from enabled to disabled, restarted and tried to connect to the forums again, failed. Changed the DNS over HTTPS back to NextDNS again and restarted Firefox and back in.
This is becoming bloody tiresome, someone’s ass needs to be roasted over a large bonfire.
This cr4p with the Akamai Distributed Network has to be:
actively monitored so avast is aware of all of the errors triggered.
resolve the cause of the errors and be fixed.
or the Akamai Distributed Network be canned.
As this solution which was I believe to address the damn slow page loading, etc. in the forums needs to be fixed.
Avast users shouldn’t need to be DNS network savvy just to access and get some help in the Avast forums.
Finally, Avast has to have a Forum Administrator (currently 9) in more than name only, whom is active in the forums as r@vast used to be before his absence (about 3 months ago) and he wasn’t an Administrator, but effectively a link with the Avast Team.
The situation should be being actively monitored by the Avast Team, after all it is their reputation that suffers with these lock outs and inability to connect to the avast support forum.
It shouldn’t be the user having to get creative to find a way round this cr4p.
I never signed up to the Avast Slack channel, never dreaming I would need it. When the forum is supposedly down or DAMN slow there HAS TO BE a way to communicate this to Avast!
Yeah I tried to see if there was a notice on the Avast site, or on Twitter. But nothing. Silence.
We the (mostly) Avast Free users that are here to help each other as best we can, are apparently second rate citizens. “Forum unreachable or down? F 'em.” :o
When signed-in, we all now are on: -hostname:forum.avast.com,
behind Akamai cloud client protection (blocking various abuse, like dDos, scraping etc.)
and given an A-record Frankfurt IP address
See for yours e.g. on https://pl.ipshu.com
I think there is given no direct need for avast here to communicate this to their forum users.
At the end of the day it is their security policy with Akamai for account protection settings.
Hope it won’t hamper new avast users finding their way here.
All is well that ends well.
Well my connections have been up AND down like a whore’s drawers, what worked once and for a while doesn’t work after a period of time (non use of forums).
So I have been restarting firefox, flip flopping DNS settings restarting firefox to try again this has taken several changes and restarts and I manage to get back in. This however is no guarantee that I will be able to access the forums next time.
I have just tried something else and whilst it appears to have worked (the flip flopping settings also seemed to work), I have now added forum.avast.com to Firefox’s “No proxy for” option. That worked but as I said in a few hours that may not work and I’m flip flopping around like a fish out of water.
Avast needs ACTIVE monitoring of the many hundreds/tens of thousands of error messages being generating as this is PATHETIC!
NOT TO MENTION - If this move to Akamai was to resolve forum speed issues it has failed as at times I still get slow page loads (and much slower than what is shown at the bottom of the page).
Three times today, virtually every bloody time I try to get on the forums, I have to go through this flip flopping as described in Reply #6, #10 and #16.
Tiresome doesn’t begin to describe this fiasco.
Active monitoring by the Avast Team (in conjunction with Akamai) of the cryptic error messages as to what they actually mean and why they are displayed.