Read logs and investigate startup errors

Open Logs on the app page. If the app includes multiple services, use the available service selector to inspect the component reporting the problem.

Logs view for diagnosing an app. Example data; available controls vary by app and connection.

Logs view for diagnosing an app. Example data; available controls vary by app and connection.

Find the first useful error

1. Note when the problem started and any recent update or configuration change.
2. Read the startup messages around that time.
3. Look for a specific failure: invalid configuration, denied permission, database connection failure, lack of space or memory.
4. Compare the message with the app’s setup notes before changing anything.

The final message can be a consequence rather than the cause. A repeated restart message may follow an earlier configuration error.

Check related information

Use Metrics and Resources to check limits and usage. If the website is unreachable but the app appears healthy, check DNS, access rules and connection type.

Logs are diagnostic output, not instructions to execute commands blindly. Redact credentials, tokens, private URLs and personal information before sharing a relevant excerpt in a support ticket.

If there are no logs, include that fact and the deployment status in your ticket. Avoid deleting the app simply to clear an error; deletion can remove the evidence and data.