When I try to see if https://secure.quantserve.com/quant.js is blocked, it's not, it displays the text within in. Regular http version is blocked
root@DietPi:~# pihole -q secure.quantserve.com
Match found in list.0.raw.githubusercontent.com.domains:
secure.quantserve.com
Match found in list.2.sysctl.org.domains:
secure.quantserve.com
Match found in list.6.hosts-file.net.domains:
secure.quantserve.com
debug token: g39xcgeldt
The protocol doesn't matter, both HTTP and HTTPS will be blocked the same. Make sure you are using Pi-hole for DNS on your clients (check if you can reach http://pi.hole/admin).
Hi Mcat12, I definitely am using it. I show up on the console and nearly all ads are blocked otherwise.
edit: actually, the console shows the site to be blocked even when I go the https site, but the content is still displayed. Is this supposed to happen?
If you use nslookup to resolve the domain on the client, ex. nslookup secure.quantserve.com, what is the output?
I only have a Chromebook and there's no nslookup. But tracepath shows it stopping at my pi, and pinging it shows only replies from the pi
ssh into the Pi and run a dig command for that domain.
What do you see on your browser when you try to go to https://secure.quantserve.com/quant.js ? I see a bunch of nonformatted code, is that what is supposed to happen?
root@DietPi:~# dig secure.quantserve.com
; <<>> DiG 9.10.3-P4-Raspbian <<>> secure.quantserve.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23551
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;secure.quantserve.com. IN A
;; ANSWER SECTION:
secure.quantserve.com. 2 IN A 192.168.0.11
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Dec 23 15:22:46 CST 2018
;; MSG SIZE rcvd: 66
I see the same. I had to unblock the site to get to it, as I expect you did as well, since your dig command shows the site is on a block list and is being blocked by your Pi-Hole installation.
No, I didn't unblock it. Console claims blocked but I'm still able to see the code. So there is something goofy with the setup after all
Have you cleared the browser cache or is there a potential alternate path for DNS in your browser (i.e. Firefox DNS over HTTPS)?
Clearing the cache did it, thank you very much for the support!
Going to that js file would give just a bunch of code because that is what the file is.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.