@varaande  - were you able to resolve the issue? If yes, please share the fix you applied.

Hello everyone, I am facing an issue where the AEM dispatcher is not serving the page from the publisher. AEM setup is on-premise and non-prod. I had AEM 6.3.3.8 running with the dispatcher(4.2.x) on the Apache server, where the publisher and dispatcher are hosted on separate servers. I had performe...

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 ...

Hi Team,I am performing in-place upgrade from AEm 6.3 to AEM 6.5. Everything worked fine and my server got updated to 6.5.0. Now, I wanted to install the service pack 9. After installation of service pack, when i did a server restart - login credentials doesn't work (same login was working with 6.3 ...

The server got corrupted and stopped working. So, I can't check it anymore. Thanks for looking into it!

Hi Everyone, I have a system running on AEM 6.3.3.8 and I wanted to migrate it to 6.5. I want to keep every setting as-is. So, I am performing an in-place upgrade. Every log was OK except the below error - lines from upgrade.log file*INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator UP...

@Asutosh_Jena_ Thanks for checking. But, I have already mentioned in my post that it's not working.

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 viahttps://<IP>:<PORT>/libs/granite/core/content/login...

The website uses Google Recaptcha and hence, it allows browsers to have google.com cookies listed under their domain.Also, third-party cookies are blocked by default in Firefox, Safari and Brave browsers. So, a similar issue is not there. The issue lies in the Google Chrome browser and EDGE browser....

@robertol6836527 - As mentioned in my query, the vanity URLs appeared fine in the author instance and not in publishers for newly changed URLs. In my checks, I found that some oak indexes were failing. Once, the indexes were re-indexed - the issue was resolved.