Pihole v6 with Unbound - Connection error - Incorrect port in error message

[hartacus]

The issue I am facing:
I have received this error approximately once per day after updating to v6:
"Connection error (127.0.0.1#5535): TCP connection failed while receiving payload length from upstream (Connection prematurely closed by remote server)"
I understand that this is detailed in this bug report, along with a possible fix via Unbound configuration, which I am going to try: TCP connection failed while receiving payload length from upstream
However, the upstream DNS server is Unbound listening on 127.0.0.1#55353. Note that the error message contains the wrong port number, with one digit dropped off the end. Pihole generally works so I don't think it's actually getting the port number wrong, I think it's just a problem with the error message.

Details about my system:
Pihole v6
Raspberry Pi 1 Model B
Raspbian Bookworm
Unbound on local port 55353
Nginx webserver running reverse proxy

Tricorder link: https://tricorder.pi-hole.net/oP5jWUjI/

[Bucking_Horn]

Indeed:

udp:127.0.0.1:55353 is in use by unbound

doesn't match:

WARNING: Connection error (127.0.0.1#5535): TCP connection failed while receiving payload length from upstream (Connection prematurely closed by remote server)

My guess would be that the formatter expects only 4 digits, so 55353 was shortened to 5535.

Am I reading you correctly in assuming that your topic is about that error message, rather than the actual error condition itself?

[hartacus]

Yes that's right, I saw that the error itself has been addressed in other posts and solutions suggested, so I'm trying those solutions at the moment. This ticket is about the error message dropping a digit from the port number (assuming that's what's actually happening).