Edge Delivery Services: Domain mapping fails due to incorrect origin after site verification
This article describes how to resolve domain mapping failures in Adobe Edge Delivery Services when the site origin is incorrectly updated with a challenge file path after site verification. It provides steps for both an engineering-led fix and a customer-actionable workaround.
Description description
Environment
Adobe Experience Manager as a Cloud Service (all versions using Edge Delivery Services)
Issue/Symptoms
- After completing site verification in the Edge Delivery Services site console, the site origin is incorrectly updated to append the path
/well-known/adobe/cloudmanager-challenge.txt. - The affected site origin appears as
<site-origin>/well-known/adobe/cloudmanager-challenge.txtinstead of<site-origin>. - Attempts to map a domain to the site fail, and onboarding cannot be completed.
- The Edge Delivery Sites dashboard shows the affected site with the incorrect origin and no mapped domain.
- API responses and dashboard entries confirm that the persisted origin includes the challenge file path.
Cause
A defect in the Edge Delivery Services site validation flow causes the origin to be incorrectly saved with the challenge file path after verification, blocking domain mapping and onboarding.
Resolution resolution
Follow the steps to resolve the issue:
-
Do not delete or modify the affected Edge Delivery Services site entry if you are waiting for an engineering-led fix. The site entry must remain unchanged so that it can be included in the corrective cleanup performed by Adobe Engineering.
-
Wait for confirmation from Adobe that the engineering-led cleanup is complete. This process updates the stored origin to remove the
/well-known/adobe/cloudmanager-challenge.txtpath. -
After receiving confirmation that the fix has been applied:
- Verify the corrected origin using the Sites API or the Edge Delivery Sites dashboard. The origin should no longer include the challenge file path.
- Proceed with domain mapping for the affected site.
-
If immediate onboarding is required and waiting for the engineering-led fix is not acceptable:
- Delete the affected Edge Delivery Services site entry.
- Re-create the site entry from scratch.
- Re-onboard and re-verify the site, then attempt domain mapping again.
-
After either resolution path, confirm that domain mapping completes successfully and the site is onboarded as expected.