HTTP 404 for DevOps: Root-Cause, Routing, and Prevention Across Edge, Ingress, and App Layers

HTTP 404 errors look straightforward to end users, but in real-world platforms they can originate from several layers: edge, ingress, reverse proxy, or application routing. This guide is for DevOps engineers who need a fast, repeatable way to isolate the source, fix it safely, and reduce recurring not-found incidents.

Originally published on 2014-07-21; fully revised and updated.

What an HTTP 404 means operationally

A 404 Not Found response means the server handling the request could not find a resource at the requested path. In distributed deployments, this does not immediately prove the application is broken; it may indicate routing, rewrite, cache, or host-header mismatches before traffic even reaches the app.

Where 404s commonly originate

404 triage workflow

Use a top-down flow: reproduce the error, determine which layer generated it, then patch the specific route or resource. This avoids chasing application bugs when the issue is at the edge.

flowchart TD
    A[User reports missing page] --> B[Reproduce with curl and host header]
    B --> C{Response is 404?}
    C -- no --> D[Investigate non 404 issue]
    C -- yes --> E[Check CDN or load balancer logs]
    E --> F{404 at edge?}
    F -- yes --> G[Fix edge route or cache rule]
    F -- no --> H[Check ingress or reverse proxy routes]
    H --> I{Route match exists?}
    I -- no --> J[Fix path mapping or rewrite]
    I -- yes --> K[Check app routes and resource data]
    K --> L[Deploy fix and add alert]

Step-by-step checks with commands

Reproduce from the client side and with explicit host header

curl -i https://example.com/docs/install
curl -i -H "Host: example.com" http://INGRESS_IP/docs/installCode language: JavaScript (javascript)

The second request helps confirm whether DNS/CDN behavior differs from direct ingress behavior.

Validate Kubernetes ingress and service wiring

kubectl get ingress -A
kubectl describe ingress my-app -n prod
kubectl get svc -n prod
kubectl get endpoints my-service -n prodCode language: JavaScript (javascript)

Look for host/path rules that do not match the failing URL, and ensure the target service has healthy endpoints.

Confirm reverse-proxy route behavior

server {
    listen 80;
    server_name example.com;

    location / {
        try_files $uri $uri/ =404;
    }

    error_page 404 /404.html;
    location = /404.html {
        internal;
    }
}Code language: PHP (php)

Choose the right response code

Monitor 404 trends before users escalate

Track top missing paths and sudden spikes. Even simple log analysis can reveal broken links, bad rewrites, and deployment regressions quickly.

awk '$9 == 404 {print $7}' /var/log/nginx/access.log | sort | uniq -c | sort -nr | head -20Code language: JavaScript (javascript)

Best practices

• Test critical URLs in CI/CD after each deployment.
• Validate host and path routing at every layer (edge, ingress, proxy, app).
• Use consistent rewrite rules across environments to avoid drift.
• Create alerts on abnormal 404 rate changes, not only absolute counts.
• Serve a helpful custom 404 page, but keep the HTTP status code accurate.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.