Deploy Error: Health Checks Component Issues app failed to deploy

I’m unable to see logs, it is stuck on loading for past 30 mins, I’ve tried restarting browser but I have no idea why my app deployment failed.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev
Site Moderator
Site Moderator badge
February 9, 2024

Hi there,

What I could suggest is following the steps from the documentation here:

As an app is deployed, App Platform verifies that its components are healthy by checking their availability on the app’s TCP port (the default port is 8080). If the app is not available on that port, then the health check fails and the app rolls back to the last healthy deployment.

There are two common issues that cause an app to fail a health check:

  • The app starts on a different port than App Platform expects, such as starting on port 3000 when App Platform expects that app to be available on port 8080. You can change the port App Platform uses to perform health checks by editing the http_port field in your app’s spec file and uploading the new app spec.

To edit your app’s spec, navigate to your app’s Overview page and then click the Settings tab. Scroll down to the App Spec section and the click Edit. A preview of the spec opens. Click the Download link at the bottom of the preview window. The spec downloads to your local machine.

Open the spec in a text editor and edit the http_port field to port 8080. Once you have edited the file, save it can close it.

Back in your app’s Settings, click Upload File in the App Spec section. Your machine’s local file manager opens. Select the updated spec file and click Open. The spec uploads to App Platform and triggers a new build.

  • The app’s HTTP server is configured to listen for HTTP requests on address localhost or This is common on NodeJS apps. These addresses use a loopback network interface that is only accessible from within the app’s container and are not accessible to external network traffic.

If your app is configured to listen on a different HTTP endpoint than the app’s root endpoint, you can configure the health checks feature to check your defined endpoint.

To change your app’s health check endpoint, navigate to your app’s Overview page and then click the Settings tab. Select the component that requires the health check and then scroll down to the Health Checks section. Click Edit.

In the Health Check section, click HTTP and then enter the endpoint you want to monitor into the HTTP Path field. Click Save. This automatically trigger a new build.

Hope that this helps!



Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel