Let's Encrypt HTTP-01 requests were reaching ordinary Kubernetes HTTP routes instead of Traefik's internal ACME challenge handler. The CA observed backend responses (404/401/403), so Traefik continued serving its default certificate.
Change
remove the Kubernetes web catch-all redirect Ingress and its backend routes;
rendered resources no longer include the Kubernetes HTTP redirect catch-all;
the Traefik redirect explicitly targets public port 443.
Post-merge acceptance
Verify externally that HTTP redirects to https://<host>/ without :8443, a real HTTP-01 attempt succeeds, and the served certificate has Let's Encrypt issuer/SANs for all four domains.
## Problem
Let's Encrypt HTTP-01 requests were reaching ordinary Kubernetes HTTP routes instead of Traefik's internal ACME challenge handler. The CA observed backend responses (404/401/403), so Traefik continued serving its default certificate.
## Change
- remove the Kubernetes `web` catch-all redirect Ingress and its backend routes;
- restore Traefik entrypoint HTTP-to-HTTPS redirect;
- set the redirect port explicitly to public `443`, preventing internal `:8443` in `Location`;
- keep `web` available for the built-in HTTP-01 challenge router;
- update the ingress decision/runbook.
## Verification
- `git diff --check` passes;
- `kubectl kustomize k3s_rencher/infrastructure/ingress` renders successfully;
- rendered resources no longer include the Kubernetes HTTP redirect catch-all;
- the Traefik redirect explicitly targets public port `443`.
## Post-merge acceptance
Verify externally that HTTP redirects to `https://<host>/` without `:8443`, a real HTTP-01 attempt succeeds, and the served certificate has Let's Encrypt issuer/SANs for all four domains.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Let's Encrypt HTTP-01 requests were reaching ordinary Kubernetes HTTP routes instead of Traefik's internal ACME challenge handler. The CA observed backend responses (404/401/403), so Traefik continued serving its default certificate.
Change
webcatch-all redirect Ingress and its backend routes;443, preventing internal:8443inLocation;webavailable for the built-in HTTP-01 challenge router;Verification
git diff --checkpasses;kubectl kustomize k3s_rencher/infrastructure/ingressrenders successfully;443.Post-merge acceptance
Verify externally that HTTP redirects to
https://<host>/without:8443, a real HTTP-01 attempt succeeds, and the served certificate has Let's Encrypt issuer/SANs for all four domains.8738e3c9d0to875a2fd0f1