AEM Local Publisher gives blank screen , Once logged in , Pages are working fine | Community
Skip to main content
P
PoovithaSelvaraj
Level 3
March 27, 2025
Solved

AEM Local Publisher gives blank screen , Once logged in , Pages are working fine

  • March 27, 2025
  • 2 replies
  • 839 views

Hi , 

 

I am facing small issue in my local publisher where once I start / restart instance ,my page is coming blank  with following error ,

 

27.03.2025 15:43:25.688 *INFO* [[0:0:0:0:0:0:0:1] [1743070405657] GET /content/mchp/en-us.html HTTP/1.1] com.day.cq.wcm.foundation.TemplatedContainer page has no template assigned 27.03.2025 15:43:25.688 *WARN* [[0:0:0:0:0:0:0:1] [1743070405657] GET /content/mchp/en-us.html HTTP/1.1] com.day.cq.wcm.foundation.TemplatedContainer template has no structure support 27.03.2025 15:43:25.690 *ERROR* [[0:0:0:0:0:0:0:1] [1743070405657] GET /content/mchp/en-us.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=nt:unstructured, superType=null, path=/content/mchp/en-us/jcr:content/root 27.03.2025 15:43:25.690 *ERROR* [[0:0:0:0:0:0:0:1] [1743070405657] GET /content/mchp/en-us.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=nt:unstructured, superType=null, path=/content/mchp/en-us/jcr:content/image 27.03.2025 15:43:53.548 *INFO* [[0:0:0:0:0:0:0:1] [1743070433518] GET /content/mchp/en-us.html HTTP/1.1] com.day.cq.wcm.foundation.TemplatedContainer page has no template assigned

 

 

However If I logged In , pages are working fine. Any idea why this is happening ? Am I missing anything ?

 

Thanks, 

Poovitha S

Best answer by PRATHYUSHA_VP

Hi @poovithaselvaraj 

 

Please check the below link for same issue. It looks like permission issue when you're not logged in publish instance.

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/quot-page-has-no-template-assigned-quot-error/m-p/314873

 

Hope this helps

 

Thanks

2 replies

PRATHYUSHA_VP
Community Advisor
PRATHYUSHA_VPCommunity AdvisorAccepted solution
Community Advisor
March 27, 2025

Hi @poovithaselvaraj 

 

Please check the below link for same issue. It looks like permission issue when you're not logged in publish instance.

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/quot-page-has-no-template-assigned-quot-error/m-p/314873

 

Hope this helps

 

Thanks

    AmitVishwakarma
    Community Advisor
    AmitVishwakarmaCommunity Advisor
    Community Advisor
    March 27, 2025

    Hi @poovithaselvaraj ,

    1. Verify Page Template Assignment

    From the error logs, AEM is saying:

    com.day.cq.wcm.foundation.TemplatedContainer page has no template assigned

    This means your page does not have a valid template assigned, or the template does not support structure mode.

    Solution:

         - Log in to AEM Author → Navigate to /content/mchp/en-us
         - Open the page properties and check if the page has a valid template assigned.
         - If missing, reassign the correct template under page properties → advanced and republish the page.
         - Ensure the template exists under /conf/<your-project>/settings/wcm/templates/ and is properly configured.

     

    2. Check Anonymous User Permissions on the Publish Instance

    Since the page works when logged in but fails when logged out, it’s likely a permission issue for the anonymous user.

    Solution:

         - Log in to AEM Publish (/crx/packmgr or /useradmin)
         - Go to /useradmin
         - Search for the anonymous user (everyone or anonymous)
         - Assign Read Access (Read permission) to:

              - /content/mchp/en-us

              - /conf/<your-project> (if using Editable Templates)

              - /etc.clientlibs/<your-project> (for client libraries, if applicable)
              - Save and restart your publisher instance.

     

    3. Check Page Component & Rendering Issues

    Your logs show:

    org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=nt:unstructured

    This means AEM cannot resolve the renderer for the page structure.

    Solution:

         - Verify that all required components for the page template are deployed and active in /system/console/components.
         - Make sure the Core Components bundle is installed and active (for editable templates).
         - Check if the cq:template property exists for the page in /content/mchp/en-us/jcr:content.

    4. Disable Dispatcher Cache (For Debugging)

    If you’re using a Dispatcher, it may be blocking content rendering.
    Temporarily disable caching by adding the following rule in dispatcher.any:

    /cache { /rules { /0000 { /glob "*" /type "deny" } } }

    5. Restart AEM and Validate:

    Restart AEM Publisher


    Regards,
    Amit

      Terms & ConditionsAccessibility statement

      Loading footer...