DocsShip apps
When a deploy fails
OpsNexa Online explains failed deploys in plain words, with the steps to fix them and a button to the right place.
A failed deployment says what went wrong in plain words, right above its log and on the app’s overview. These explanations are built in and need nothing set up. They cover the common causes:
| What you’ll read | What it means |
|---|---|
| The branch doesn’t exist | The app’s branch was renamed or deleted. Change it under Settings. |
| The repository is private | OpsNexa Online can’t read it. Connect a git account or the GitHub App. |
| A package or build script is missing | The build command expects something the repository doesn’t have. |
| The code has a TypeScript or syntax error | The build stopped on an error in the code, with the file and line. |
| The app listens on the wrong port, or only on localhost | Set the port under Settings → Advanced, or make the app listen on 0.0.0.0. |
| It ran out of memory | Give it more under Settings → Size, or reduce what the build uses. |
| A setting or the database is missing | Add the setting under Settings, or a database on the Database tab. |
Each explanation comes with the steps to fix it and a button that takes you to the right place.
Ask for a deeper look
When your company has AI features on, developers also get Ask Claude for a deeper look: the end of the build log is sent to Claude, with the values of secret settings replaced by [hidden], and the answer is kept with the deployment.
Get told
Failed deploys can notify a Slack or Discord channel, email or a webhook, with the explanation included. You can also have OpsNexa Online email you when a deploy you started fails. See Monitors and notifications.
Something unclear or missing? Tell us, or press the ? at the top of OpsNexa Online for the guide and tours inside the product.