-
fix(gateway): let passthrough targets issue their own certs; HTTPS-only for terminated routes
Release / version (push) Canceled after 0sRelease / frontend (push) Canceled after 0sRelease / linux (amd64) (push) Canceled after 0sRelease / linux (arm64) (push) Canceled after 0sRelease / windows (push) Canceled after 0sRelease / macos (push) Canceled after 0sRelease / release (push) Canceled after 0sBuild and Push Docker Image / build-and-push (push) Canceled after 0sreleased this
2026-10-03 21:14:55 +03:00 | 53 commits to main since this releaseTraefik's built-in HTTP-01 router matches /.well-known/acme-challenge/ on
every host at priority MaxInt and 404s tokens it didn't request, so a
passthrough target (e.g. Dokploy behind *.sslip.io) never got Let's
Encrypt's check and :443 kept Traefik's self-signed cert. The managed
Traefik now sets entryPoints.web.allowACMEByPass; the dynamic file routes
a passthrough host's challenges to the other proxy above our own solver,
which still handles every other host.Routes the gateway terminates (http/redirect) are now HTTPS-only: tls is
forced server-side, the form drops the toggle, wildcards are
passthrough-only, and IP hostnames skip ACME (LE can't issue for IPs).
Re-importing our own file no longer yields the passthrough :80 half or
the ACME routers as separate routes.Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01NvzfeA1V4Faj7FC5qM5b9qDownloads