Without https filtering in non-browser apps adguard premium won't be as desirable as it was once.

So it would be great if you can find some workaround other than don't move certificate to system. But this solution is so complex that I simply cannot advise anyone going this path.Īpart from FB, Insta where adguard is unable to filter ads irrespective of system or user certificate, there are many apps today that uses https ads and with Android 10+ they are not filtered by adguard without system certificate. The complex solution is to make your Chrome 'managed' and apply a special policy that disables Certificate Transparency. After all, 99% of AdGuard users don't have root and therefore don't move the cert anywhere. However, practice shows that blocking domains is not bad and it's enough to get rid of most of the ads there. HTTPS filtering won't work in the non-browser apps (Facebook, Insta, etc).HTTPS filtering will work just okay in the browsers.You're right, the only simple solution is to keep the certificate in the user store. If you receive this error, this indicates that your CA has not taken steps to make sure your certificate supports CT, and you should contact your CA's sales or support team to ensure you can get a replacement certificate that works.Ĭonsidering this problem affect all chromium based browsers, I ask AdGuard possible workaround for this, instead of falling back to a per basis browsers compilation with that flag disabled by default. In the case of a main page load, the user will see a full page certificate warning page, with the error code net::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED.

I opened this issue for informative reasons, and for possible solution from both sides. This result in the AdGuard for Android certificate not being trusted and being unabled to use the browser at all. Bromite latest v.55 has enabled by default options inside chrome://flags/Įnables compliance against the Certificate Transparency Policy, without any reports being issued.

Adguard for chrome android