# Reverse Proxy Issues on-premise deployment w/ v14.6.2

**URL:** <https://community.bloomreach.com/t/reverse-proxy-issues-on-premise-deployment-w-v14-6-2/2819>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [October 11, 2021, 8:51pm UTC](https://community.bloomreach.com/t/reverse-proxy-issues-on-premise-deployment-w-v14-6-2/2819 "2021-10-11T20:51:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![aoliva](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/aoliva/32/280_2.png) [@aoliva](https://community.bloomreach.com/u/aoliva)\
**Post date:** [October 11, 2021, 8:51pm UTC](https://community.bloomreach.com/t/reverse-proxy-issues-on-premise-deployment-w-v14-6-2/2819/1 "2021-10-11T20:51:51Z")

</div>

We have followed the instructions to set the on-premise instance and is running now, but then I set up and apache as a reverse proxy as per the documentation: [Configure Apache HTTP Server as Reverse Proxy for Hippo - Bloomreach Experience - The Headless Digital Experience Platform Built for Commerce](https://documentation.bloomreach.com/14/library/deployment/configuring/configure-apache-httpd-as-reverse-proxy-for-hippo.html)

Afterwards, the site looks ok, but with the CMS I found 2 issues ATM:

- When trying to access the CMS console, it goes in an infinite loop
- When entering the CMS and checking the Experience Manager section, the channel does not appear.

I reached the instance directly bypassing the apache proxy for double checking, but when doing it everything seems fine and I can reach the console.

Could anyone provide some guidance what could be missing on the configs?

Thanks!

---

<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:** [October 12, 2021, 11:04am UTC](https://community.bloomreach.com/t/reverse-proxy-issues-on-premise-deployment-w-v14-6-2/2819/2 "2021-10-12T11:04:15Z")

</div>

you probably need to adjust context path property:

```auto
hst:showcontextpath: false

```

depending if you are accessing cms via context path or not ([foo.com/cms](http://foo.com/cms) or just [cms.foo.com](http://cms.foo.com), without context path)

To correct it, you can use safe-fail mode, ? **HstMode** =false

```auto
https://cms.myproject.com/console?HstMode=false

```

see:

> **[Hosts Configuration - Bloomreach Experience - The Headless Digital Experience...](https://documentation.bloomreach.com/14/library/concepts/hst-configuration-model/hosts-configuration.html)**
>
> The headless digital experience platform built for commerce

---

<div class="post-metadata">

**Author:** ![aoliva](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/aoliva/32/280_2.png) [@aoliva](https://community.bloomreach.com/u/aoliva)\
**Post date:** [October 12, 2021, 11:35pm UTC](https://community.bloomreach.com/t/reverse-proxy-issues-on-premise-deployment-w-v14-6-2/2819/3 "2021-10-12T23:35:43Z")

</div>

Thanks for the response, I tried what you mentioned and now the channels are appearing on the exp. mgr., still I found that I have to leave a trailing slash (/) at the end of the URL to get to the console or repository, for example [https://mysite.com/console](https://mysite.com/console) causes the infinite loop, meanwhile if I enter [https://mysite.com/console/](https://mysite.com/console/) it goes to the console.

Any ideas? maybe a rewrite rule is needed I think for that specific case.