AEM publish instance is not accepting default password | Community
Skip to main content
December 18, 2020
Solved

AEM publish instance is not accepting default password

  • December 18, 2020
  • 3 replies
  • 2580 views

Hi,

 

While trying to create AEM publish instance , using aem-65-p4503 jar, on start up it is navigating to login page. Default admin admin is not being accepted by it. Anyone any idea ??

 

 

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 joerghoh

if you rename the quickstart.jar to aem-65-p4503, the runmode "publish" is not deduced from the name of the jar, but only the port, so technically you have an author running on port 4503. But anyway, the default passwords still should work. You can either try to analyze the issue or you can just start over.

3 replies

arunpatidar
Community Advisor
Community Advisor
December 18, 2020

you can try to setup again by running jar from command line, there you can set admin password by yourself.

Arun Patidar
shelly-goel
Adobe Employee
Adobe Employee
December 18, 2020

@narin_209202  It asks for the admin password while setting up the instance. In case you're not sure what the password was set to, you can try resetting it with oak-run command as mentioned in this link:

 

https://helpx.adobe.com/experience-manager/kb/How-to-reset-the-admin-password-in-AEM-6-3.html

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
December 20, 2020

if you rename the quickstart.jar to aem-65-p4503, the runmode "publish" is not deduced from the name of the jar, but only the port, so technically you have an author running on port 4503. But anyway, the default passwords still should work. You can either try to analyze the issue or you can just start over.

narindera257447
Level 2
December 22, 2020
Thank you for help , looks like some instance creation issue. Recreated the instance and it worked fine.
November 20, 2024

How did u recreated instance, I am also facing same issue for author instance.