I am getting this error
Connection error (1.1.1.1#53): TCP connection failed while receiving payload length from upstream (Resource temporarily unavailable)
it strange, it happened after setting a static IP on the host and disabling DHCP on the router
I hate always used pi-hole for DHCP but the router was set to only respond to the docker host machine
connect to everything seems fine as far as I know
The problem seems to have gone away on its own
Please run docker exec <containername> pihole -d or generate a debug in the webUI and share the debug link so one of the devs can take a look.
From V6 it has been removed from the web hi
And you need an extra flag for uploading it
sudo docker exec pi-hole pihole -d -a
Your debug token is: https://tricorder.pi-hole.net/sOyDOpQs/
Debug log looks OK.
Screenshot says there is a connection error to 1.1.1.1, which suggests perhaps a temporary routing issue 2 days ago at around 13:00.
Maybe check router logs to see if there was any issues with connection to the internet 
I wish I could
The Linksys mesh I have has no logs
I have been having connectivity issues with the child node that connects the pi-hole server
But it was not showing as disconnected at the time pi-hole said it had connection issues
If anyone knows a way to get logs, the devices are Linksys SPNX55GC-UK
I know that’s slightly off topic, but there nodes are driving my crazy at the minute, normally disconnecting around 6-7PM
And just to make it clear, how the device topology is:
Fibre box - parent node(wired) - child node(wireless) - Raspberry Pi(wired to child node)
So maybe the child node went down for less time, that it takes to change it’s light to red
I did have issues with a Linksys live chat yesterday kept saying connecting
Again Sorry it’s slightly off topic, but could help with a solution
That’s what I thought after having a Quick Look
Even straight after there was no errors logged
So it looks like it was probably the child node disconnecting
I think I may have discovered something, that could be the cause of some of my issues, the child node just went down while the docker host raspberry pi was backing up with rsync to another raspberry pi
This sometimes causes high load and slow DNS response
So if the DHCP server briefly becomes unavailable
Would the child node still have internet connectivity?
I don’t know if I am right here, but I believe the device keeps its DHCP lease even if the server is offline
So it could be pi-hole being slowed down, causing the child node to go down, causing pi-hole to have a connection error
I think part of my issue could have been WPA2/WPA3 mixed, switching to WPA3 only the node did not connect, changing to WPA2 it connected
Docker containers have no way to communicate to the host that a file is locked, such as the pi-hole DB. Using rclone on a running docker container's mounts can cause unexpected issues. If you'd like to rclone/backup files from containers, the recommended way is to shut them down first.
I'd suspect this is the cause of your issues.
Maybe that has been a problem all along
the only problem with that is I think the cache resets, and it would have to be scheduled in the night, when nobody is using pi-hole
But then if the docker host raspberry pi get high load during the backup and watchdog reboots it
the docker host raspberry pi is in my bedroom, Raspberry pi 5 with the active cooler, I lock the fan off during the night, but if it reboots it runs automatically again
The issue did seem to be the node maybe disconnecting or losing its IP address
I changed the node to WPA2 instead of WPA2/WPA3 mixed and it has not gone offline since and pi-hole has not had the connection error since
Why did I said that, the node disconnected again and pi-hole get the same connection error
The message is not saying Pi-hole caused the connection error. Pi-hole just noticed there was a connection failure. This happens even if there is a small temporary connection failure.
Also, the code for detecting and printing the TCP connection failed ... (Resource temporarily unavailable) message didn't exist in Pi-hole v5.
Probably this issue was always there, but Pi-hole v5 never showed the message because it couldn't detect it. Now v6 shows the message.
It was always there, the node must be disconnecting for like milliseconds, the led stays blue, which means it working normally, if it loses connection it should flash red
It’s confusing and sort of irrelevant here though
Linksys have no idea why it does it
