Thanks - I assumed this was likely the case.  The potential concern is for clients in regulated industries eg banking where it is necessary for them to be able to fully understand where their data is stored including in secure backup form.

this is where use of the dispatcher and potentially loadbalancer makes sense, as you can then map a proper domain main to the server and expose it safely with relevant allow lists etc if you need to limit access to specific source IP ranges (eg your office locations).

Configuration of HTTPS for the AEM Author is only possible by initially connecting over HTTP as out of the box AEM doesn't support HTTPS connections.   If it's a remote machine as in your case running in AWS Cloud, you could avoid exposing it publicly via HTTP by using an SSH tunnel from your local ...

Are you able to share the full stack trace of the error in the logs? Does the same happen if you pre-create the destination folder before installing the package? from the above it appears to relate to the import creating the folders to enable it to place content deeper in the tree.  Can you check in...

oops - posted the above from the wrong account. Martin

the x-frame-options header needs to be set in apache vhost config, rather than in the dispatcher farm configuration. In our Managed Services deployment, this header is set by default: Header merge X-Frame-Options SAMEORIGIN "expr=%{resp:X-Frame-Options}!='SAMEORIGIN'" x-frame-options is somewhat lim...

Are you able to compare the properties you see on your page and a we.retail page after creation based on the editable template?  wondering if you template is adding some properties which are causing the inheritance to to work differently.

is the content also missing from the repo structure if you look at the page in crx/de?are you running the latest service pack, and does the same happen with 6.5.0 with no SPs installed?