Expand my Community achievements bar.

SOLVED

AEM editor is not loading anything and when we restart the instance it shows http 503 error

Avatar

Level 1

AEM editor is not loading anything and when we restart the instance it shows HTTP ERROR 503 Problem accessing /. Reason: AuthenticationSupport service missing. Cannot authenticate request. Even after deleting the quickstart and reopening the instance again it works for 15 to 20 minutes and doesn't work again 

Can someone help how to resolve this issue?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @SyamKowshik ,

In addition to @Fanindra_Surat that's known issue only If you are working with SPA project, do follow the below steps

  • Navigate /apps/spa/osgiconfig/config/org.apache.sling.jcr.repoinit.RepositoryInitializer~spa.cfg.json
  • Delete .cfg.json or replace it's script into a -.config

Otherwise as @DEBAL_DAS suggested worth visiting these links

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-restart-issue-authenti...

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/authenticationsupport-serv...

Regards,

Santosh

View solution in original post

5 Replies

Avatar

Community Advisor

Hi @SyamKowshik - This is a known issue due to the presence of a repoinit config file in the project deployed, resulting in a repository initialization error causing HTTP 503 on AEMs. To fix this, either remove the Repoinit file from the configs if not using or replace it with a org.apache.sling.jcr.repoinit.RepositoryInitializer-.config file from both the project you are deploying and the /crx-quickstart/launchpad/config/org/apache/sling/jcr location in file system.

 

Ref: https://github.com/adobe/aem-project-archetype/issues/852

 

Thanks,

Fani

 

Avatar

Correct answer by
Community Advisor

Hi @SyamKowshik ,

In addition to @Fanindra_Surat that's known issue only If you are working with SPA project, do follow the below steps

  • Navigate /apps/spa/osgiconfig/config/org.apache.sling.jcr.repoinit.RepositoryInitializer~spa.cfg.json
  • Delete .cfg.json or replace it's script into a -.config

Otherwise as @DEBAL_DAS suggested worth visiting these links

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-restart-issue-authenti...

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/authenticationsupport-serv...

Regards,

Santosh

Avatar

Community Advisor

@SantoshSai - Not necessarily. We encountered similar issues on non-SPA projects as well and fixed them by removing or correcting the file.

Avatar

Community Advisor

Good to know. However, I have deployed multiple projects with same but never experienced such in non-SPA

Screen Shot 2022-06-03 at 10.45.08 PM.png