# Slow loading sites on Unifi Equipment

**URL:** <https://discourse.pi-hole.net/t/slow-loading-sites-on-unifi-equipment/6553>\
**Category:** Help\
**Created:** [January 14, 2018, 3:52pm UTC](https://discourse.pi-hole.net/t/slow-loading-sites-on-unifi-equipment/6553 "2018-01-14T15:52:02Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kyle\_LeFevre](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@Kyle\_LeFevre](https://discourse.pi-hole.net/u/Kyle_LeFevre)\
**Post date:** [January 14, 2018, 3:52pm UTC](https://discourse.pi-hole.net/t/slow-loading-sites-on-unifi-equipment/6553/1 "2018-01-14T15:52:02Z")

</div>

I have a new network setup and am I'm trying to get my new pi-hole working. My equipment is: Ubiquiti USG (router/firewall), 8-port managed switch, and AP AC Lite. Pi-hole is on subnet 192.168.1.x along with the USG.

I don't believe that there is an issue with the communication on the network and the pi-hole.

When I connect to websites the typical behavior is that non-blocked items are loading, then blocked items will sit and try to connect until they timeout. Below is the Chrome inspector from pi-hole's ad page as an example.

 ![test](https://discourse.pi-hole.net/uploads/default/original/2X/2/2b13909ffba5350d8024cba09f0cacb41419ed77.jpg)

I did change the iptables per previous posts on the forum and did not see any change in behavior. I have ipv6 disabled on my modem and by default the unifi equipment does have ipv6.

## Debug Token:

9nrsxtqcdm

---

<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:** [January 14, 2018, 9:15pm UTC](https://discourse.pi-hole.net/t/slow-loading-sites-on-unifi-equipment/6553/2 "2018-01-14T21:15:43Z")

</div>

What does the Timing tab look like on one of those blocked requests?

---

<div class="post-metadata">

**Author:** ![Kyle\_LeFevre](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@Kyle\_LeFevre](https://discourse.pi-hole.net/u/Kyle_LeFevre)\
**Post date:** [January 14, 2018, 10:59pm UTC](https://discourse.pi-hole.net/t/slow-loading-sites-on-unifi-equipment/6553/4 "2018-01-14T22:59:23Z")

</div>

Sorry, I’m not sure exactly what you mean by the timing tab.

The two blocked JavaScript items are connections that timed out after 22 seconds.

---

<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:** [January 15, 2018, 11:05am UTC](https://discourse.pi-hole.net/t/slow-loading-sites-on-unifi-equipment/6553/5 "2018-01-15T11:05:26Z")

</div>

If you click on one of the requests in the dev tools (such as in your screenshot), it opens up with the request information, including a tab called Timing.

If you try to connect to the web interface over https, does it time out?

---

<div class="post-metadata">

**Author:** ![Kyle\_LeFevre](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@Kyle\_LeFevre](https://discourse.pi-hole.net/u/Kyle_LeFevre)\
**Post date:** [January 15, 2018, 2:18pm UTC](https://discourse.pi-hole.net/t/slow-loading-sites-on-unifi-equipment/6553/6 "2018-01-15T14:18:29Z")

</div>

Ok thanks.Here is the timing tab:

 ![timing](https://discourse.pi-hole.net/uploads/default/original/2X/0/0b2f38d5be80c1b57a28ce1e75c29bcd4aef82a1.png)

Yes the web interface times out if I try to connect via https.

---

<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:** [January 15, 2018, 9:22pm UTC](https://discourse.pi-hole.net/t/slow-loading-sites-on-unifi-equipment/6553/7 "2018-01-15T21:22:51Z")

</div>

Do you have custom firewall rules in place? What is the output of the following two commands?

```bash
sudo iptables -L
sudo ip6tables -L

```

---

<div class="post-metadata">

**Author:** ![Kyle\_LeFevre](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@Kyle\_LeFevre](https://discourse.pi-hole.net/u/Kyle_LeFevre)\
**Post date:** [January 15, 2018, 11:25pm UTC](https://discourse.pi-hole.net/t/slow-loading-sites-on-unifi-equipment/6553/8 "2018-01-15T23:25:27Z")

</div>

I do, here are the current rules.

 ![firewallrules](https://discourse.pi-hole.net/uploads/default/original/2X/b/b010335d2d28685d11afc6b14a566fde63e90bb8.png)

---

<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:** [January 16, 2018, 8:14pm UTC](https://discourse.pi-hole.net/t/slow-loading-sites-on-unifi-equipment/6553/9 "2018-01-16T20:14:24Z")

</div>

Have you seen this already?

> [@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…

Do you have a Linux computer (not the Pi-hole itself) at hand that shows these slow loading problems?

If so, please run

```auto
nmap --reason pi.hole -p443 # for TCP
sudo nmap --reason pi.hole -p443 -sU # for UDP

```

I get:

```plaintext
PORT STATE SERVICE REASON
443/tcp closed https conn-refused

PORT STATE SERVICE REASON
443/udp closed https port-unreach ttl 64

```

and that _with and without_ any firewall rules on my Pi-hole.