# Connection Errors

**URL:** <https://discourse.pi-hole.net/t/connection-errors/78673>\
**Category:** Help\
**Created:** [March 31, 2025, 4:19pm UTC](https://discourse.pi-hole.net/t/connection-errors/78673 "2025-03-31T16:19:54Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [March 31, 2025, 4:23pm UTC](https://discourse.pi-hole.net/t/connection-errors/78673/2 "2025-03-31T16:23:21Z")

</div>

Your specific cause _ **Connection prematurely closed by remote server** _ when sending DNS requests to _`unbound`_ has been intensively analysed and identified as being caused by specific behaviour of _`unbound`_ terminating queries if it exhausts its TCP connections, see [Two Pi-hole instances, One with "failed to send..." - #44 by DL6ER](https://discourse.pi-hole.net/t/two-pi-hole-instances-one-with-failed-to-send/75057/44).

While there is nothing that could be improved on the Pi-hole side, increasing _`unbound`_'s `incoming-num-tcp` (e.g. to 40) is reported to mitigate the issue, though it may still reoccur under heavy load at times.

In all likelihood, this error has occurred for Pi-hole v5 all along, but Pi-hole v6 started registering it. If you didn't notice any issues with v5, then this is probably nothing to seriously worry about.

---

_[View the full topic](https://discourse.pi-hole.net/t/connection-errors/78673)._