Testing new config
All checks were successful
Remote Deployment Pipeline / Prepare Context (pull_request) Successful in 2s
Remote Deployment Pipeline / Deploy (Staging) (pull_request) Has been skipped
Remote Deployment Pipeline / Deploy (Dev/Preview) (pull_request) Successful in 46s
Remote Deployment Pipeline / Cleanup Preview (pull_request) Has been skipped
Remote Deployment Pipeline / Deploy (Production) (pull_request) Has been skipped

This commit is contained in:
2025-12-19 19:53:51 +01:00
parent 5d5d7e783a
commit 860f4333e1

View File

@@ -1,5 +1,10 @@
# ./traefik/forward-to-legacy-nginx.yaml # ./traefik/forward-to-legacy-nginx.yaml
entryPoints:
web:
# Essential: Allows your routers to intercept /.well-known/acme-challenge/
allowACMEByPass: true
tcp: tcp:
routers: routers:
# Router for HTTPS (Passthrough) # Router for HTTPS (Passthrough)
@@ -23,14 +28,24 @@ tcp:
http: http:
routers: routers:
# Router for HTTP # 1. ROUTE FOR TRAEFIK-MANAGED DOMAINS
# For domains Traefik should handle, send challenges to the internal ACME service.
traefik-acme-handler:
rule: "Host(`test-whoami.kovagoadi.hu`) && PathPrefix(`/.well-known/acme-challenge/`)"
entryPoints:
- "web"
service: "acme-http@internal" # This is the internal service name
priority: 1000 # High priority to ensure it wins
# 2. THE CATCH-ALL ROUTER (LEGACY)
# This remains your broad catch-all. Since it has lower priority,
# the one above handles the Traefik domains, and everything else hits this.
nginx-legacy-router: nginx-legacy-router:
rule: "HostRegexp(`^.+$`)" rule: "HostRegexp(`^.+$`)"
service: nginx-legacy-service service: nginx-legacy-service
# Low priority ensures specific containers are handled first
priority: 1
entryPoints: entryPoints:
- "web" - "web"
priority: 1 # Will catch ACME for any domain NOT listed in the handler above
services: services:
nginx-legacy-service: nginx-legacy-service: