2ememain.be

[adguard-bot]

Issue URL (Incorrect Blocking)

http://2ememain.be

Comment

Impossible to visit the site. It's as if it was disabled.

Screenshots

Screenshot 1


Screenshot 1 with AdGuard disabled


System configuration

Information	Value
AdGuard product:	AdGuard for Android v4.4.1
System version:	Android 12
Browser:	Firefox Mobile
AdGuard mode:	VPN
HTTPS filtering:	enabled
Stealth mode options:	Hide your search queries, Send Do-Not-Track header, Hide your Referrer from third-parties, Hide your User-Agent, Remove X-Client-Data header from HTTP requests, Self-destructing third-party cookies (180), Self-destructing first-party cookies (4320)
DNS filtering:	server: https://dns.adguard-dns.com/dns-query filters: https://filters.adtidy.org/android/filters/15_optimized.txt
Filters:	Ad Blocking: AdGuard Base, AdGuard Mobile Ads Privacy: AdGuard URL Tracking, AdGuard Tracking Protection, Legitimate URL Shortener Social Widgets: AdGuard Social Media Annoyances: AdGuard Annoyances, AdGuard Mobile App Banners, AdGuard Popups, AdGuard Cookie Notices, AdGuard Widgets, Adblock Warning Removal List Security: Online Malicious URL Blocklist Language-specific: AdGuard French
Custom filters:	https://raw.githubusercontent.com/bogachenko/fuckfuckadblock/master/fuckfuckadblock-mining.txt, https://raw.githubusercontent.com/bogachenko/fuckfuckadblock/master/fuckfuckadblock.txt, https://gitlab.com/magnolia1234/bypass-paywalls-clean-filters/-/raw/main/bpc-paywall-filter.txt
Userscripts:	https://userscripts.adtidy.org/release/adguard-extra/1.0/adguard-extra.meta.js https://userscripts.adtidy.org/release/disable-amp/1.0/disable-amp.meta.js SaferWeb_Anti_Malicious_Scripts_v1.0(local) Google_Reverse_Image_Search_v1(local) Google_Image_Enhancer_v1.0(local) medium.com:_read_unlimited_stories_v0.1(local) GoogleCache

[Sergey-Lyapin]

Unfortunately, we cannot reproduce the issue with your settings.

Please try checking the filters updates, maybe it was already solved. Try to check without third-party userscripts and custom filters. If you’re still able to reproduce the issue, reopen it here. We’d appreciate if you supply additional information or screenshots.