On this page
Check the deployment first
Open the failed deployment and identify the first useful error. A build can fail before an application container starts. Private repository or registry access, dependency downloads, and resource limits can also stop a deployment.
For 502 or 503
Confirm the app is running, listening on the expected interface and internal port, and passing its health check. Compare the configured domain with the hostname used by the visitor. Review proxy logs after DNS and the application's local status are understood.
Test one change
Save the previous configuration, take a backup, and change one setting at a time. Repeated deployments can consume resources without fixing a wrong port or health path. Application-image rollback does not reverse database migrations or recover persistent data.
Escalate with evidence
Provide the deployment timestamp, redacted error, domain, and relevant service reference. Do not share repository tokens or environment secrets.