Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLVED

EDS and universal editor integration in AEMaaCS - getting error "Couldn't connect to the page" when opening universal editor

Avatar

Community Advisor

Hi all, 

I followed this tutorial (EDS site via EDS template using Universal Editor in AEMaaCS - no doc authoring): https://www.aem.live/developer/ue-tutorial?lang=en#create-github-project  and followed each step exactly as mentioned but I am getting the below error page when opening the index page in universal editor:

kapil_rajoria_0-1755501123206.png


I also tried adding these in head tag but all in vain: (https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/dev... )

<meta name="urn:adobe:aue:system:aemconnection" content="aem:https://author-x-y.adobeaemcloud.com">
<meta name="urn:adobe:aue:system:fcsconn" content="fcs:https://author-x-y.adobeaemcloud.com"> 
<meta name="urn:adobe:aue:system:fcsconnection" content="fcs:https://example.franklin.adobe.com/345fcdd">
<script src="https://universal-editor-service.adobe.io/cors.js" async></script>

 
I can't find any other resources regarding the integration. Can anyone help regarding this?
 
@daniel-strmecki @Shiv_Prakash_Patel @Martin_Buergi_Adobe @RaphaelWe 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Employee

First thing you should try is to update to the latest AEM CS release. It will show you a meaningful error message to help you investigate the issue instead of the blank page. A few possible issues are:

 

(1) The repository you are using was not synced with Edge Delivery Services (AEM Code Sync app not installed), or the code sync was incomplete. There are 4 files that are essential for AEMCS to render any page for editing in Universal Editor, which are head.html, component-models.json, component-defintion.json and component-filters.json. All of them must be available on your Edge Delivery site.

 

(2) Your AEMCS instance is generally outdated: in the past AEM used .hlx.page to retrieve these files, which has been deprecated and new sites are not even provisioned for it anymore since a longer time already. It may be that your AEMCS version is too and does use .aem.page.

View solution in original post

2 Replies

Avatar

Correct answer by
Employee

First thing you should try is to update to the latest AEM CS release. It will show you a meaningful error message to help you investigate the issue instead of the blank page. A few possible issues are:

 

(1) The repository you are using was not synced with Edge Delivery Services (AEM Code Sync app not installed), or the code sync was incomplete. There are 4 files that are essential for AEMCS to render any page for editing in Universal Editor, which are head.html, component-models.json, component-defintion.json and component-filters.json. All of them must be available on your Edge Delivery site.

 

(2) Your AEMCS instance is generally outdated: in the past AEM used .hlx.page to retrieve these files, which has been deprecated and new sites are not even provisioned for it anymore since a longer time already. It may be that your AEMCS version is too and does use .aem.page.

Avatar

Community Advisor

Thanks, worked fine after I updated my AEM CS.