NGINX ingress error pages
Quave ONE may show a branded NGINX ingress error page when a request reaches a platform gateway but cannot be completed. These pages are platform-owned: they are separate from error pages returned by your application.
The currently configured branded responses are:
- 404 when the ingress has no matching host or route.
- 502, 503, and 504 when the gateway cannot complete a request to an upstream application.
Your application’s own 4xx responses and 500 responses are returned directly by your application. Quave ONE does not replace those responses with this branded ingress page.
In most cases, this is probably not a problem with the Quave ONE platform. It usually means the gateway could not route the request to your app as expected, or your app did not provide a healthy response in time.
If you are not sure what to do to fix it, please contact support@quave.one.
What to check first
- Confirm the host and path you opened are configured in the App Env Hosts section.
- Check that your app containers are running and ready.
- Review your app logs for startup failures, crashes, or request errors.
- Review metrics for CPU, memory, restarts, and response latency.
- Retry the request after applying fixes or after a temporary deploy or restart finishes.
Error codes
| Code | When Quave ONE shows this page | What to do |
|---|---|---|
| 404 | The ingress has no matching host or route. An application route that returns its own 404 does not use this page. | Confirm the hostname, path, App Env host configuration, and application routes. |
| 502 | The gateway could not get a valid response from the upstream service. | Check that the app is running, listening on the expected port, and passing readiness or health checks. |
| 503 | The upstream service is temporarily unavailable or has no ready endpoints. | Check deploy progress, container readiness, crashes, resource limits, and scaling state. |
| 504 | The upstream service took too long to respond. | Check slow requests, database or API dependencies, CPU or memory pressure, and app timeout settings. |
For these platform-owned responses, callers that request JSON (including API-like requests) can receive a small Quave ONE JSON error payload with the same HTTP status instead of HTML.
When to contact support
Please contact support@quave.one if the error persists after your app is healthy, the host and path are configured correctly, and you are not sure how to proceed from logs or metrics.
Include the HTTP code, URL, approximate time, and any recent deploy or configuration changes so support can investigate faster.