Forbidden access to /aem/start.html

[ElmoPro]

Hello Community Warriors, 

I cannot access to http://localhost:4502/aem/start.html , neither to http://localhost:4502/sites.html.

I get forbidden cannot serve request to "/aem/start.html ". 

HTTP ERROR 403 Forbidden

URI:STATUS:MESSAGE:SERVLET:

/aem/start.html

403

Forbidden

org.apache.felix.http.base.internal.dispatch.DispatcherServlet-1d6f1c75

HTTP ERROR 403 Forbidden

URI:STATUS:MESSAGE:SERVLET:

/sites.html

403

Forbidden

org.apache.felix.http.base.internal.dispatch.DispatcherServlet-1d6f1c75

==> I don't have any error on the console 

Please help

[HeenaMadan]

Can you try on http://localhost:4502/libs/granite/core/content/login.html

 if still you get 403 then check logs and paste error message here

[priyak]

@ElmoPro 

Can you please verify if you are able to open /crx/de or /system/console.

If not can you restart the instance and check for any error logs.

And can you also specify the version you are using.

[HrishikeshKa]

Hi @ElmoPro ,

It seems like you're encountering a 403 Forbidden error when trying to access specific pages in Adobe Experience Manager (AEM) through your localhost. This error typically occurs due to permission issues or misconfiguration. Here are some steps you can take to troubleshoot:

1. Check Permissions: Ensure that the user you're logged in as has the necessary permissions to access the /aem/start.html and /sites.html pages. You might need to check your user permissions within AEM or the servlet container (like Apache Felix).

2. Verify URL: Double-check the URLs you're using. Make sure they are correct and properly formed. Sometimes a small typo can lead to a 403 error.

3. Check Configuration Files: Review your AEM configuration files, especially any security-related configurations. Ensure that there are no restrictions or rules preventing access to these pages.

4. Restart AEM: Try restarting your AEM instance. Sometimes, a simple restart can resolve permission-related issues.

5. Inspect Logs: Check the AEM logs for any relevant error messages or warnings. Even though you mentioned no errors on the console, there might be logs in other files.

6. Proxy or Firewall: If you're accessing AEM through a proxy server or firewall, ensure that they are not blocking access to these URLs.

7. Clear Browser Cache: Sometimes, cached data in your browser can cause issues. Try accessing the URLs in an incognito/private browsing window or clear your browser cache.

8. Check for Updates: Ensure that your AEM instance is up-to-date. Sometimes, bugs or security vulnerabilities in older versions can cause unexpected behavior.

9. Consult Documentation or Community: If none of the above steps resolve the issue, consult the AEM documentation or community forums for further assistance. It's possible that others have encountered similar issues and have solutions or workarounds.

By systematically going through these steps, you should be able to diagnose and resolve the 403 Forbidden error you're experiencing with AEM.

[aanchal-sikka]

@ElmoPro 

It is happening for a specific credential or all (including admin).

If its specific, please check the permissions of this user.

[Harwinder-singh]

@ElmoPro Can you check the status of bundles via /system/console? 

[ElmoPro · Accepted solution]

I cannot access to any link of aem. I lost much time working on this. So I decided to re install all the packages, and to reconfigure the environement.

thanks for all yours replies. I really appreciate them.