Https://secure.quantserve.com/quant.js timed out

[pelangi]

Expected Behaviour:

Just as the http equivalent, I should see this blocked

Actual Behaviour:

Timed out

Debug Token:

ztbu6pc7va

I noticed massive slowness in some web pages and even though I can see the web page it actually takes so long for the page to be fully loaded.

Reading this article and this article, I have enabled ULA and updated iptables but it doesn't seem to help.

I have done testings using secure.quantserve.com/quant.js which shows blocked instaneously over HTTP. However I got timed out over HTTPS. Is it expected? Or something wrong with my setup? Please help. Thank you.

[Mcat12]

I don't see anything related. If you're unable to find the firewall rule or whatever is causing blocked HTTPS to be slow, you could test out NXDOMAIN blocking in the FTLDNS beta.

[jacob.salmela]

Here are the guides you should follow.

Why do some sites take forever to load when using Pi-hole? (for versions < v4.0)

Update: 2018-08-06 As of v4.0, this should no longer be a problem unless you choose to deviate from the new default blocking mode and return to the IP-based mode. And the iptables rules mentioned in this article should not be needed. Update As of v3.1 the first reason should not be an issue anymore That being said, there are generally two reasons this happens: your ISP changes your IPv6 address (Global Unicast Address), causing Pi-hole to become misconfigured and timing out when trying…

Why Some Pages Load Slow When Using Pi-hole And How To Fix It (for versions < v4.0)

Originally published at: https://pi-hole.net/2018/02/02/why-some-pages-load-slow-when-using-pi-hole-and-how-to-fix-it/ Update: 2018-08-06 As of v4.0, this should no longer be a problem unless you choose to deviate from the new default blocking mode and return to the IP-based mode. Update: 2018-05-26 This problem is far less likely to happen when using NXDOMAIN or NULL blocking: https://pi-hole.net/2018/05/18/nxdomain-and-null-blocking-with-ftldns/ Pi-hole can make your network run…

And as @Mcat12 mentioned, FTLDNS with NXDOMAIN blocking will not need the firewall rules.

[pelangi]

Thanks @jacob.salmela. I switched to FTLDNS and don't have these issues any more.

[Tntdruid]

@jacob.salmela

FTLDNS with NXDOMAIN blocking

Cant find any where to set that in FTLDNS
@jacob.salmela

[DL6ER]

Add

BLOCKINGMODE=NXDOMAIN

in your /etc/pihole/pihole-FTL.conf and restart pihole-FTL.

We'll publish the official documentation for FTLDNS shortly. Although it is not yet complete, details concerning the NXDOMAIN blocking are already included.

[pelangi]

Note that /etc/pihole/pihole-FTL.conf may not exist yet and you need to create it. I did.

[kalpik]

I have the same issue. HTTPS times out. I think I'm using FTLDNS (not beta). Anything else I can try?

[jacob.salmela]

_FTL_DNS is only in beta now. Did you restart after making the change to the config file?