- Expediere
- 23 septembrie 2026 la 15:59 UTC
- Autor
- Kamo
- Comite
- 334ac8c
Opening a computer landed on the redirect service's fallback page — "the request reached the fallback page instead of being redirected. Check the Host header." Two causes, and each hid behind the other. TRAEFIK WAS NOT WATCHING THE NAMESPACE. **************** listed kamo, mail, kamo-universe, monitoring, default and desktop. Not hosted-computers. So every IngressRoute and Middleware for the gateway was invisible to Traefik: kubectl showed them, their priorities were right, and nothing in the cluster reported a problem, because an unwatched CRD is not an error — it is nothing at all. Requests for computers.<domain> fell through to the catch-all kamo-nowww-route at priority 1 and were answered by the redirect service. `desktop` is on that list for exactly this reason, and the comment above it says "VERIFY this list covers all kamo route namespaces". It was not verified. THE APP WAS AT /guacamole, NOT /. guacamole/guacamole deploys its war as guacamole.war unless WEBAPP_CONTEXT says otherwise, and this deployment never set it — the platform-admin gateway does. Once Traefik could route at all, every link answered a Tomcat 404 that mentions no context path, from a pod whose logs end with "Server startup in 4690 ms". And the probes had to move with it: pointed at /guacamole/ while the app moved to ROOT, the container deployed ROOT.war, answered 404 at the old path, and was killed by its own liveness probe. The path and the context are one decision in two places. Verified end to end: / now 302s to login for a bare visit, and /?data=<token> is served by Guacamole.