# Console not available for cms url

**URL:** <https://community.bloomreach.com/t/console-not-available-for-cms-url/1898>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [May 6, 2020, 2:55pm UTC](https://community.bloomreach.com/t/console-not-available-for-cms-url/1898 "2020-05-06T14:55:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dennis\_Vonk](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/dennis_vonk/32/369_2.png) [@Dennis\_Vonk](https://community.bloomreach.com/u/Dennis_Vonk)\
**Post date:** [May 6, 2020, 2:55pm UTC](https://community.bloomreach.com/t/console-not-available-for-cms-url/1898/1 "2020-05-06T14:55:17Z")

</div>

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…

- browse to [http://site.local.issues.nl](http://site.local.issues.nl) → works and shows site
- browse to [http://cms.local.issues.nl](http://cms.local.issues.nl) → works and shows BRXM
- browse to htpp://localhost:8080/cms/console → works and shows BR console

BUT:

- browse to [http://cms.local.issues.nl/console](http://cms.local.issues.nl/console) → **doesn’t work**  
I get redirected to  
[http://cms.local.issues.nl/cms/?initialPath=/cms/](http://cms.local.issues.nl/cms/?initialPath=/cms/)

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

Any help is appreciated!

---

<div class="post-metadata">

**Author:** ![machak](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/machak/32/1298_2.png) [@machak](https://community.bloomreach.com/u/machak)\
**Post date:** [May 6, 2020, 5:01pm UTC](https://community.bloomreach.com/t/console-not-available-for-cms-url/1898/2 "2020-05-06T17:01:52Z")

</div>

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:

> **[Configure Apache HTTP Server as Reverse Proxy for Hippo - Bloomreach...](https://documentation.bloomreach.com/14/library/deployment/configuring/configure-apache-httpd-as-reverse-proxy-for-hippo.html)**
>
> Configure the Apache HTTP Server (httpd) as a reverse proxy for Hippo's CMS and delivery tier web applications.

---

<div class="post-metadata">

**Author:** ![Dennis\_Vonk](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/dennis_vonk/32/369_2.png) [@Dennis\_Vonk](https://community.bloomreach.com/u/Dennis_Vonk)\
**Post date:** [May 7, 2020, 6:28am UTC](https://community.bloomreach.com/t/console-not-available-for-cms-url/1898/3 "2020-05-07T06:28:19Z")

</div>

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 ☹

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

---

<div class="post-metadata">

**Author:** ![Dennis\_Vonk](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/dennis_vonk/32/369_2.png) [@Dennis\_Vonk](https://community.bloomreach.com/u/Dennis_Vonk)\
**Post date:** [May 8, 2020, 6:11am UTC](https://community.bloomreach.com/t/console-not-available-for-cms-url/1898/4 "2020-05-08T06:11:47Z")

</div>

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.
