Logs
Use deployment build output and service details to investigate a NexHost release.
Logs#
The deployment detail page is the primary place to inspect release output. It records the source-preparation, dependency, build, and release stages for a deployment.
Find the relevant release#
- Open Deployments in the dashboard.
- Filter or open the project’s deployment history.
- Select the release whose status needs investigation.
- Read the output from the first error upward; later messages often follow from the original failure.
What the stages mean#
| Stage | Typical problems |
|---|---|
| Source | Incorrect repository, archive, branch, or root directory. |
| Dependencies | Missing lockfile, unavailable package, or install-command failure. |
| Build | Compilation, framework configuration, or missing environment value. |
| Publish or startup | Missing static output, invalid start command, or an application that exits. |
| Health check | The application did not listen on PORT, the path is wrong, or it did not become ready in time. |
Share logs safely#
Before sharing output with another person, remove passwords, access tokens, connection strings, and private URLs. The dashboard output is useful for support when paired with the project name, deployment time, and failed stage.