Matching Host Groups between Platform and Site applications not working

Experience Manager (PaaS/OnPrem)
1

Currently trying to configure cms, on a different domain, so site: demo.example.com and cms: cms-demo.example.com. I’ve encountered two problems:

  • the hst:showcontextpath property on hst:platform, doesn’t seem to do anything, the cms wil only be available on cms-demo.example.com/cms, If hst:showcontextpath is set on true or false.
  • In the channel-manager the correct channels are found but when trying to open the channel, it resolves to: cms-demo.example.com/site/_cmscontext which gives a 404

example config:

hst:hst

/development:
  jcr:primaryType: hst:virtualhostgroup
  /com:
    jcr:primaryType: hst:virtualhost
    /example:
      jcr:primaryType: hst:virtualhost
      /demo:
        jcr:primaryType: hst:virtualhost
        /hst:root:
          jcr:primaryType: hst:mount
          hst:alias: resourceapi
          hst:homepage: root
          hst:mountpoint: /hst:hst/hst:sites/example-site
          hst:pagemodelapi: resourceapi
          hst:schemeagnostic: true
		  
hst:platform

/development:
  jcr:primaryType: hst:virtualhostgroup
  /com:
    jcr:primaryType: hst:virtualhost
    hst:scheme: https
    hst:showcontextpath: false
    hst:showport: false
    /example:
      jcr:primaryType: hst:virtualhost
      /cms-demo:
        jcr:primaryType: hst:virtualhost
        /hst:root:
          jcr:primaryType: hst:mount
          hst:ismapped: false
          hst:namedpipeline: WebApplicationInvokingPipeline

I’ve read the Hosts Configuration - Bloomreach Experience Manager (PaaS/Self-Hosted) - The Fast and Flexible Headless CMS three times over as well as Experience Manager Troubleshooting - Bloomreach Experience Manager (PaaS/Self-Hosted) - The Fast and Flexible Headless CMS but it does not seem the work as described

With kind regards,
Joost

2

Context setting is pretty simple: if you are using context, and in your case you are,
you need to set it to true.

If you have apache or nginx and you are stripping /cms context, then set it to false.
Same holds for site parts.

For example, our demo ( https://cms.demo.onehippo.com/ ) is stripping /cms context via apache proxy.