Frontend pipeline deployment breaks the website

This article describes a solution to the issue where frontend pipelines are not successfully applied to websites, even when deployment finishes successfully. Add ServerAlias to an enabled vhost to fix it.

Description description


AEM as a Cloud Service


Frontend pipelines are not successfully applied to websites. Although the deployment finishes successfully, the JS/CSS files are not applied to the website.

Steps to reproduce

  1. Create a new site using the aem-site-template-standard version 2.2.0.
  2. Download sources from that site.
  3. Make some changes to the website theme.
  4. Push the sources into the repo/branch.
  5. Run the FE pipeline from that repo/branch.

After the FE pipeline is deployed, the new site breaks, and no JS/CSS is loaded.

In addition, you will see that at:

"/conf/fe-pipeline-test/sling:configs/com.adobe.cq.wcm.core.components.config.HtmlPageItemsConfig/jcr:content", the property "prefixPath" is set to:

"", which looks good.

But whatever resource you try to load from this server (like the CSS:, you always get It works.

Resolution resolution

When styling loads from the static domain and only returns It works, you need to verify whether the static domain is blocked at the Dispatcher level.

For FE pipelines to work, the deployed frontend artifacts need to be served correctly by the CDN/Dispatcher.

If the Dispatcher configuration blocks the static domain, the CSS/JS cannot be loaded.

For this, at least one of the enabled vhosts has either:

ServerAlias *
ServerAlias "static-p<progId>-e<envId>"

On checking the Dispatcher configuration, if you see that only the deault.vhost has ServerAlias "*". However, the default.vhost is not enabled.

Adding ServerAlias to an enabled vhost fixes the issue.

Ask Questions In Our Experience League Campaign Community

If you have any questions you’d like answered about this topic, or read previous answered-questions, we invite you to view our Experience League Community blog post that includes this article, send us your questions and comments, and join our Experience League Campaign Community!