I’m using Avast Premium Security on Windows 11. Since a couple of months I’m getting the message “deze site is niet bereikbaar” - “This site is not reachable” on a lot of website which are really safe. Almost 1 out of 2 websites are giving this message. When I set Web Guard to off, the issue disappears. I have this with different Internet browsers (Edge, Chrome, Avast Secure Browser) and on 2 different PC’s. I have the most recent updates of AVAST. I do not find any settings of Web Guard which can influence the results. Does other users have the same issue and how to solve this?
In the Web Guard settings, try disabling only QUIC/HTTP3 scanning.
Menu->settings->protection->Core shields->web guard
Hi Chris,
Thanks for your rely. It seems that on my computer “Web Guard” in core shields is greyed out.
Hi,
What you see on the screen is simply the user interface.
You need to go to “menu” (top right) and then to “settings.” like my screenshoot
Then after “protection”, “core shield” as shown in my previous screenshot.
Is disabling what appears to be a core part of a core shield a good long term fix for something that shouldn’t be an issue? I’ve noticed is the proposed workaround for the Chrome issue that has plagued users the last several months.
I agree Dinobot2 about Chrome and its issue. I suggest you try using Slimjet browser. I have the same Avast as you, but after many years of Chrome failing after an update I switched. Slimjet isn’t perfect, but more closer to 98% better than Chrome. While I have Edge I seldom use it, but even then it is a Google product, I haven’t the problem you have.
Do you have any other blocking software or another virus software installed? If the either, shut it off and try access those sites again with and without the Web Guard OUIC/HTTP3 on. If both are off and no issue, repeat but turn on only one of those packages. You might find you need to remove the other virus software or whatever software is the issue.
1 Like
Hello Chris,
Thanks for your support on this. It seems in my version of Avast I do not have the possibility to enable anything in Web Guard. It is not shown:
Hi,
Same here today,
it must have changed with an update this week.
The setting is now located at:
menu->settings->Scam Guardian
2 Likes
Hi Chris,
Thanks for your reply.
It is already enabled…. So this is not the reason I think.
As I said at the beginning…
…to check if this is the reason for your problem, you need to uncheck (disabled) the box.
Sorry misunderstood. My apologies.
I will try it.
Best regards,
Worked for me, avast was even blocking facebook
Many legitimate sites are being blocked. Removing part of the protection by disabling this option solves the problem but seems a ridiculous workaround. Interestingly I see this problem on one of my PCs, but not on the other one, both PCs have identical settings. Hopefully Avast will fix it.
1 Like
It seems it works for me too.
Then why exist that option? If enable it block most sites
First, I’m an Avast user and not an Avast Team member.
Because QUIC/HTTP3 is the new higher standard for secure and faster website connections and sites are switching to it.
If that wasn’t there, none of those sites would be scanned and you would be unaware of it.
HTTP/3 uses the QUIC protocol, which runs over UDP instead of TCP, to provide a faster, more reliable, and more secure web experience. QUIC addresses the “head-of-line blocking” issue found in HTTP/2 by allowing data streams to operate independently, improving performance on lossy networks and mobile devices. It also features faster connection establishment with zero-round-trip time (0-RTT) and mandatory, built-in encryption.
I rather doubt it is happening for every site using the QUIC/HTTP3 protocol is impacted by this. But it is possible to add those sites to the Avast Exceptions but you would need to use UDP(:)sitename(.)com(/)* rather than HTTPS (:)sitename(.)com(/)*
Instead of completely disabling the QUIC/HTTP3 protocol.
1 Like
probably the proper answer.
Certainly also that the most important third-party sites (e.g., statistics) integrated into the majority of website source codes have recently adopted this protocol, which can overload avast shield detection?