Troubleshoot a failed Node.js deployment

Start with the correct deployment

Deployment logs describe fetching and building the code. Events from the running application appear separately on Logs. You need access to the website's details; deploying changes requires management permissions.

Investigate the error

1. Open the website and Deploys.
2. Find the failed row by its time and commit identifier. The Live label identifies the deployment currently serving the website.
3. Open the row to see its log. Find the first error before the generic failure message at the end of the build.
4. If fetching code fails, check the GitHub connection, repository and branch. If dependency installation fails, check package.json, the lockfile and package availability.
5. If the error identifies a missing variable, add it on Environment. For a code error, fix it in the repository and deploy the corrected commit.

Verify the fix

Confirm that the new deployment completes and the correct commit is live. Test the website in a browser too: a successful build alone does not establish that login or database access works.

If you need help

Include the service and website names, deployment time, commit identifier and a few log lines around the error in your support request. Remove API keys, tokens and personal data. If the log indicates exhausted memory or disk space, check Usage and plan before trying again.