Screenshot 1

Screenshot 2

Information | value
--- | ---
Platform: | Android 10
AdGuard product: | AdGuard for Android v3.4 (120)
Browser: | Chrome
AdGuard mode: | VPN
Filtering quality: | High-quality
HTTPS filtering: | enabled
DNS requests blocking: | enabled
Filters: | Ad Blocking:
AdGuard Mobile Ads,
AdGuard Base
Privacy:
AdGuard Tracking Protection
Social Widgets:
AdGuard Social Media
Annoyances:
AdGuard Annoyances
Custom filter subscriptions: |
@ameshkov It's really frustrating that bing ad reports I've opened earlier are usually marked as "can't reproduce".
We can't fix this - if this is it small A/B Test by Microsoft.
Small A/B test need send resource of site and/or HAR file from devtools.
@krystian3w This is a captured har file when the ads show up.
www.bing.com.zip
@phgmacedo HTTPS filtering is not working in Brave browser. Please check in Chrome, Samsung Browser.
@phgmacedo HTTPS filtering is not working in Brave browser. Please check in Chrome, Samsung Browser.
So that's why my web browser (and my phone) is feeling so slow lately...
But I can still reproduce this issue in Google chrome on Android.
I have found out that https filtering only works on mobile network. It does not work on wi-fi. Is this supposed to happen?
Maybe on the contrary, IPv6 of the mobile network may make it difficult to filter ads (if was not fixed in latest v3.4).
Weird. Now I see HTTPS filtering is working in this browser.
@Chinaski1 Could you, please, assist?
I have found out that https filtering only works on mobile network. It does not work on wi-fi. Is this supposed to happen?
There were 2 different user certificates on my device. One for "vpn and apps", and another one for "wi-fi". Clearing stored credentials, and re-adding the adguard certificate, https blocking is working again. This issue can be closed.
Most helpful comment
There were 2 different user certificates on my device. One for "vpn and apps", and another one for "wi-fi". Clearing stored credentials, and re-adding the adguard certificate, https blocking is working again. This issue can be closed.