When deploying an application, if there is an issue with deployment, you may see one of the following errors:

Something went wrong, please contact support.

Build process failed
Unknown build fail type

If the rollout process fails immediately, or if the build process fails, no pods are created, and runtime logs do not exist. An incorrect start command or ENTRYPOINT on the web process is most often the cause.

If the rollout process runs for a minute or two and then fails, this usually means the pods were created, but something went wrong, and the process stopped. In this case, you should check the application runtime logs to identify any error messages. The error messages can help you to identify bugs in the application’s code so you can debug the issue.

If you cannot identify the issue, check the following, and if the issue persists, contact our Support team.

GitHub Repository

Check your repository to ensure all the correct files have been pushed into the repository for your application.


If you choose Set up container image automatically when you add your application, we use a buildpack to automatically determine and set up a container for your application. When using buildpacks, you must ensure the correct language version is in your application’s files. For more details, see our documentation on specifying a language version.

Start Command or ENTRYPOINT

The Start Command or ENTRYPOINT for the web process starts your application. If this is incorrect, the application will not run. You can check the command in a couple of places in MyKinsta. Processes > Runtime processes > Web process or Deployments > History, select a deployment to view the details and Rollout process in the details.

Successful rollout process in Deployment details.
Successful rollout process in Deployment details.
Failed rollout process in Deployment details.
Failed rollout process in Deployment details.

If your application uses a Dockerfile to set up your container image, you must specify the ENTRYPOINT in the Dockerfile to run a container. For more information about how to specify your application’s ENTRYPOINT, see the Dockerfile reference.

For more details about what command to use based on your application’s language, see the examples provided in our Application Start Command documentation.

Environment Variables

Environment variables feed your application information from outside of the running of that application. An incorrect environment variable may prevent your application from running. You can check your environment variables in Settings > Environment variables.

Environment variables for your application.
Environment variables for your application.

Confirm that the correct environment variables exist and contain valid values. There are a couple of important things to keep in mind when creating and checking environment variables:

  • Commas are interpreted as delimiters by the rollout process, so they cannot be used in environment variables.
  • Each key must be unique, and a key can only be added once.


For Application Hosting, only ports 80 and 443 are open. If your application exposes any ports, you must use 8080.

Related Documentation