NGINX
274 incident problems in NGINX environments.
먼저 읽을 가이드
추천 문제
All problems (274)
K8S-1603A Gateway listener change is correct and one pod still routes oldOne gateway pod still routes old after a listener change.KubernetesAdvanced10 minProCICD-1587A Helm provenance job validates at origin and fails at one proxyOne proxy path fails Helm provenance checks after republishing the chart.CI/CDAdvanced10 minProNETWORK-1561An NGINX ingress keeps the new upstream and one site still reports the old client IPOne site logs the wrong client IP after ingress and real_ip cleanup.NetworkAdvanced10 minProNETWORK-1571An NGINX map update is correct and one hostname still routes oldOne hostname still routes to the old upstream after a map update.NetworkAdvanced10 minProNETWORK-1581An NGINX upstream keepalive fix lands and one site still speaks to the old backendOne site still talks to the old backend after an NGINX keepalive fix.NetworkAdvanced10 minProSECURITY-1495A CrowdSec bouncer loads the new decision list and one reverse proxy still blocks healthy clientsHealthy clients remain blocked after CrowdSec decisions are cleaned up behind a reverse proxy chain refactor.SecurityAdvanced11 minProSECURITY-1505A CrowdSec decision list updates and healthy clients still blockHealthy clients remain blocked after decision cleanup behind a reverse proxy chain refactor.SecurityAdvanced11 minProSECURITY-1515A CrowdSec decision list updates and healthy clients still blockHealthy clients remain blocked after decision cleanup behind a reverse proxy chain refactor.SecurityAdvanced11 minProK8S-1509A Gateway API canary route attaches and all traffic still lands on stableCanary weights never take effect on one controller revision after a Gateway API migration.KubernetesAdvanced11 minProK8S-1499A Gateway API canary route looks correct and 100 percent of traffic still lands on stableCanary weight changes never take effect after moving from Ingress to Gateway API on one controller revision.KubernetesAdvanced11 minProK8S-1553A Gateway API listener changes and one edge pod still serves the old routeA route change fails on one edge pod while the rest of the gateway fleet is correct.KubernetesAdvanced11 minProK8S-1523A Gateway API route attaches and one worker still serves the old backendA backend switch never takes effect on one gateway worker after a route change.KubernetesAdvanced11 minProK8S-1513A Gateway API route attaches and still serves the old backendA backend switch never takes effect on one gateway worker after a Gateway API change.KubernetesAdvanced11 minProSECURITY-1382A Grafana auth proxy setup works and admin privileges disappearA Grafana auth proxy setup works and admin privileges disappear focuses on Identity And Access and asks the reader to isolate the key signal in NGINX. Identity regressions can come from harmless-looking canonicalization changes like lowercasing...SecurityIntermediate11 minProK8S-1573A ReferenceGrant is applied and one cross-namespace route still failsOne cross-namespace route fails after ReferenceGrant rollout.KubernetesAdvanced11 minProCICD-1534A registry mirror serves the new image and signature verification still failsSignature verification fails only through one mirror tier after edge caching is enabled.CI/CDAdvanced11 minProK8S-1563A TLSRoute attaches cleanly and one gateway pod still serves the old backendOne gateway pod serves the old backend after a TLSRoute change.KubernetesAdvanced11 minProCICD-1524An image mirror serves pulls and signature verification still failsVerification fails only when images are pulled through one registry mirror tier.CI/CDAdvanced11 minProK8S-1490An ingress-nginx admission patch succeeds and websocket upgrades still failWebSocket upgrades fail only for canary users after ingress annotations were centralized.KubernetesAdvanced11 minProNETWORK-1551An NGINX gateway reloads and one location still uses the old upstreamOne route keeps hitting the old upstream after a gateway reload.NetworkAdvanced11 minPro