Troubleshooting
Troubleshooting
Every message Kuppit shows when something goes wrong, what it means, and what to do about it.
When a deployment fails, a domain will not go active, or a pull request gets no preview, Kuppit says why in one sentence. These pages take each sentence and say what happened behind it, what to check, and how to fix it. The failure page in the dashboard links to the matching entry.
Reading a failed deployment
A failed deployment's page opens with the failure, above the phases:
- The title is Build failed when the image could not be built, and Deployment failed otherwise.
- One sentence names the cause. The same sentence heads its entry here.
- The sentence is followed by whose problem it is. Your application's failures offer View relevant logs, which opens the stream that failed with errors selected. Failures you fix on the Variables tab say Check this service's variables, then deploy again and offer Edit variables. Kuppit's own say This is Kuppit's to fix, not something in your repository.
- Advanced details holds the infrastructure's own error code and message, for when the sentence is not enough.
- Redeploy builds the same commit again with the service's current settings and variables.
Whatever failed, traffic was not moved. The deployment that was serving keeps serving.
Deployments
| It says | Go to |
|---|---|
| The Dockerfile Kuppit was told to build no longer exists · Build settings no longer match the repository · The repository is too large for Kuppit to build · The repository source could not be read · The build failed · The build ran out of time | Build failures |
| The new revision could not start · The application did not become healthy | Start and health failures |
| A variable references a database that no longer exists · … that is being deleted · … something the database does not expose · The referenced database is still being created | Reference failures |
| Kuppit encountered an internal build error · Kuppit lost track of the build · Traffic did not move to the new revision · The deployment stopped making progress · and the rest that are Kuppit's | Failures that are Kuppit's |
Domains and previews
- A custom domain stuck at Needs ownership, Needs routing, Securing, or showing DNS issue or Failed: Domain issues.
- A pull request whose check says No preview, or has no Kuppit Preview check at all: No preview for a pull request.
Was this page helpful?