Catch-all router steals traffic due to priority conflicts

Multiple routers match the same request but wrong router wins due to priority. Common with catch-all routers using HostRegexp({any:.+}) or PathPrefix(/). If catch-all has higher or equal priority to specific router, it handles traffic instead. Symptoms: expected router exists and rule matches but traffic goes to different service or returns unexpected responses.

Query routers with 'docker exec traefik wget -qO- http://127.0.0.1:8080/api/http/routers | jq -r ".[] | [.name,.rule,(.priority|tostring)] | @tsv"'. Identify conflicting routers and their priorities. Set explicit priorities with traefik.http.routers.<name>.priority label, higher values win. Keep matching rules simple and specific. Remove or deprioritize catch-all routers. Test routing with actual requests to verify correct router handles traffic.