Troubleshooting · By Rivtor · Updated
Fix application port and health-check failures
A running application process can still fail routing. It must listen on the configured port and an interface reachable by the router, and respond correctly at the chosen health path.
See the Rivtor deployment workflow →
Check the listener
A loopback-only listener inside a container is not reachable through the usual container network path. Use the framework’s production server and set its address deliberately. Ensure the deployment port agrees with the application port; a development server that silently selects another free port can hide the mismatch locally.
Keep health responses predictable
Use a small response that does not require browser login or redirect to another page. Distinguish basic process liveness from a broader readiness or database check. Startup migrations and long initialization should be explicit rather than hidden behind an always-successful endpoint.
Read the first startup error
Look for missing imports, permissions problems, address conflicts and absent configuration. Repeated router connection failures can be secondary symptoms of an application that exited. Fix the underlying failure before increasing health-check timeouts.
Verify the normal user route
Check both the health endpoint and a representative application operation. Inspect redirect destinations, HTTPS handling and any route prefix. A healthy backend at one address is still unavailable to a frontend configured to call a different hostname.
Command reference
curl -i https://example.com/health
These commands illustrate the documented workflow. Replace example addresses and identifiers with your own. Deployment and migration commands affect the selected project; confirm the target before running them.
Trace the path to the listener
A useful diagnostic sequence is: application process, bind address, listening port, service routing and public URL. A successful startup log only covers the first step. A listener bound to 127.0.0.1 may be unreachable from another container.
curl -i http://127.0.0.1:8000/health
curl -i https://api.example.com/health
The first command targets a local example process; the second targets a public example URL. Replace both with your configuration. Compare status codes and response bodies rather than interpreting every response as proof that the intended application handled it.
Design the health endpoint for its purpose
Use a small, predictable response with a meaningful status code. A liveness check can establish that the process responds; a readiness check may also need essential dependencies. Balance dependency checks against their load and failure behavior.
A redirect from a trailing-slash mismatch may behave differently from a direct successful response. Test the exact configured health path. A slow migration or import failure belongs in startup investigation rather than a longer timeout applied without diagnosis.
Confirm normal application behavior
After reachability succeeds, load a real public page and run a synthetic API/data operation. Check verification coverage and keep skipped checks distinct from successes. For runtime preparation, use the Express guide or FastAPI guide.
Source: FastAPI server concepts.
Next steps
Read the Rivtor reference for supported configuration and limitations, and use the deployment quickstart when trying Rivtor for the first time. Validate workflows with synthetic data before connecting valuable production records.