Apache 404 cache or propagation drift response

When this happens

Use this when the panel says fixed but some users still see the old error. Do not stop at the screen message; validate browser cache, CDN cache, DNS TTL, panel propagation, and stale application cache first.

Symptom checklist

• 404 appears repeatedly in the Apache UI or logs.
• DocumentRoot, Directory permissions, AllowOverride, error_log differs between successful and failed requests.
• The issue appears only after separating Apache config errors from application errors.
• It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

• 404 specifically changes the investigation surface for Apache: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• The requested path reaches a server block, ingress, or router that does not own it.
• A rewrite or permalink rule captures the route before the intended handler.
• Static output, submodule content, or uploaded files were not deployed.
• The host header maps to a default virtual host instead of the target site.
• A cache serves an old 404 after the route has been added.
• For the cache or propagation drift case, the first useful clue is browser cache, CDN cache, DNS TTL, panel propagation, and stale application cache.

First 1-minute checks

1. Write down the first failure time, latest change, affected user, path, and object ID.
2. Compare DocumentRoot, Directory permissions, AllowOverride, error_log for success and failure in the same window.
3. Test the hypothesis: routing failure caused by missing route, wrong virtual host, rewrite rule, permalink cache, ingress rule, or missing deployed file.
4. Classify this as cache or propagation drift: browser cache, CDN cache, DNS TTL, panel propagation, and stale application cache.
5. Capture current values before changing configuration.

First evidence

Treat 404 as a cache or propagation drift case. First collect evidence for browser cache, CDN cache, DNS TTL, panel propagation, and stale application cache.

Output examples

Normal output

Fresh requests and DNS answers show the same intended value from multiple networks.

Failing output

Only one resolver, browser, CDN edge, or cached object still returns the old value.

Output-to-action branches

• The panel says fixed but some users still see the old error.
  Separate DNS, CDN, browser, and application cache, then purge only the stale layer.
• The working and failing outputs differ.
  Act on the differing layer first: For 404, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Command output is normal but users still fail.
  Separate browser cache, cookies, permissions, and network location before declaring it fixed.

Do not do this

• Do not repeatedly edit correct DNS records just because a stale resolver is still visible.
• Do not change multiple layers before identifying the failing layer.
• Do not delete production data, grant broad permissions, or disable security controls as a first response.

Evidence quality

Auto-generated operator draft: includes issue-specific causes, commands, output branches, and unsafe-action warnings. Official-source links and real incident validation are queued for enrichment.

Commands to run first

grep -R "404" ./logs

apachectl -S

apachectl configtest

grep -R "404" /var/log/apache2

find /var/www -maxdepth 2 -type d -ls

curl -I https://example.com/missing-path

grep -R "404\|not found\|rewrite\|permalink" ./logs

nginx -T | grep -n "server_name\|rewrite\|location"

curl -I https://example.com -H 'Cache-Control: no-cache' && dig +trace example.com

Fix order

1. Record the full 404 message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for routing failure caused by missing route, wrong virtual host, rewrite rule, permalink cache, ingress rule, or missing deployed file.
3. Compare the failing case with a successful case before editing settings.
4. If this is the cache or propagation drift branch, Separate DNS, CDN, browser, and application cache, then purge only the stale layer.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For 404, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Check host and path routing before changing application code.
• Print rewrite, ingress, or server configuration and verify rule order.
• Confirm the built artifact actually contains the expected file or route.
• Purge CDN and application route cache after fixing the origin route.
• Add a regression URL check for the exact failing path.
• For the cache or propagation drift branch, Separate DNS, CDN, browser, and application cache, then purge only the stale layer.

Evidence links

• Apache HTTP Server documentation official
• Apache mod_rewrite documentation official

Verification metadata

• operator-draft
• official-reference-linked
• 2026-07-23

Update queue

• Review cadence
  weekly-source-review
• Next enrichment
  Add one official-source check and one real output example for Apache 404.

Environment-specific checks

• Shared hosting, proxies, VPNs, or CDN layers can change Apache config errors from application errors results.
• Do not trust only the Apache UI; compare command output.
• Japanese hosting panels may show completion before DNS or SSL fully propagates.
• Test from both office and external networks.

Prevent it next time

• Store normal examples for DocumentRoot, Directory permissions, AllowOverride, error_log.
• Add vhost, Directory, mod_rewrite, and file permissions to the release checklist.
• Keep recurring errors in the same note format.
• Split alerts by error rate, latency, certificates, disk, and permission changes.

Related notes

• Apache 403 Forbidden DocumentRoot permission error
• Apache .htaccess fix note
• Apache failed fix note
• Apache .htaccess fix note 2
• Apache failed fix note 2
• Apache .htaccess fix note 3
• Apache failed fix note 3
• Apache .htaccess fix note 4