Connection error (9.9.9.9#53): TCP connection failed while receiving payload length from upstream (Resource temporarily unavailable)

The issue I am facing:
I am getting a new error every few days in v6. :
Connection error (9.9.9.9#53): TCP connection failed while receiving payload length from upstream (Resource temporarily unavailable)

I have searched previous threads, however most are related to unbound.
I am not using unbound, I am using Quad9.

Details about my system:
Here is my debug log: https://tricorder.pi-hole.net/QbhadP4R/

What I have changed since installing Pi-hole:
Updating to V6.

My error is very similar to this:

Today I got another error. It seems to be happening more frequently.

2025-04-09 10:25:15 CONNECTION_ERROR Connection error (149.112.112.112#53): TCP connection failed while receiving payload length from upstream (Connection prematurely closed by remote server)

I see this log message also from time to time. My upstream server is my router in the same network.

Do you only see the error message, or do you also notice that something isn't working correctly?

As far as I can tell, everything is working perfectly.

Not sure if this error message is meaningful but there doesn't seem to be a way to disable this error message either.

Seems to be happening daily now, is this a change in V6?

2025-04-10 15:23:49 CONNECTION_ERROR Connection error (9.9.9.9#53): TCP connection failed while receiving payload length from upstream (Resource temporarily unavailable)

2025-04-11 12:44:20 CONNECTION_ERROR Connection error (149.112.112.112#53): TCP connection failed while receiving payload length from upstream (Connection prematurely closed by remote server)

Connection errors like these were already happening with v5, but Pi-hole v5 simply ignored these errors, without reporting them.

This is not actually a Pi-hole error. Pi-hole v6 is simply identifying and reporting a connection error ("TCP connection failed while receiving payload").

The only difference is: Pi-hole v6 reports the errors.

2 Likes

I see. Is this type of error actionable?
If not, how can I hide them?

Any updates?

I have unchecked Solution because it does not resolve the issue.
If this kind of connection error is not meaningful, users should have the option to hide it even if it means changing a config file manually.

Every week I am seeing at least 10 of these errors and it is becoming like alarm fatigue.