TCP connection failed - Error message

Help
1

I'm seeing this error quite a bit lately:
Connection error (127.0.0.1#5335): TCP connection failed while receiving payload length from upstream (Connection prematurely closed by remote server)

I don't know what the reason is or how to investigate this. Appreciate any help:

Pi-hole debug:
https://tricorder.pi-hole.net/2DAtlszy/

2

I have seen this occasionally since moving to v6 of Pi-hole (once a week or so). There are already forum threads about this issue. Try searching for ‘TCP connection’. There is potentially an unbound config option that might help, but otherwise…it’s more of a warning than anything as I never noticed DNS issues at my clients because of it.

3

Yes, I've seen some of the threads about it but I couldn't find a solution for it. I know this issue was also on v5, but it wasn't reported on that version.

I didn't see which unbound setting I need to modify to resolve this.

4

You may have a look at this: Connection error TCP connection failed - #2 by Bucking_Horn . I changed mine to the recommended 20 from the default of 10, but I still get about the same cadence of the message.

5

Is it under: /etc/unbound/unbound.conf.d ?

6

It’s where ever your unbound configs are. That is ‘a’ general location, but I self build it, so my config is /usr/local/etc/unbound/unbound.conf.d/pi-hole.conf. Did you not install and config it from the Pi-hole guide?

7

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