Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

HTTP ERROR 503 (Problem accessing /crx/de. Reason: Service Unavailable)

tushaar_srivastava
Level 4
Level 4

Hi All,

 

I am getting 503 error while opening instance, not sure how to I tired to restart instance.

Since we are using remote AEM environment, where I only can see the instance service in stopping status.

 

Not sure how to fix it using crx-quickstart folder >____

 

tushaars9735484_0-1599123286793.png

 

@kautuk_sahni  @Arun_Patidar  @Vijayalakshmi_S 

 

503 aem6.5 Error
1 Accepted Solution
Andrei_Dantsou
Correct answer by
Level 4
Level 4

Hello @tushaar_srivastava,

The 503 error occurs due to the fact that the service is stopping. You should wait while the instance is completely stopped and to start it again. 
The steps for stopping/starting an instance using the scripts located under <cq-installation>/bin (crx-quickstart/bin folder in your case) are described in the documentation
https://docs.adobe.com/content/help/en/experience-manager-64/deploying/deploying/command-line-start-...

Regards

View solution in original post

3 Replies
Andrei_Dantsou
Correct answer by
Level 4
Level 4

Hello @tushaar_srivastava,

The 503 error occurs due to the fact that the service is stopping. You should wait while the instance is completely stopped and to start it again. 
The steps for stopping/starting an instance using the scripts located under <cq-installation>/bin (crx-quickstart/bin folder in your case) are described in the documentation
https://docs.adobe.com/content/help/en/experience-manager-64/deploying/deploying/command-line-start-...

Regards

View solution in original post

Vijayalakshmi_S
Community Advisor
Community Advisor

Hi @tushaar_srivastava,

Most of the time, we get this error when the server is not completely up and trying to access at that point in time. 

Give it some time to start up and then access.

If the error still persist,  

  • Try to access Felix console and check if all the bundles are active.
  • Check error.log for error/exception.

Update this thread if you get to see any exception.

 

surabhikatiyar
Employee
Employee

Check the AEM error.log file and see if you are getting the "AuthenticationSupport service missing. Cannot authenticate request" error trace.

 

If yes, then try to re-index the complete repository by deleting the "index" folder under the path /crx-quickstart/repository. And then restart the instance and monitor the logs.

 

If you still get this error, try to restore the instance from the last healthy backup.

 

This type of issue comes up when the instance is shut down abruptly and the repository could not be shut down gracefully.