A build failed

Read the deployment logs and find the first error. Check the selected branch, build method, dependency files, build command, and required environment variables. Try the same build locally before redeploying.

The build passed, but the app does not respond

Check the application's start command and listening port. A process that starts and exits immediately will not serve requests. Review runtime logs and confirm the domain routes to the port your app actually uses.

A database connection fails

Confirm that the database is running. Check the host, port, database name, and credentials against the database detail page. Use an address reachable from where the client runs. After changing application variables, save them and deploy again.

A domain or certificate does not work

Confirm that DNS points to the destination provided for your application. Check that HTTPS and the intended certificate option are selected. A dashboard entry alone does not verify DNS propagation or certificate issuance.

A repository is missing

Check the GitHub account and installation connected to your organization. Confirm that the installation has access to the repository, then return to the application settings and select it.

You cannot create a service

Check the selected organization, your permissions, your subscription, and the remaining site or database allowance. Ask your organization owner to review access if needed.

Ask for help

Contact support with:

• The project and service name.
• The action that failed and approximately when it happened.
• The first relevant error message and steps to reproduce it.
• What you already checked.

Remove passwords, tokens, and connection credentials from logs or screenshots before sharing them.