# Traefik's 60-Second readTimeout Covers the Whole Request Body

DevFeed: [Traefik's 60-Second readTimeout Covers the Whole Request Body](<https://devfeed.tech/articles/traefik-s-60-second-readtimeout-covers-the-whole-request-body-58581.md>)

Original publisher: [Read original article](<https://philipptheserver.com/posts/traefik-readtimeout-request-body/>)

Author: Philipp Lehmann (philipp.lehmann@gruppe.ai)

Published: 2026-09-23T07:00:00Z

Content type: tutorial

Language: en

Sources: [Philipp Lehmann](<https://devfeed.tech/sources/philipp-lehmann.md>)

Topics: [traefik](<https://devfeed.tech/topics/traefik.md>), [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Nextcloud](<https://devfeed.tech/topics/nextcloud.md>), [browser](<https://devfeed.tech/topics/browser.md>), [cephfs](<https://devfeed.tech/topics/cephfs.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [cephfs](<https://devfeed.tech/tags/cephfs.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [networking](<https://devfeed.tech/tags/networking.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [server](<https://devfeed.tech/tags/server.md>), [testing](<https://devfeed.tech/tags/testing.md>), [traefik](<https://devfeed.tech/tags/traefik.md>)

## AI overview

This troubleshooting article explains how a Traefik read timeout caused slow Nextcloud uploads to be truncated. It identifies the inner cluster Traefik as the limiting hop and clarifies that the default 60-second timeout covers reading the entire request body, not just the headers or gaps between packets.

## Source excerpt

"Expected filesize of 104857600 bytes but read 29491200": Traefik's readTimeout defaults to 60s and bounds the whole request body, so slow uploads get cut.