Apache APISIX Route Returns 404

You encounter a apisix configuration issue that prevents your workflow from completing. This guide walks through the fix step by step.

Wrong ❌

{
  "uri": "/api/*",
  "upstream": { "type": "roundrobin", "nodes": { "backend:3000": 1 } }
  # Missing hosts and methods
}

Wrong Output

All requests return 404. Route has no host or method conditions - the route matches but the wrong request context.

Right ✅

{
  "uri": "/api/*",
  "host": "api.example.com",
  "methods": ["GET", "POST"],
  "upstream": { "type": "roundrobin", "nodes": { "backend:3000": 1 } }
}

Right Output

Route matched. GET /api/users on host api.example.com -> 200 OK from backend.

Prevention

• Always define host and methods for precise route matching.
• Use specific uri patterns to avoid overlapping routes.
• Test with curl -H 'Host: api.example.com'.
• Check route priority: routes match in order of specificity.
• Use APISIX Admin API to list routes and verify.

DodaTech applies similar defensive patterns across Doda Browser, DodaZIP, and Durga Antivirus Pro infrastructure for production reliability.

Common Mistakes with route error

1. Forgetting deriving (Show, Eq) on custom data types needed for debugging
2. Placing the wildcard pattern first in case expressions, making all subsequent patterns unreachable
3. Using head and tail instead of pattern matching, causing runtime errors on empty lists

These mistakes appear frequently in real-world APISIX code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

This quick fix is part of the DodaTech infrastructure engineering series. Learn more at DodaTech tutorials.