HTTP ERROR 404 Problem accessing /system/console/configMgr. Reason: Not Found | Community
Skip to main content
Jeanmaradiaga
August 31, 2021
Solved

HTTP ERROR 404 Problem accessing /system/console/configMgr. Reason: Not Found

  • August 31, 2021
  • 2 replies
  • 3275 views

I was updating our QA environment with a service pack and it worked perfectly, I checked the new AEM version on the landing page and it had been updated correctly, so I then went on to upload a config package for some services and installing that but the instance just got stuck in the installing screen. After a while I reloaded and no matter where I go (logs, crx, console) I get a white screen with the error in the title, so my question is. Now what?


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 Asutosh_Jena_

Hi @jeanmaradiaga 

 

Please restart the instance and monitor the logs to ensure the server has restarted properly.

Now you should be able to access all consoles.

 

Post restart validate if the installation has been completed successfully.

 

Thanks!

2 replies

Asutosh_Jena_
Community Advisor
Asutosh_Jena_Community AdvisorAccepted solution
Community Advisor
August 31, 2021

Hi @jeanmaradiaga 

 

Please restart the instance and monitor the logs to ensure the server has restarted properly.

Now you should be able to access all consoles.

 

Post restart validate if the installation has been completed successfully.

 

Thanks!

Jeanmaradiaga
August 31, 2021

@asutosh_jena_ - This may be a dumb question but how I am supposed to re-start the instance? Via SSH?

Asutosh_Jena_
Community Advisor
Community Advisor
August 31, 2021

If this is a Linux server, then you can navigate to your AEM installation directory.

<AEM Installation Directory>/crx-quickstart/bin

You can see a file named "stop"

 

Fire the command: ./stop

 

This will stop the instance in 3-4min. You can monitor the log to see if it's stopped or not.

 

For Restart, navigate to same location and fire the command: ./start

 

 

Jeanmaradiaga
August 31, 2021

Thanks, I'll have to ask for the credentials first thing in the morning then.