Docs · Troubleshooting
Fix it by symptom.
Most Runex deploy problems fall into three groups: the build fails, the app starts but isn't reachable, or a custom domain doesn't resolve. Find your symptom below and follow its checklist.
- build failed
- → deployment failed
- crashes on start
- → deployment failed
- url times out
- → port configuration
- domain won't load
- → custom domain
- https pending
- → custom domain
Symptoms
What's going wrong?
Pick the closest match.
First checks
What should you check first, whatever the problem?
Logs, then variables, then the platform URL. Build and runtime output lives in logs and monitoring.
- Read the build and runtime logs for the failing deploy in the dashboard
- Confirm every environment variable the app needs is set
- Test the *.runex.cloud URL before debugging a custom domain
- Check the GitHub App still has access to the repository
FAQ
Troubleshooting questions
Before you open a ticket.
Where do I see why a Runex deploy failed?
Open the deploy in the dashboard. The build log shows install and compile errors; the runtime log shows crashes after the app starts.
Does a failed deploy take my app offline?
No. Traffic stays on the last healthy version until a new deploy passes its health check.
How do I roll back while I debug?
Pick an earlier successful deploy in the dashboard and roll back. It goes live without a rebuild.
Next step
Fixed? Ship it.
Push the fix and Runex redeploys automatically.