AEM http://localhost:4502/ getting Error 404 Not Found after upgrading SDK version to 2025.7.21570

[winter_bunny]

EM jar version: 2025.7.21570.20250715T080514Z-250600

I tried updating my AEM local instance to the latest jar version, downloaded it and renamed it to cq-quickstart.jar. Replaced the old jar file, deleted the crx-quickstart folder and run:

java -jar cq-quickstart.jar 

Once it's done, I got this:

I use IntelliJ and Docker, I stopped all running instance before I triggered the java -jar command.

I tried checking the logs, but couldn't find anything that makes sense. 

Anyone experience the same? Any help is greatly appreciated.

[Sid_Gour]

Hi @winter_bunny ,

You may be experiencing this issue due to recent technical release. 

Stick to older version for now and raise ticket with Adobe for this issue. 
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/release-notes/ma....

Thanks,

[winter_bunny]

I already did, hopefully it will be fixed. Thank you for your reply.

[B_Sravan]

Hi @winter_bunny ,

I'm not sure about the SDK issue mentioned by @Sid_Gour , but I did notice an incorrect naming convention for your JAR file. While it's not the root cause of the current issue, please follow the standard format: <Name>-<Run-mode>-<Port>.jar. For example, you could name it something like AEM-author-p4502.jar.

Regarding the issue, have you checked the error log under the crx-quickstart folder? Path: crx-quickstart/logs/error.log

Here are a few possible causes:

1. Review the error log for any specific messages, and let me know which version you upgraded from. AEMaaCS now recommends using Java 11, 17, or preferably Java 21.

2. It might just need more time to finish loading, so consider waiting a little longer.

Thank you!

Regards,
@B_Sravan 

[winter_bunny]

I upgraded the

AEM jar version: 2025.7.21570.20250715T080514Z-250600 and

I did try to rename it to aem-author-p4502.jar and retry but still not working, I still get 404. I am using this:

java version "11.0.27" 2025-04-15 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.27+8-LTS-232)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.27+8-LTS-232, mixed mode) 

I checked the error.log, I get these type of *ERROR*

16.07.2025 18:52:41.205 *ERROR* [FelixStartLevel] com.adobe.granite.product.support.impl.ServiceProtector Preventing whiteboard registration of protected servlet context named com.adobe.aem.adobeapi from bundle com.adobe.aem.repoapi [255] : [org.osgi.service.http.context.ServletContextHelper]

16.07.2025 18:52:41.443 *ERROR* [ResourceResolverFactory deregistration on close] com.adobe.granite.product.support.impl.ServiceProtector Preventing whiteboard registration of protected servlet context named com.adobe.aem.adobeapi from bundle com.adobe.aem.openapi-support [200] : [org.osgi.service.http.context.ServletContextHelper]

16.07.2025 18:52:47.785 *ERROR* [FelixStartLevel] com.adobe.granite.product.support.impl.ServiceProtector Preventing whiteboard registration of protected servlet context named org.apache.felix.webconsole from bundle org.apache.felix.webconsole [87] : [org.osgi.service.servlet.context.ServletContextHelper]

 I also waited extra time to load the jar file but nothing happens, still 404 when i refresh the login page.

[Uppari_Ramesh]

Hi @winter_bunny ,

Please go inside crq quickstart folder amd then go to launchpad config org apache sling jcr repoint and delete all files inside. 

Before delete, atop aem instance and then restart. Some times it works.

Thanks 

Ramesh 

[winter_bunny]

Hello, I tried to do this but still getting 404 on http://localhost:4502/

[winter_bunny · Accepted solution]

UPDATE: New version was added.

AEM SDK v2025.07.21575.1752585123262-250600

This version now works and login page is now accessible.

[Sid_Gour]

That's what, even I told the same in my first post. Recent releases (10th July and 15th July) had issues which created such inconveniences and Adobe was quick enough to fix those issues.