Did not get Pi-hole working in Docker. Disabled AdGuard, but the admin page does not show up.
Now enabled AdGuard. It seems to work, but statistics are not changing. I see in query log new sites appearing, but statistics is the same.
I have added few domais, that show me most ads, but it is not blocking them. Tried to even dublicate.
I just used my phone to test adguard with default settings. Works. All Google ads are being blocked as far as I can see. Stats work also. Though the first time it didn’t work, but I soon realized my phone was still connected with my VPN. Are you sure you test device uses adguard as it’s DNS?
now it is working again. Took a break, and tested if I could get Pi-hole running - NO
It is now blocking some of the track.adform.net stuff, but not all. As i can still see ads, and if I click on it, I see first track.adform.net/xxxx and then i´am redirected to the page the ad was aboud.
Try disabling all the lists and try the one I linked to above. Its an amalgamation of various other lists that wont interfere with each-other.
It’s been my go-to list since I used to just use a browser extension for Ad-blocking, then Pi-Hole, now AdGuard.
Facebook and Youtube are a nightmare to try and block.
The other thing is it may be pulling the adverts through on Cache if they are your usual websites you visit.
On a page with adverts (served from where you KNOW they are blocked) try pressing CTRL&F5. You may find they are hidden then.
Yep, this is what I had to do because systemd-resolved is a DNS service running on port 53. Just make sure your fix is still in place after reboot. I can’t remember what I had to do, because the service kept on restart at reboot.
I think it came in with Ububtu 18.04, not sure though, pretty much first time I have used Ubuntu in anger. Frustrates the hell out of me, can’t get VNC to work, just seems to be a known bug in Ubuntu…
No problem, I’m still looking for the one I had like 3 builds ago. I literally only had the one blocklist and it contained around 300,000 Urls. It was perfect for my uses but never made a note of the name of it. I just remember it was from Github.
Ok guys (tagging @Coedy and @RogTP to make sure you see this), I just figured out that stopping the systemd-resolved service wasn’t the best solution. Because afterwards your systems can’t use any DNS anymore.
But I found a better solution. Make resolved not listen on port 53 while running.
Here are the steps:
Edit (as root) /etc/systemd/resolved.conf and uncomment #DNSStubListener=yes and change it to #DNSStubListener=no
To be honest I don’t remember what I did… Looks like I did point 1, but note it is still commented out. My /etc/resolv.conf is missing and systemd-resolved is disabled. When I do nmcli device show <interfacename> it shows I am using my Adguard instance as DNS.
It was a while ago now, so I suspect I did something else as well…