Troubleshooting deploys

First deploy failed

Confirm build and start commands match your stack.
Ensure the app listens on 0.0.0.0 and process.env.PORT.
Set a health check path your app serves (or add a /health route).
Point database URLs at managed Postgres/Key Value services — not localhost inside the container.

502 or service not live

The gateway returns 503 until a deploy succeeds and status is live. Open Events to inspect the failed deploy log.

TLS errors on default URLs

Default {serviceId}.breachfix.com hostnames require wildcard routing on your cluster. Operators should follow Cloudflare tunnel setup and run ./scripts/verify-public-routing.sh.

Build succeeds but app crashes

Check runtime logs for missing env vars, wrong start command, or port binding issues.