fix: Explicitly exclude ACME challenge path from HTTPS redirect
- Add explicit exclusion of /.well-known/acme-challenge from catch-all redirect - Ensures ACME challenges are never redirected to HTTPS - Traefik handles ACME challenges automatically, but explicit exclusion is safer
This commit is contained in:
@@ -54,7 +54,8 @@ services:
|
||||
|
||||
# Global redirect to HTTPS (lower priority, matches everything else)
|
||||
# ACME challenges are excluded from redirect automatically by Traefik
|
||||
- "traefik.http.routers.http-catchall.rule=HostRegexp(`{host:.+}`)"
|
||||
# Explicitly exclude ACME challenge path to be safe
|
||||
- "traefik.http.routers.http-catchall.rule=HostRegexp(`{host:.+}`) && !PathPrefix(`/.well-known/acme-challenge`)"
|
||||
- "traefik.http.routers.http-catchall.entrypoints=web"
|
||||
- "traefik.http.routers.http-catchall.middlewares=redirect-to-https"
|
||||
- "traefik.http.routers.http-catchall.priority=1"
|
||||
|
||||
Reference in New Issue
Block a user