# Unable to connect

**URL:** <https://discourse.pi-hole.net/t/unable-to-connect/58427>\
**Category:** Help\
**Tags:** docker\
**Created:** [October 8, 2022, 4:45pm UTC](https://discourse.pi-hole.net/t/unable-to-connect/58427 "2022-10-08T16:45:02Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [October 10, 2022, 7:12am UTC](https://discourse.pi-hole.net/t/unable-to-connect/58427/27 "2022-10-10T07:12:09Z")

</div>

> [@chiragnahata](#):
>
> after running sudo ss cannot find the port 53 listed there

Good - that means port 53 is free now.  
Restarting your Pi-hole container with the correct port mappings for 53 UDP and TCP should have worked then, and obviously, it did. 😉

> [@chiragnahata](#):
>
> But why is it not blocking ads.

You have to configure your network to make use of Pi-hole, see [Post-Install - Pi-hole documentation](https://docs.pi-hole.net/main/post-install/#making-your-network-take-advantage-of-pi-hole).

You can verify if blocking is operational by running the following commands _from a **client** _ that's using Pi-hole for DNS:

```auto
nslookup pi.hole

```

```auto
nslookup flurry.com

```

The latter should result in a `0.0.0.0` reply.

> [@chiragnahata](#):
>
> 2022-10-10  
> 11:17:36 LOAD Long-term load (15min avg) larger than number of processors: 4.9 \> 4  
> This may slow down DNS resolution and can cause bottlenecks.

System load is reported as is via the underlying OS.  
If you run Pi-hole in a virtualised environment, the reported details may not be accurate, see also e.g. [High Load in docker on Synology](https://discourse.pi-hole.net/t/high-load-in-docker-on-synology/55831).

---

_[View the full topic](https://discourse.pi-hole.net/t/unable-to-connect/58427)._