Error while Peeking first byte read: connection timed out

Traefik Traefik v2
1

Traefik inside docker swarm with 4 nodes keeps showing the following error in the logs, which could be generating these errors

time="2024-01-09T08:48:02-03:00" level=error msg="Error while Peeking first byte: read tcp xxxxxxx:443->xxxxxxx:52442: read: connection timed out"
time="2024-01-09T08:48:02-03:00" level=error msg="Error while Peeking first byte: read tcp xxxxxxx:443->xxxxxxx:52440: read: connection timed out"
time="2024-01-09T08:48:02-03:00" level=error msg="Error while Peeking first byte: read tcp xxxxxxx:443->xxxxxxx:59646: read: connection timed out"
time="2024-01-09T08:48:14-03:00" level=error msg="Error while Peeking first byte: read tcp xxxxxxx:443->xxxxxxx:57658: read: connection timed out"
time="2024-01-09T08:48:16-03:00" level=error msg="Error while Peeking first byte: read tcp xxxxxxx:443->xxxxxxx:32344: read: connection timed out"
time="2024-01-09T08:48:33-03:00" level=error msg="Error while Peeking first byte: read tcp xxxxxxx:443->xxxxxxx:53980: read: connection timed out"
time="2024-01-09T08:49:00-03:00" level=error msg="Error while Peeking first byte: read tcp xxxxxxx:443->xxxxxxx:11174: read: connection timed out"
time="2024-01-09T08:49:02-03:00" level=error msg="Error while Peeking first byte: read tcp xxxxxxx:443->xxxxxxx:52359: read: connection timed out"
time="2024-01-09T08:49:06-03:00" level=error msg="Error while Peeking first byte: read tcp xxxxxxx:443->xxxxxxx:3402: read: connection timed out"
time="2024-01-09T08:49:45-03:00" level=error msg="Error while Peeking first byte: read tcp xxxxxxx:443->xxxxxxx:40723: read: connection timed out"
2

Share your full Traefik static and dynamic config, and docker-compose.yml if used.

Enable and check Traefik debug log (doc) and Traefik access log in more detailed JSON format (doc).

You removed the IPs, so we can’t see if these are external or internal connections. If it’s external, a lot of people are scanning and testing servers for vulnerabilities all day long.

Seemingly related post (link).

I don’t think it’s a Docker Swarn network issue, as we usually see "Bad Gateway" errors there or connections fail because of wrong MTU, but that does not concern the first byte, but rather > 1400 bytes.

3

I've noticed these kind of errors too. In my case, the pattern is x.x.x.x:443->y.y.y.y:z, where x.x.x.x is the traefik container local ip address (docker), y.y.y.y is a seemingly random ip, and z is a random port. I was concerned that my vps is corrupted, but the linked post states that y.y.y.y wants to connect to traefik, not the other way around.

Looking at my log entries I've found ~400 of these in the past 24 hours. (Additionally, I have crowdsec configured with fbonalair/traefik-crowdsec-bouncer forward auth and I can see a lot of 404s and 403s in the logs, but no corellation.)

Is this something to be concerned about? (My guess is no.)

4

Public Internet, loads of bad actors are trying to hack your system 24/7. I would think this is normal, make sure to always keep Traefik up to date.