NGINX
274 incident problems in NGINX environments.
먼저 읽을 가이드
추천 문제
All problems (274)
LINUX-1265A reverse proxy only breaks WebSocket auth flowsLinux incident scenario used for structured troubleshooting practice.LinuxIntermediate16 minProLINUX-1270A reverse proxy only breaks WebSocket auth flowsAn authentication layer added at the reverse proxy works for ordinary pages and suddenly breaks upgraded connections or live UI channels.LinuxIntermediate16 minProLINUX-1259A reverse proxy serves normal HTTP but WebSocket clients still failA proxy migration succeeds for normal requests while browsers or clients using WebSockets begin failing immediately.LinuxIntermediate16 minProNETWORK-1203Host DNS works but the proxy process keeps an old resolver view until it reloadsName resolution is fixed at the host level, yet one long-lived process still uses an older resolver state and continues sending traffic to the wrong backend.NetworkIntermediate17 minProK8S-111Gateway API reports the HTTPRoute as accepted but the listener hostname mismatch prevents any real attachmentStatus conditions look promising, yet traffic never arrives because the route was accepted by the controller but not bound to the intended hostname listener.KubernetesAdvanced18 minProNETWORK-1190WebSocket path fails only through reverse proxyA network team validates normal HTTP traffic and DNS, yet upgraded sessions still fail because one proxy hop never forwards the needed semantics.NetworkIntermediate18 minProNETWORK-1195Reverse proxy returns 499 and upstream timeout togetherA team reads public NGINX troubleshooting threads and focuses on 499 status codes. The real problem is a backend path slow enough that clients disconnect first.NetworkIntermediate19 minProK8S-1183Ingress NGINX returns 400 on WebSocket pathA public ingress-nginx snippet was copied into production. Browser requests work until the WebSocket path crosses an extra proxy boundary.KubernetesIntermediate24 minProLINUX-003Tracking the upstream application bottleneck in an Nginx 502 incidentA troubleshooting exercise that comprehensively considers the proxy, ports, application state, and timeout settings.LinuxAdvanced28 minProLINUX-1295A websocket reverse proxy works until reloadA proxy reload appears harmless and long-lived websocket sessions begin failing only on one path afterward.LinuxIntermediate14 minProK8S-363A gateway API route is admitted while one backend reference still points to a namespace alias only the old ingress controller understood during a staged decommissionThe route object looks valid and one controller-specific assumption no longer applies. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.KubernetesIntermediate16 minProK8S-124An ingress rewrite rule strips the trailing slash from the websocket path and only interactive sessions fail while health checks stay greenThe service looks healthy through normal probes, yet upgraded connections hit a subtly different path contract.KubernetesIntermediate16 minProK8S-479A gateway API route is admitted (404 and Rewrite Mismatch)A gateway API route is admitted (404 and Rewrite Mismatch) focuses on cluster-networking-and-service-discovery and asks the reader to isolate 404 and Rewrite Mismatch in NGINX. 실무에서는 404-and-rewrite-mismatch 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶...KubernetesIntermediate18 minProK8S-483A gateway API route is admitted (404 and Rewrite Mismatch)A gateway API route is admitted (404 and Rewrite Mismatch) focuses on cluster-networking-and-service-discovery and asks the reader to isolate 404 and Rewrite Mismatch in NGINX. 실무에서는 404-and-rewrite-mismatch 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶...KubernetesIntermediate18 minProK8S-484A gateway API route is admitted (404 and Rewrite Mismatch)A gateway API route is admitted (404 and Rewrite Mismatch) focuses on cluster-networking-and-service-discovery and asks the reader to isolate 404 and Rewrite Mismatch in NGINX. 실무에서는 404-and-rewrite-mismatch 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶...KubernetesIntermediate19 minProK8S-539A gateway API route is admitted (404 and Rewrite Mismatch)A gateway API route is admitted (404 and Rewrite Mismatch) focuses on cluster-networking-and-service-discovery and asks the reader to isolate 404 and Rewrite Mismatch in NGINX. 실무에서는 404-and-rewrite-mismatch 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶...KubernetesIntermediate19 minProSECURITY-1678An mTLS certificate chain validates and backend auth still failsAn mTLS path validates at the edge, yet backend authorization still fails on the same request chain.SecurityIntermediate11 minProK8S-1680A cert-manager Certificate is renamed and one HTTPS path still failsHTTPS still fails on one path after a certificate secret rename and reissue.KubernetesIntermediate12 minProSECURITY-1689An mTLS chain validates and backend auth still failsAn mTLS path validates at the edge, yet backend authorization still fails.SecurityIntermediate9 minProSECURITY-1699An mTLS chain validates and backend auth still failsAn mTLS path validates at the edge, yet backend authorization still fails.SecurityIntermediate9 minPro