Subdomain fails to verify due to dispatcher redirect
When configuring domain mapping in Adobe Experience Manager as a Cloud Service, a subdomain fails to verify in Cloud Manager even though the apex domain verifies successfully and both use the same certificate. This issue occurs because the dispatcher configuration for the subdomain redirects all requests and prevents Cloud Manager from receiving the required 2xx response during verification. Temporarily adjusting the dispatcher configuration allows verification to succeed.
Description description
Environment
- Adobe Experience Manager as a Cloud Service – Sites
- Cloud Manager
- Dispatcher
Issue/Symptoms
- A subdomain (for example, www.example.com) appears as Deployed but does not go live or verify in Cloud Manager.
- The apex domain (example.com) verifies without issue.
- Requests to specific paths (such as
/depot/) on both domains return 200 responses. - Requests to the root path (/) on the subdomain result in a redirect or do not return a 2xx response.
Resolution resolution
To resolve this issue, follow these steps:
- Review the dispatcher vhost configuration for the affected subdomain.
- Identify if there is a rule that redirects all requests from the subdomain to another hostname such as an apex domain, preventing any 2xx responses from being returned.
- Temporarily modify the vhost configuration so that requests to the subdomain serve content directly or otherwise return a 2xx response.
- Initiate or retry domain verification for the affected subdomain in Cloud Manager.
- After successful verification, restore the original redirect logic if desired.
- Verify that both domains are now live and functioning as expected.
Notes: Cloud Manager requires at least one successful 2xx response from each mapped hostname during verification. Unconditional redirects prevent this and cause verification to fail. Verification occurs once per mapping event. You can restore redirects after completion.