Console not available for cms url

Experience Manager (PaaS/OnPrem)
1

given Bloomreach 14.1 and this host definition in hst:myproject:

/local-env:
  jcr:primaryType: hst:virtualhostgroup
  hst:defaultport: 80
  /nl:
    jcr:primaryType: hst:virtualhost
    hst:showcontextpath: false
    hst:showport: false
    /issues:
      jcr:primaryType: hst:virtualhost
      /local:
        jcr:primaryType: hst:virtualhost
        /site:
          jcr:primaryType: hst:virtualhost
          /hst:root:
            jcr:primaryType: hst:mount
            hst:alias: Main
            hst:mountpoint: /hst:myproject/hst:sites/main

and hst:platform:

/local-env:
  jcr:primaryType: hst:virtualhostgroup
  hst:defaultport: 8080
  /nl:
    jcr:primaryType: hst:virtualhost
    /issues:
      jcr:primaryType: hst:virtualhost
      /local:
        jcr:primaryType: hst:virtualhost
        /cms:
          jcr:primaryType: hst:virtualhost
          /hst:root:
            jcr:primaryType: hst:mount
            hst:ismapped: false
            hst:namedpipeline: WebApplicationInvokingPipeline

and my host definitions:
127.0.0.1 site.local.issues.nl
127.0.0.1 cms.local.issues.nl

and some apache configuration to make the magic happen, I have the following issue…

BUT:

What am I missing, how to make “http://cms.local.issues.nl/console” work on my local machine?

Any help is appreciated!

2

I think you have to look at David Copperfield part. Most probably something is wrong with cookies (sessions?) so, you get redirected to login…however, strange is you get redirected with context path added…so, maybe you haven’t configured context path part correctly…platform should also have hst:showcontextpath: false.

For reference see:

3

Hi Machak,

thanks for you help. So, I added the property hst:showcontextpath and hst:showport for the platform part, as described in the documentation.
Then I did a run in incognito window (chrome) but didn’t help, same error :frowning:

for full disclosure, here is my (very basic) apache configuration:

<VirtualHost *:80>
  ServerName cms.local.issues.nl
  ProxyPreserveHost On
  #INCLUDE THE EXTRA PROXYPASS RULE FOR /site HERE
  ProxyPass /site/ http://localhost:8080/site/
  ProxyPass / http://localhost:8080/cms/
  ProxyPassReverse / http://localhost:8080/cms/
  ProxyPassReverseCookiePath /cms /
  ProxyPreserveHost Off
</VirtualHost>
<VirtualHost *:80>
  ServerName site.local.issues.nl
  # Strip port handling, do this last so above rules will match on 80 as well
  ProxyPass / http://localhost:8080/site/
  ProxyPassReverse / http://localhost:8080/site/
  ProxyPassReverseCookiePath /site /
</VirtualHost>

Additional info about my request (from Chrome -> network tab

console 					302		other														196 B	6 ms	
console/					302		cms.local.issues.nl/console							213 B	4 ms	
?initialPath=/cms/console/	302		cms.local.issues.nl/cms/console/					202 B	6 ms	
?initialPath=/cms/			302		cms.local.issues.nl/cms/?initialPath=/cms/console/	202 B	5 ms	
?initialPath=/cms/			302		cms.local.issues.nl/								202 B	5 ms	
?initialPath=/cms/			302		cms.local.issues.nl/								202 B	5 ms	
?initialPath=/cms/			302		cms.local.issues.nl/								202 B	4 ms	
?initialPath=/cms/			302		cms.local.issues.nl/								202 B	4 ms	
....
net::ERR_TOO_MANY_REDIRECTS

I hope this can help.

Added info: these redirects also occur on the test environment

4

Hi all,

I wanted to let you know that I found a workaround: the solution lies in the request url.
http://cms.local.issues.nl/console
vs
http://cms.local.issues.nl/console/

2nd url is the one that is working. Sometimes, it is that simple.