AEM Sites not working in local AEM instance

Hi ​@ktp,

Which laptop do you have - Apple Silicon Mac, or Windows on ARM / Snapdragon?

Hello ​@ktp, can you pls help with the following:

1. Do you have any custom javascript OR page properties that interacts with the author services?
2. Any console logs?
3. Could you check if a servlet or something else has been registered on the same resourceType (your page component)

Regards,

Ramkumar

Hi ​@ktp please share a few additional details so that community can help narrow down the root cause more precisely: 

• Browser console errors – Open Developer Tools (F12) and check the Console and Network tabs for any JavaScript errors or failed requests.
• Java version – Run java -version and share the exact version and distribution
• Operating System – Let me know whether you're using Mac (M1/M2/M3) or Windows on ARM.
• AEM SDK version – The exact SDK build/version you downloaded from Adobe.

With this information, we can identify whether the problem is related to JVM compatibility/ARM-specific behavior/client libraries or a frontend rendering issue.

Thanks 

Hi ​@ktp, Kindly install the AEM Guides WKND packages and try creating a page. If you succeed, it will confirm that there is an issue with your project templates.

Hi,

A blank page in AEM usually does not always mean the issue will show up clearly in error.log. In this case, because the page creation wizard loads but becomes blank after selecting a template, I would first check the browser console and network tab to see if any Touch UI/clientlib/Granite UI JavaScript or CSS requests are failing.

I wrote a short checklist here that may help with this type of issue, including blank rendered pages:

https://sourcedcode.com/blog/aem/development/basic-steps-to-debug-an-error-in-aem

The basic flow I would suggest is:

1. Check the browser console first.

2. Check failed network requests, especially clientlibs and Granite UI requests.

3. Then check crx-quickstart/logs/error.log.

4. If error.log does not show anything useful, check the other custom logs under crx-quickstart/logs.

Since you are running this on an ARM-based laptop, I would also validate the same AEMaaCS SDK on another supported environment or machine if possible. This will help confirm whether the issue is caused by the local runtime/JDK/ARM setup or by the project templates/clientlibs themselves.