AEM cloud dispatcher vhost mapping with domain | Community
Skip to main content
bsr060893
bsr060893
Level 3
June 25, 2026
Question

AEM cloud dispatcher vhost mapping with domain

  • June 25, 2026
  • 3 replies
  • 90 views

Hi,

We are trying to set new domain in cloud 

Followed the documentation and domain shows verified.

In domain mapping section status is shown as deployed 

If I try access the domain with home page I am able to view it. The vhost header is resolved to publish. 

 

I tried adding custom vhost for newly added domain and a farm file.

 

My vhost is not picking up and x-vhost is always publish not the custom one.

 

After checking found that domain mapping section has go live button to make domain available for traffic as mentioned in the docs.

 

So my host file not resolved willbe causing because of domain not yet go live?

 

But when the status is deployed how I can access the domain.

 

Could someone help with the insights 

 

 

3 replies

A
akhil_merupula
Level 4
June 27, 2026

Hi ​@bsr060893,

 

The “deployed” status in Cloud Manager means the domain mapping is configured, but your custom vhost still needs to explicitly match that domain for the dispatcher to pick it up.

 

The x-vhost: publish tells you the dispatcher is falling back to the default vhost, which means your custom vhost’s ServerName (or ServerAlias) doesn’t match the incoming host header. Double-check that your vhost file has the exact domain name configured:

 

<VirtualHost *:80>
    ServerName yournewdomain.com
    ...
</VirtualHost>

 

Also confirm the vhost file is included in your dispatcher config’s available_vhosts and symlinked in enabled_vhosts, in AEM Cloud the dispatcher SDK is strict about this.

 

The “Go Live” button controls CDN routing, not dispatcher vhost resolution. Your vhost should work independently of that once the config is deployed correctly.

bsr060893
bsr060893Author
Level 3
June 27, 2026

Hi ​@akhil_merupula ,

 

Thank you for the inputs.

I have double checked my farm and vhost files. The domain i have is prod-aem.example.com.

 

In this case subdomain prod-aem, domain is example.com

I have vhost for full domain as in prod-aem.example.com and symlink is correct. I have ran full validator in local and have no errors.

I have included this domain in my farm file under/virtualhosts.

As per logs i can see my farm is picking up as i see logs in dispatcher.

 

Could suggest if subdomain is causing the issue? 

A
akhil_merupula
Level 4
June 27, 2026

The subdomain itself isn’t the issue, prod-aem.example.com is a valid ServerName and should resolve fine.

 

Since the farm is picking up but x-vhost still shows publish, the likely culprit is the CDN layer. In AEM Cloud Service, the CDN sits in front of the dispatcher and resolves the domain mapping before the request reaches your vhost. If the domain isn’t “Go Live” yet in Cloud Manager, the CDN won’t route traffic to your environment correctly, it’ll fall back to the default publish routing regardless of your vhost config.

 

So yes, click “Go Live” in the domain mapping section and then retest. The vhost config looks fine based on what you’ve described; the CDN routing is the missing piece.

    lavishvasuja
    lavishvasuja
    Level 4
    June 28, 2026

    ​@bsr060893 -

    I wouldn't expect the subdomain itself to be the issue. If the ServerName/ServerAlias, /virtualhosts  mapping, and dispatcher validation all look correct, the dispatcher configuration appears to be in order.

    One thing I'd verify is whether the domain has been marked Go Live in Cloud Manager. My understanding is that Deployed indicates the domain configuration has been provisioned, whereas Go Live makes the domain available for live traffic. If it hasn't been marked Go Live yet, it would be worth checking whether that changes the behavior, as it may help determine whether the issue is related to domain routing rather than the dispatcher configuration itself.

    If the issue persists after the domain is Go Live, I'd then review the vhost matching order, ServerAlias  values, /virtualhosts entries, and the generated dispatcher configuration to confirm the expected vhost is being selected.

    bsr060893
    bsr060893Author
    Level 3
    June 29, 2026

    Hi ​@akhil_merupula , ​@lavishvasuja 

     

    I have tried checking on Go Live option in domain mappings.

    It has 2 step proecess and in 2nd step mentioned to do CNAME config.

    Currently for my dev we have a CNAME pointed for to our publish env (publish-xxx.adobeaemcloud.com)

    Do i need to change it to cdn.adobecloud.com as mentioned in docs? So all my stage, dev and other envs will have same CNAME or docs are being generic and need to point to our respective publisg tiers?

    Terms & ConditionsAccessibility statement

    Loading footer...