NGINX
274 incident problems in NGINX environments.
먼저 읽을 가이드
추천 문제
All problems (274)
K8S-1903An Ingress host is valid and one route still 404sOne route still 404s after the Ingress update.KubernetesBeginner6 minFreeK8S-1913An Ingress host is valid and one route still 404sOne route still 404s after the Ingress update.KubernetesBeginner6 minFreeK8S-1953An Ingress host is valid and one route still 404sOne route still 404s after the Ingress update.KubernetesBeginner6 minFreeK8S-1713An Ingress host works and one route still failsOne route still fails after an Ingress host update.KubernetesBeginner6 minFreeK8S-1703An Ingress rule is accepted and one backend still returns errorsOne backend still errors after the Ingress rule was accepted.KubernetesBeginner6 minFreeK8S-1683An Ingress rule is added and one path still 404sOne Ingress path still returns 404 after a routing update.KubernetesBeginner6 minFreeK8S-1783An Ingress rule is valid and one request still 404sA request still 404s after the Ingress rule update.KubernetesBeginner6 minFreeK8S-1613An Ingress change is correct and one path still returns 404One Ingress path still returns 404 after annotation cleanup.KubernetesBeginner7 minFreeK8S-1644An Ingress host is added and one path still failsOne path still fails after an Ingress host update.KubernetesBeginner7 minFreeK8S-1673An Ingress host is added and one path still failsOne Ingress path still fails after a service port name cleanup.KubernetesBeginner7 minFreeK8S-1634An Ingress host is added and one route still failsOne route still fails after an Ingress host update.KubernetesBeginner7 minFreeK8S-1654An Ingress host is added and one route still failsOne route still fails after an Ingress host update.KubernetesBeginner7 minFreeK8S-1664An Ingress host is added and one route still failsOne route still fails after an Ingress host update.KubernetesBeginner7 minFreeK8S-1694An Ingress host is added and one route still failsOne route still fails after an Ingress host update.KubernetesBeginner7 minFreeK8S-1624An Ingress TLS secret is ready and one host still failsOne host still fails TLS after an Ingress hostname update.KubernetesBeginner7 minFreeNETWORK-020The CDN cache is fine, but a TLS version difference with the origin fails only miss requestsA situation where most requests are cache hits and look fine, but origin communication breaks only in the cache-miss segment.ReviewedNetworkIntermediate24 minProK8S-002Analyzing a service failure where the Pod is Running but receives no trafficA scenario for step-by-step checking of Service, Endpoint, readiness probe, and selector mismatch possibilities.KubernetesIntermediate22 minProSECURITY-002An intermediate certificate chain problem that fails only on certain clientsThe latest browsers connect fine, but some clients fail TLS verification because the server does not send the complete certificate chain.SecurityIntermediate21 minProNETWORK-1205Proxy health page is green but user traffic still failsA proxy health endpoint looks fine, but actual user traffic still fails because the TLS hostname path chooses a different upstream certificate or route than the simple health check.NetworkIntermediate19 minProK8S-009Only certain APIs return 404 due to an Ingress path-rewrite rule mismatchCovers a path-rewrite problem where health checks pass but only real user requests fail.KubernetesIntermediate24 minPro