fix(traefik): Remove conflicting TCP router for subdomain handling

The TCP router was intercepting wildcard subdomain traffic at the TCP layer
and sending it directly to nginx:80, bypassing HTTP routing entirely.
This caused 404 errors because nginx wasn't receiving proper HTTP routing.

Now relying on:
- TLS store's defaultGeneratedCert for wildcard certificate
- HTTP HostRegexp router for subdomain routing to nginx

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
poduck
2025-12-03 17:34:41 -05:00
parent 9cbf19ed1b
commit f3951295ac

View File

@@ -53,29 +53,6 @@ tls:
sans:
- "*.smoothschedule.com"
tcp:
routers:
# Catch-all for tenant subdomains at TLS layer
# This matches any subdomain that isn't handled by specific HTTP routers
subdomain-sni-router:
rule: 'HostSNIRegexp(`.*\\.smoothschedule\\.com`)'
entryPoints:
- web-secure
service: nginx-tcp
tls:
passthrough: false
certResolver: letsencrypt-dns
domains:
- main: "smoothschedule.com"
sans:
- "*.smoothschedule.com"
services:
nginx-tcp:
loadBalancer:
servers:
- address: "nginx:80"
http:
routers:
# Main domain and www