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

**URL:** <https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269>\
**Category:** Help\
**Created:** [May 2, 2018, 11:18am UTC](https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269 "2018-05-02T11:18:04Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![pelangi](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/b19c9b/32.png) [@pelangi](https://discourse.pi-hole.net/u/pelangi)\
**Post date:** [May 2, 2018, 11:18am UTC](https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269/1 "2018-05-02T11:18:04Z")

</div>

## 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.

---

<div class="post-metadata">

**Author:** ![Mcat12](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/mcat12/32/20_2.png) [@Mcat12](https://discourse.pi-hole.net/u/Mcat12)\
**Post date:** [May 2, 2018, 5:01pm UTC](https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269/2 "2018-05-02T17:01:13Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [May 5, 2018, 9:59am UTC](https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269/3 "2018-05-05T09:59:03Z")

</div>

Here are the guides you should follow.

> [@Why do some sites take forever to load when using Pi-hole? (for versions \< v4.0)](https://discourse.pi-hole.net/t/why-do-some-sites-take-forever-to-load-when-using-pi-hole/3654):
>
> 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](https://docs.pi-hole.net/ftldns/blockingmode/#pi-holes-unspecified-ip-blocking-default) and return to the [IP-based mode](https://docs.pi-hole.net/ftldns/blockingmode/#pi-holes-full-ip-blocking). 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)](https://discourse.pi-hole.net/t/why-some-pages-load-slow-when-using-pi-hole-and-how-to-fix-it/6945):
>
> Originally published at: [https://pi-hole.net/2018/02/02/why-some-pages-load-slow-when-using-pi-hole-and-how-to-fix-it/](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](https://docs.pi-hole.net/ftldns/blockingmode/#pi-holes-unspecified-ip-blocking-default) and return to the [IP-based mode](https://docs.pi-hole.net/ftldns/blockingmode/#pi-holes-full-ip-blocking). 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/](https://pi-hole.net/2018/05/18/nxdomain-and-null-blocking-with-ftldns/) Pi-hole can make your network run f…

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

---

<div class="post-metadata">

**Author:** ![pelangi](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/b19c9b/32.png) [@pelangi](https://discourse.pi-hole.net/u/pelangi)\
**Post date:** [May 5, 2018, 12:31pm UTC](https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269/4 "2018-05-05T12:31:59Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Tntdruid](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/tntdruid/32/773_2.png) [@Tntdruid](https://discourse.pi-hole.net/u/Tntdruid)\
**Post date:** [May 5, 2018, 3:25pm UTC](https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269/5 "2018-05-05T15:25:36Z")

</div>

> [@jacob.salmela](#):
>
> FTLDNS with NXDOMAIN blocking

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

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [May 5, 2018, 3:29pm UTC](https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269/6 "2018-05-05T15:29:33Z")

</div>

Add

```auto
BLOCKINGMODE=NXDOMAIN

```

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

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

---

<div class="post-metadata">

**Author:** ![pelangi](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/p/b19c9b/32.png) [@pelangi](https://discourse.pi-hole.net/u/pelangi)\
**Post date:** [May 7, 2018, 1:29am UTC](https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269/7 "2018-05-07T01:29:26Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kalpik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/kalpik/32/3866_2.png) [@kalpik](https://discourse.pi-hole.net/u/kalpik)\
**Post date:** [May 27, 2018, 3:33pm UTC](https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269/8 "2018-05-27T15:33:25Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [May 27, 2018, 3:34pm UTC](https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269/9 "2018-05-27T15:34:48Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [June 17, 2018, 3:34pm UTC](https://discourse.pi-hole.net/t/https-secure-quantserve-com-quant-js-timed-out/9269/10 "2018-06-17T15:34:52Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.