hey, i’ve been tinkering with similar configs. have you tried separating the host and path routing into distinct routers? sometimes traefik seems to prefer more granular rules. how did u decide on your backend labels? it’s quite fun experimenting with these configs.
hey, i’ve had better luck by creatin a seperate router for dashboard routes. some ticky label escapin & rule order tweaks helped clear up docker misbehavin. hope that gives u a hint in sorting it out!
hey, you might wanna split the router rules. i tried that and sometimes traefik doesnt mix host and path well. check your label order and if the path needs exact matching, might be the issue. good luck!
In my experience, configuring Traefik with both host and path routing can be quite reliable if the rules are sufficiently distinct and accurately quoted. Rather than merging the two rules into a single router, consider maintaining clarity through explicit rule definition. I encountered issues when the label syntax got misinterpreted by Docker and Traefik even though the concept was sound. It can help to test the configuration with a minimal setup first. Verifying label syntax and the Traefik version often resolves unexpected routing behaviors, streamlining debugging when integrating advanced routing combinations.
hey, im tinkering with similar setups. have you tried swapping the order of the labels? sometimes the host rule gets evaluated better that way. also, what traefik version are you on? curious if a config tweak helped you too!