Ever since upgrading to Adguard ver 7 I have been having problems with my browsing (see enclosed image). I have installed the new certificate. If I press "Try again" the page will then load but every fresh page brings up the same try again page. I am running Win 8.1 pro and using Cyberfox 52.9.1 Can someone help please.
On the Adguard mobile App, what exactly is the adguard simplified domain names filter that is on by default, and would i want to turn it off.
i have no issues with adguard premium on mobile. the extension is powered by firefox itself and has no cert to insert.
In the adguard mobile app, when i try to select the cleanbrowsing adult filter for DNSCrypt IPv4 and press on add to adguard it does not work. Has the known dns providers list been updated recently for cleanbrowsing because i think they support DNSSEC now. The cleanbrowsing security filter does not show any DNSCrypt servers like the cleanbrowsing family and adult filters do.
Info is here. That depends on how you use AdGuard. Assuming yours is Premium, if you're willing to enable HTTPS filtering, turn it off as other default filters are better. If not, keep it turned on and turn other filters (English, Tracking) off unless specifically needed (e.g. regional filters) because in this case they are mostly spoiled on https pages (particularly big is all rules w/ $third-party option doesn't work). Strange, but u can manually add the config info. IIRC they support DNSSEC from the beginning and the last part is normal as they don't have DNSCrypt config for the security filter (by its nature, DNSCrypt requires its DNS stumps being published). You can use DoH instead. Remember, tho, if you're already using Android9+' private DNS feature, AG's DNS setting doesn't have effect as AG can do nothing against the DNS traffic. [EDIT: terminology]
I don't use Windows version but I remember similar thing happened when I was testing other product which also install local cert. Possibly some TLS related config may be related, try setting up a new profile on Cyberfox and also on normal Firefox. If the issue doesn't replicate, you can narrow down the issue one by one via about:config. This kind of trouble is one reason why messing up TLS by MITM is not a very good idea tho.
Google introduced Private DNS in Android Pie v9, which lets you easily configure your DNS for your whole Android device. With Private DNS option, you can set a DNS server for all of your Wi-Fi and Mobile networks at one place rather than changing it one by one for each. Not only it makes the process simple, but Private DNS also adds support for a new security feature called DNS over TLS. And Private DNS on Android only supports DNS over TLS, so if the DNS resolver provider you want to use doesn’t support it, you cannot use it in Private DNS.
