Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
I should access APK mirror.
Example url: https://www.apkmirror.com/
From either chrome or firefox, from my Note20ultra android 13 phone.
Actual Behaviour:
I get errors that im using adblocker...as if it detects pihole somehow...
(It worked in the past).
Seems like one of the block lists in use could be the issue. Have you tried (after a while, as there was a tempban in place) using the disable pihole in the webgui to see if that made a difference?
If the site works then it's likely that the filters in use on your setup were causing the issue.
Hi thanks,
Yes that exactly what I tried and why I posted in discourse.
Its very unusual to me that a website detects pihole in that way. And when I check the query list, the main website is allowed.
I have Pihole running with the default adlist only. I tested the site and worked ok for me. This is likely not the actual apkmirror domain tripping this but an adblock tester they are trying to load. If it doesn't, then the site assumes your adblocking. One thing you can try is login into the pihole and tail the output. This can be done from the command line ( pihole -t or pihole -t >test.txt if you want to view it in an editor etc ) or you can do it via the gui under tools > Tail Pihole.log
Also, not sure if you did this or not but to ensure its the pihole, have you turned off adblocking for a time frame and then tested? If you do so make sure to clear cookies / refresh the page.
Yes I tested turning off pihole for a small duration and it worked, I accessed the site...
I also tailed the pihole and checked queries, the obvious one are working and some weird ones not... (Blocked).
Interesting. I tried to break the site by disabling java script and disabling some of the allowed domains like instant.page with no luck. It still blocks ads and still lets me use the site.
If its working when you disable pihole then it would seem to be something in the adlists. Perhaps using firefox debug tool could shed some light on it?
Do you have more that one adlist running? If so, perhaps try and disable one list at a time and check? Other that, Nothing else comes to mind to try.
Dec 30 15:13:18: query[A] www.apkmirror.com from 192.168.2.1 Dec 30 15:13:18: forwarded www.apkmirror.com to 208.67.220.220 Dec 30 15:13:18: query[HTTPS] www.apkmirror.com from 192.168.2.1 Dec 30 15:13:18: forwarded www.apkmirror.com to 208.67.220.220 Dec 30 15:13:18: reply www.apkmirror.com is 104.19.134.58 Dec 30 15:13:18: reply www.apkmirror.com is 104.19.135.58 Dec 30 15:13:18: reply www.apkmirror.com is 104.19.136.58 Dec 30 15:13:18: reply www.apkmirror.com is 104.19.132.58 Dec 30 15:13:18: reply www.apkmirror.com is 104.19.133.58 Dec 30 15:13:18: reply www.apkmirror.com is Dec 30 15:13:18: query[A] html-load.com from 192.168.2.1Dec 30 15:13:18: gravity blocked html-load.com is 0.0.0.0 Dec 30 15:13:18: query[HTTPS] html-load.com from 192.168.2.1 Dec 30 15:13:18: gravity blocked html-load.com is NODATADec 30 15:13:18: query[A] www.googletagmanager.com from 192.168.2.1Dec 30 15:13:18: gravity blocked www.googletagmanager.com is 0.0.0.0 Dec 30 15:13:18: query[HTTPS] www.googletagmanager.com from 192.168.2.1 Dec 30 15:13:18: gravity blocked www.googletagmanager.com is NODATADec 30 15:13:18: query[A] stats.wp.com from 192.168.2.1Dec 30 15:13:18: gravity blocked stats.wp.com is 0.0.0.0 Dec 30 15:13:18: query[HTTPS] stats.wp.com from 192.168.2.1 Dec 30 15:13:18: gravity blocked stats.wp.com is NODATADec 30 15:13:18: query[A] instant.page from 192.168.2.1Dec 30 15:13:18: gravity blocked instant.page is 0.0.0.0 Dec 30 15:13:18: query[HTTPS] instant.page from 192.168.2.1 Dec 30 15:13:18: gravity blocked instant.page is NODATADec 30 15:13:18: query[A] fonts.googleapis.com from 192.168.2.1 Dec 30 15:13:18: forwarded fonts.googleapis.com to 208.67.220.220 Dec 30 15:13:18: query[HTTPS] fonts.googleapis.com from 192.168.2.1 Dec 30 15:13:18: forwarded fonts.googleapis.com to 208.67.220.220 Dec 30 15:13:18: query[A] fonts.gstatic.com from 192.168.2.1 Dec 30 15:13:18: forwarded fonts.gstatic.com to 208.67.220.220 Dec 30 15:13:18: query[HTTPS] fonts.gstatic.com from 192.168.2.1 Dec 30 15:13:18: forwarded fonts.gstatic.com to 208.67.220.220 Dec 30 15:13:18: query[A] fb.html-load.com from 192.168.2.1 Dec 30 15:13:18: forwarded fb.html-load.com to 208.67.220.220 Dec 30 15:13:18: query[HTTPS] fb.html-load.com from 192.168.2.1 Dec 30 15:13:18: forwarded fb.html-load.com to 208.67.220.220 Dec 30 15:13:18: query[A] ads.pro-market.net from 192.168.2.1Dec 30 15:13:18: gravity blocked ads.pro-market.net is 0.0.0.0 Dec 30 15:13:18: query[HTTPS] ads.pro-market.net from 192.168.2.1 Dec 30 15:13:18: gravity blocked ads.pro-market.net is NODATADec 30 15:13:18: query[A] static.cloudflareinsights.com from 192.168.2.1Dec 30 15:13:18: gravity blocked static.cloudflareinsights.com is 0.0.0.0 Dec 30 15:13:18: query[HTTPS] static.cloudflareinsights.com from 192.168.2.1 Dec 30 15:13:18: gravity blocked static.cloudflareinsights.com is NODATADec 30 15:13:18: query[A] cmp.inmobi.com from 192.168.2.1 Dec 30 15:13:18: cached cmp.inmobi.com is Dec 30 15:13:18: forwarded cmp.inmobi.com to 208.67.220.220 Dec 30 15:13:18: reply fonts.googleapis.com is 142.250.203.106 Dec 30 15:13:18: query[HTTPS] cmp.inmobi.com from 192.168.2.1 Dec 30 15:13:18: forwarded cmp.inmobi.com to 208.67.220.220 Dec 30 15:13:18: reply fonts.gstatic.com is Dec 30 15:13:18: reply fonts.gstatic.com is 216.58.215.227 Dec 30 15:13:18: reply fonts.googleapis.com is NODATA Dec 30 15:13:18: reply fb.html-load.com is 34.117.56.93 Dec 30 15:13:18: reply fb.html-load.com is NODATA Dec 30 15:13:18: reply cmp.inmobi.com is Dec 30 15:13:18: reply cmp-prod.inmobi-choice.io is Dec 30 15:13:18: reply d23sp3kzv1t6m5.cloudfront.net is NODATA Dec 30 15:13:18: reply cmp.inmobi.com is Dec 30 15:13:18: reply cmp-prod.inmobi-choice.io is Dec 30 15:13:18: reply d23sp3kzv1t6m5.cloudfront.net is 3.165.190.74 Dec 30 15:13:18: reply d23sp3kzv1t6m5.cloudfront.net is 3.165.190.93 Dec 30 15:13:18: reply d23sp3kzv1t6m5.cloudfront.net is 3.165.190.18 Dec 30 15:13:18: reply d23sp3kzv1t6m5.cloudfront.net is 3.165.190.25 Dec 30 15:13:18: query[A] api.cmp.inmobi.com from 192.168.2.1 Dec 30 15:13:18: cached api.cmp.inmobi.com is Dec 30 15:13:18: forwarded api.cmp.inmobi.com to 208.67.220.220 Dec 30 15:13:18: query[HTTPS] api.cmp.inmobi.com from 192.168.2.1 Dec 30 15:13:18: forwarded api.cmp.inmobi.com to 208.67.220.220 Dec 30 15:13:18: query[A] content-loader.com from 192.168.2.1Dec 30 15:13:18: gravity blocked content-loader.com is 0.0.0.0 Dec 30 15:13:18: query[HTTPS] content-loader.com from 192.168.2.1 Dec 30 15:13:18: gravity blocked content-loader.com is NODATADec 30 15:13:18: query[A] fb.content-loader.com from 192.168.2.1 Dec 30 15:13:18: forwarded fb.content-loader.com to 208.67.220.220 Dec 30 15:13:18: query[HTTPS] fb.content-loader.com from 192.168.2.1 Dec 30 15:13:18: forwarded fb.content-loader.com to 208.67.220.220 Dec 30 15:13:18: reply api.cmp.inmobi.com is Dec 30 15:13:18: reply cmp-api-prod.inmobi-choice.io is Dec 30 15:13:18: reply choice-apis-prod-2120274730.eu-central-1.elb.amazonaws.com is 3.125.85.10 Dec 30 15:13:18: reply choice-apis-prod-2120274730.eu-central-1.elb.amazonaws.com is 3.127.93.12 Dec 30 15:13:18: reply choice-apis-prod-2120274730.eu-central-1.elb.amazonaws.com is 3.67.53.50 Dec 30 15:13:18: reply api.cmp.inmobi.com is Dec 30 15:13:18: reply cmp-api-prod.inmobi-choice.io is Dec 30 15:13:18: reply choice-apis-prod-2120274730.eu-central-1.elb.amazonaws.com is NODATA Dec 30 15:13:18: reply fb.content-loader.com is 34.117.56.93 Dec 30 15:13:18: reply fb.content-loader.com is NODATA Dec 30 15:13:21: query[A] ssl.gstatic.com from 192.168.2.1 Dec 30 15:13:21: cached ssl.gstatic.com is 142.250.203.99 Dec 30 15:13:21: query[HTTPS] ssl.gstatic.com from 192.168.2.1 Dec 30 15:13:21: forwarded ssl.gstatic.com to 208.67.220.220 Dec 30 15:13:21: reply ssl.gstatic.com is NODATA Dec 30 15:13:29: query[A] www.google.com from 192.168.2.1 Dec 30 15:13:29: cached www.google.com is 142.250.203.100
This is your likely culprit. You are blocking this while I'm not. If I block this, I get the same result.
From the pihole you can run pihole query content-loader.com and see what ad list this is part of or if its a regex entry.
When you remove it / or whitelist it make sure to clear cookies on what ever machine you test.
Thanks a lot,
Its a bit strange... I did a backup of teleport within pihole and created a new sd card with new os on my raspberry pi 2. (I still had a debian 10 old crap)
I reinstalled pihole and imported the backup from teleport.
I tested edge and I no longer get the problem...
Im testing from the phone and no longer get the problem either.
Pihole access works and the router is set to use it as dns (i can pihole admin)
I dont understand why, especially since I backup/import the very same teleport settings...
All i have is new raspbian os, fresh pihole (but was already latest version before)...and reimported...
Everything was working fine expect apkmirror, and that started only few weeks ago no more.
It seems with your command that the same content is blocked still now but it works properly now...
Anyway unfortunately its a bit of mystery and I managed to make it work not knowing how exactly...
Its likely you were using a cookie for the site when it was working. They can have long expiration times. Go to the pihole admin page and in domains, white list content-loader.com. In firefox you can clear cookies in Setting > Privacy and under Cookies and Data use the clear data button. Then retest the site.
