Documentation

Error 500‑001 when accessing author in AEM as a Cloud Service

Last update: Fri May 15 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

In AEMaaCS, accessing an author environment display the Error 500‑001: Failed to load page message on the author hostname. In confirmed cases, this behavior was related to Unified Shell traffic for the specific author hostname not being routed correctly at the edge/CDN layer. Issues within AEM or custom application code were not identified as contributing factors in those cases. Correcting CDN routing for Unified Shell traffic addressed the issue in confirmed cases. If Unified Shell was turned off while troubleshooting, re-enable it using the public AEM as a Cloud Service guidance. To fix this, validate Unified Shell routing, reconcile the CDN configuration, and confirm Unified Shell functionality for the affected author environment.

Description description

Environment

  • Product: Adobe Experience Manager as a Cloud Service – Sites
  • Environment: Any AEM as a Cloud Service author environment (production, staging, development, RDE)

Issue/Symptoms

  • Accessing the author hostname through the standard public hostname returns Error 500‑001: Failed to load page.

  • Unified Shell endpoints on the author host fail while standard AEM requests succeed:

    • Requests such as POST /bin/unifiedshell/discovery?configid=ims return HTTP 503.
    • Requests such as POST /bin/unifiedshell/config return HTTP 503.

  • Other endpoints, such as /aem/start.html, reach AEM successfully. An HTTP 401 response when the user is not authenticated is expected for this check and confirms that routing to the AEM author is functioning correctly.

  • The issue affects only the specific author hostname and Unified Shell calls for that environment.

  • Other AEM as a Cloud Service environments for the same tenant are not impacted.

Resolution resolution

To fix this issue, follow these steps:

  1. Provide the required details when opening a support ticket
    When contacting Adobe Support, include the following information:

    • The full author hostname (or full author URL you use in the browser) where Error 500‑001: Failed to load page appears.
    • Confirmation that standard author endpoints, such as /aem/start.html, are reachable.
    • Confirmation that only Unified Shell endpoints are failing.
    • Details showing that Unified Shell calls, including POST /bin/unifiedshell/discovery?configid=ims and POST /bin/unifiedshell/config, return HTTP 503 from an intermediate layer such as the CDN.

  2. Request CDN and Unified Shell validation
    Ask Adobe Support to reconcile the CDN configuration for the affected author hostname and verify that Unified Shell endpoints are routed correctly to the AEM author environment.

  3. Verify author access after CDN reconciliation
    After Support confirms the CDN configuration update:

    • Load /aem/start.html on the public author hostname and sign in.
    • Confirm that Error 500‑001: Failed to load page no longer appears.

  4. Unified Shell configuration (only if changed during troubleshooting)
    In AEM, check the Unified Shell configuration for the environment. If Unified Shell was disabled during troubleshooting, re‑enable it following the public AEM as a Cloud Service Unified Shell guidance. If Unified Shell was not disabled, no action is required for this step.

  5. Validate the author UI entry point
    Access the /ui entry point on the author hostname and confirm that the environment loads without Error 500‑001 and that the Experience Cloud Unified Shell header appears.

  6. Confirm resolution
    If the error no longer appears and Unified Shell loads correctly, no further action is required.

If the issue persists

If Error 500‑001 continues after CDN reconciliation and Unified Shell is enabled as expected, collect the following details and share them with Adobe Support:

  • Capture a browser network trace using the browser developer tools Network tab.
  • Record the exact error message, HTTP status codes for /bin/unifiedshell/discovery and /bin/unifiedshell/config, the time window, and the author hostname (or full URL) used.
  • Attach or share these artifacts in the support ticket to allow further analysis of Unified Shell and CDN behavior.

Notes:

  • In confirmed cases, behavior aligned with Unified Shell traffic routing at the edge/CDN layer for the affected author hostname.
  • AEM platform issues, custom application code, and user permissions were not identified as contributing factors in confirmed cases.
  • Changes to user permissions or product profiles were not required to resolve confirmed cases.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f