It will always be localhost because AEM installed on the same VM. In other words, AEM is localhost to the RHEL server. That said, If you want to access AEM outside of the RHEL server, you would need the RHEL server IP and the PORT AEM instance is running on.

Seems like a provisioning issue, Can you drop an email to "clientcare@adobe.com" to further investigate the issue.

Thanks for sharing! Looks Good 

Its Simple. - Go to the custom metadata schema- Select it- You will see the option "Apply to Folder(s)"- Select the folder you want to apply that schema to

It looks like either you still have the dispatcher module in the code and the corresponding POM file does not exist OR the other way around. C:\Users\eclipse-workspace\vaem.example\pom.xml does not exist Please validate both the module and pom file exists.

Try setting up a DEBUG logger on "org.apache.sling.resourceresolver" and you can how resource resolution is happening in the backend and update your rules accordingly.

I could not find any issues logged internally for this issue. @arunpatidar  - Do you have any ticket reference that I can use to check? That said, All bug fixes in the latest SP release for 6.5 are mentioned at [1] [1] https://docs.adobe.com/content/help/en/experience-manager-65/release-notes/servic...

Can you go to <host>:<port>/useradmin and drill down to the asset level -> check if the user has different permissions for the assets in question. I am pretty sure the permissions at asset level will be different.

Can you try using the "AllowEncodedSlashes On" in the apache vhost config?

Adding to Arun's update , Try using the latest archetype and the core components dependency should be automatically included in the POM file.