On my end, I found the solution. The debug script was using the same port 4502 so AEM isn't able to receive the project package when I run `mvn clean install`.

Still experiencing the same error @kautuk_sahni more information would be appreciated

Yeah, vault user and password are defined in the pom.xml file with the same aem credentials, also tried the `useProxy` just now but still getting the same error.

I tried installing the below package and uploaded it but my site still doesn't show on the AEM Sites list.

@ArpitVarshney I can confirm that AEM is running on port 4502. As for the bundles, almost all the bundles are active besides a few that are listed as fragment 

I set the sling.user and sling.password in the pom.xml file's properties, aside from that I usually supply the credentials after running the build on localhost:4502

I'm able to access the AEM instance at http://localhost:4502 however, when I try to build my AEM project, I get the following error.I'm running the following command which from what I understand, builds and runs the AEM project on port 4502 and adds the project to the AEM sites.mvn clean install -s ...