Files
shorty/traefik-kutt-timeout.example.yml
mifi 29be8d6307
Some checks failed
ci/woodpecker/push/ci Pipeline failed
ci/woodpecker/push/deploy unknown status
Fixes for timeouts (maybe?) and fix for Traefik Basic Auth password
2026-02-07 14:11:44 -03:00

18 lines
874 B
YAML

# Example Traefik dynamic config: longer backend timeout for Kutt.
#
# Use a SEPARATE file (e.g. serverstransports.yaml or kutt-timeout.yaml), NOT inside
# routers.yaml — Traefik can reject serversTransports in a file it treats as routers-only.
# Place this file in the same directory as your other dynamic config (e.g. /etc/traefik/conf.d/)
# so the file provider picks it up.
#
# Then uncomment the serversTransport label on the kutt service in docker-compose.portainer.yml.
#
# responseHeaderTimeout: time to wait for backend response headers (0 = no timeout).
# 300s helps avoid 504 Gateway Timeout when Kutt or OIDC is slow.
# If 504s persist, also raise entrypoint transport.respondingTimeouts.readTimeout in Traefik static config.
http:
serversTransports:
kutt-long-timeout:
forwardingTimeouts:
responseHeaderTimeout: "300s"