502 Bad Gateway errors occur during deployment in Adobe Experience Manager as a Cloud Service
In Adobe Experience Manager (AEM), public facing sites display 502 Bad Gateway errors when dispatcher instances become detached from the Application Gateway during or after a deployment. This issue affects site availability and prevents requests from reaching AEM publish instances. To fix this issue, verify dispatcher associations and reattach any detached dispatcher instances to the Application Gateway.
Description description
Environment
Adobe Experience Manager (AEM) deployments using dispatcher instances connected to an Application Gateway.
Issue/Symptoms
- Public facing AEM sites display a 502 Bad Gateway error on the homepage or other pages.
- Some sites show a broken homepage instead of the expected content.
- The issue occurs during or shortly after a Cloud Manager deployment.
- Business operations are impacted because of site outages.
Cause
During the final stage of a Cloud Manager deployment, dispatcher instances become detached from the Application Gateway. This detachment prevents requests from reaching the AEM publish instances, resulting in 502 Bad Gateway errors.
Resolution resolution
Follow the steps below to resolve the issue:
- Review the deployment status in Cloud Manager to determine whether a deployment is currently in progress or recently completed.
- Check the status of all dispatcher instances and verify their association with the Application Gateway.
- Confirm that the AEM and Dispatcher deployment steps completed successfully and wait for Cloud Manager to complete the managed load-balancer transition.
- After reattaching the dispatcher instances, validate that all affected sites are accessible and confirm that the 502 Bad Gateway errors are resolved.
- Communicate with relevant stakeholders to confirm service restoration.