***edit/update ****- 16/02/24 - this issue is with the ISP and has nothing much to do with adblocker. *
media.themoviedb.org from 192.168.1.100
09:12:14: forwarded media.themoviedb.org to 127.0.0.1#5335
09:12:14: reply media.themoviedb.org is <CNAME>
09:12:14: reply tmdb-web-image-prod.b-cdn.net is 103.180.115.15
09:12:14: reply media.themoviedb.org is <CNAME>
09:12:14: reply tmdb-web-image-prod.b-cdn.net is NODATA
As of now, now i have tried all possible ways to troubleshoot (some were asked by pihole dev team to test)
a) disabled unbound
b) disabled/alter adblock filter lists.
c) one point of time i have deleted entire Adblock list - that too didn’t made any difference.
d) disable adblock for 10/30 minute from dashboard.
here is the images with all adblocking/regex disabled:
in nutshell, regardless my configuration if im using pihole dns it is breaking TMDB, if i change DNS to any public like 9.9.9.11 or 1.1.1.1, there is no issues with the site.
Today i attempted to downgrade pihole to previous version ( which is confusing and complicated), ended up corrupting the installation.
Hence had to do a complete clean installation - its still breaking this perticular site.
Anyone has any suggestion how to fix this, and if im missing something vital to troubleshoot.
I really want to stay in pihole, i liked the device grouping and i use that extensively. but if its breaking site like this ( plus dont know what else its breaking) - i have to move away from it.
strange, can you change dns to 1.1.1.1 or 9.9.9.11 and check?
as if i change the dns it solves the issue at my end.
yes… for me too that means the issue is not related to the adblock list, rather why ways these DNS server acts. of in this particular case interacting with this website. .
i just added new image in my previous post, disabling all adblocks lists.. issues remains the same.
here the website with quad9, 9.9.9.11 DNS
yes, TVDB i use primarily for TV series,
for library updates it should use API of TMDB not the web, but tmdb’s API is broken for long time now, it only work if has the mood to work . hence using tvdb as fallback for some time now.
for movies they are ok-ok.. good in terms of they have a good quality control of images ( but not better than fanart), but the metadata is still at early stages.
I absolutely have 0 issues anywhere else. If this is the only site which may have issues with DNS based adblockers then I can live with it.
Although I’m pretty sure this is not an issue of adblockers as the image opens fine it definitely is an issue with the website.
I have been using Adguard on my Asus router for several years and it works well on limited resources. But once in a while it ends up getting killed and blocking all DNS requests.
I use the built-in Diversion adblocker on the router now. It has a basic GUI within the router GUI to manage blocklists and update, though logs have to accessed using SSH.
Little to differentiate in the implementation of adblockers. However, TMDB itself perennially has issues.
Monitor your RAM on the router maybe it’s getting filled up.
I’m using Adguard on an x86 router with just 1GB RAM since almost 2 years and it’s stable AF.
Probably, RAM usage is nearly always close to the full 512 MB even with Diversion. I had created a swap file specifically for that purpose, so found this behaviour a bit odd, especially when I am not at home and the net stops working for family members due to the adblocker.
Maybe you need to revisit your block lists. As mine works fine. I am using own recursive unbound instance as well for upstream in pihole(both on RPi). What’s your upstream DNS server in pihole?
Probably, have an old Windows tablet already that does all the server duties while also being a home dashboard. Had Adguard Home running with WSL on that few years ago but it was quite unstable.
Anyway Diversion on the router seems quite stable now, so will keep monitoring it.
yes. first their API broken and not the website.
I have raised this issue with tmdb admin team. seem lots of people facing issues and the main guy who handles the website is not around.
