Resource /libs/granite/core/content/login.html not found | Community
Skip to main content
New Participant
January 15, 2024
Solved

Resource /libs/granite/core/content/login.html not found

  • January 15, 2024
  • 2 replies
  • 2981 views

Hi, I am not able to login to my AEM Publisher instance in browser as it was showing the below error,

So, I checked the error log and found the below response,

 

GET /libs/granite/core/content/login.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /libs/granite/core/content/login.html not found

 

Because of this issue I am not able to access /system/console and it's features. Please advise how to proceed and rectify this.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by pulkitvashisth

Hi @ashishshetty 
As you say there is nothing you can find in the error logs
And you are not able to access the felix console (system/console).
You can check for these:
1. Check referrer filter configuration: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/not-able-to-login-in-aem-publish-instance/m-p/188155

2. Restarting the instance can also help resolve this.

3. If everything is fine, and its a Apache issue, you can rewrite rules as apache level to resolve this,
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/redirecting-libs-granite-core-content-login-to-error-page-in-aem/m-p/364187

 

 

2 replies

EstebanBustamante
New Participant
January 15, 2024

This issue may occur if your anonymous user lacks proper read permissions. You can work around this by logging in through any of the means below:

  • Try the wknd site (if available) and then log in through this site.

     

  • Go to the weRetail site (if available) and then log in through this site.

  • Go to the crx/de URL and log in through this UI.

Hope this helps.

Esteban Bustamante
pulkitvashisth
pulkitvashisthAccepted solution
New Participant
January 15, 2024

Hi @ashishshetty 
As you say there is nothing you can find in the error logs
And you are not able to access the felix console (system/console).
You can check for these:
1. Check referrer filter configuration: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/not-able-to-login-in-aem-publish-instance/m-p/188155

2. Restarting the instance can also help resolve this.

3. If everything is fine, and its a Apache issue, you can rewrite rules as apache level to resolve this,
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/redirecting-libs-granite-core-content-login-to-error-page-in-aem/m-p/364187