Hi Team,
I have performed in-place upgrades on author and publisher instances and after all the process is ok. Verified the upgrade.log file and error.log file.
Now, when I try to log in to the publisher instance - not able to log in.
Tried login via
https://<IP>:<PORT>/libs/granite/core/content/login.html?resource=/crx/de/index.jsp
I got navigated to CRXDE. But, only /content and /bin are being shown
https://<IP>:<PORT>/libs/granite/core/content/login.html?resource=/system/console
I got the login screen again
Any suggestions or pointers would be appreciated.
__PRESENT
__PRESENT
Solved! Go to Solution.
Views
Replies
Total Likes
Thanks everyone for looking into it.
I found the issue with the setup at my end. The login issue occured when I installed the service pack 9.. Which means, when upgraded to 6.5.0 - login was ok. When I installed service pack 9 - the login URL stopped working - only on publish instance.
To login, if I append the URL with "?sling:authRequestLogin=1", login works fine.
Maybe, this can help others facing similar issues.
Hi @RitendraS11
You should be able to login using the below URL:
http://HOST:PORT/libs/granite/core/content/login.html
Please let us know what error you see when you try to login. Also request to check the browser console when trying for login.
Thanks,
Asutosh
@Asutosh_Jena_ Thanks for checking. But, I have already mentioned in my post that it's not working.
Hi @RitendraS11 ,
Which service pack of 6.5 have you installed?
You may refer https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/after-service-pack-6-5-8-i...
Thanks
Hi @RitendraS11
What user are you using? admin then it should work, could you please check error.log when you do login?
restart AEM and try again.
The server got corrupted and stopped working. So, I can't check it anymore.
Thanks for looking into it!
@RitendraS11 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
Views
Replies
Total Likes
Thanks everyone for looking into it.
I found the issue with the setup at my end. The login issue occured when I installed the service pack 9.. Which means, when upgraded to 6.5.0 - login was ok. When I installed service pack 9 - the login URL stopped working - only on publish instance.
To login, if I append the URL with "?sling:authRequestLogin=1", login works fine.
Maybe, this can help others facing similar issues.
Views
Likes
Replies
Views
Like
Replies