# Reverse proxy with marvel

**URL:** <https://discuss.elastic.co/t/reverse-proxy-with-marvel/66322>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [November 17, 2016, 4:20am UTC](https://discuss.elastic.co/t/reverse-proxy-with-marvel/66322 "2016-11-17T04:20:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![niraj\_kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_kumar/32/4130_2.png) [@niraj\_kumar](https://discuss.elastic.co/u/niraj_kumar)\
**Post date:** [November 17, 2016, 4:20am UTC](https://discuss.elastic.co/t/reverse-proxy-with-marvel/66322/1 "2016-11-17T04:20:41Z")

</div>

I have a marvel installed ( v 2.4.1 ) and kibana (v 4.6.1 ) and i want to setup reverse proxy in order to access marvel.

If i access IP\_OF\_KIBANA:5601 i can access the kibana page but when i use the reverse proxy thing the URI reverts back to FQDN/app/kibana and comes p with the following error

"error":{"root\_cause":[{"type":"illegal\_argument\_exception","reason":"No feature for name [kibana]"}],"type":"illegal\_argument\_exception","reason":"No feature for name [kibana]"},"status":400}

I have installed apache2 and want to make this configuration work. Please suggest.

---

<div class="post-metadata">

**Author:** ![LeeDr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leedr/32/9289_2.png) [@LeeDr](https://discuss.elastic.co/u/LeeDr)\
**Post date:** [December 5, 2016, 9:29pm UTC](https://discuss.elastic.co/t/reverse-proxy-with-marvel/66322/2 "2016-12-05T21:29:13Z")

</div>

Hi Niraj,

I see nobody responded to your question. Did you find a solution to your issue?

If you did, can you please post anything that you think might help others?

If not, can you explain your configuration a little more?  
Why are you using the reverse proxy? Kibana can access Marvel data directly (without a proxy) in the Elasticsearch cluster that it gets its other data from.  
Or is your Marvel data in a different cluster than the one Kibana gets it's other data from?

Thanks,  
Lee

---

<div class="post-metadata">

**Author:** ![niraj\_kumar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_kumar/32/4130_2.png) [@niraj\_kumar](https://discuss.elastic.co/u/niraj_kumar)\
**Post date:** [December 6, 2016, 12:50am UTC](https://discuss.elastic.co/t/reverse-proxy-with-marvel/66322/3 "2016-12-06T00:50:39Z")

</div>

The reason i wanted reverse proxy was to keep the ability to secure my kibana/marvel from unwanted usage. Something like a basic auth.

This is the current config i have and it works perfectly fine for kibana, marvel and sense.

```
<Directory "/var/www">
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Require valid-user
AuthType Basic
AuthName "Restricted Area"
AuthBasicProvider file
AuthUserFile /etc/apache2/auth.passwords

```

```
  ProxyPass /app/kibana http://app-01:5601/app/kibana
  ProxyPassReverse /app/kibana http://app-01:5601/app/kibana

  ProxyPass /bundles http://app-01:5601/bundles
  ProxyPassReverse /bundles http://app-01:5601/bundles

  ProxyPass /elasticsearch http://data-01:9200
  ProxyPassReverse /elasticsearch http://data-01:9200

  ProxyPass /app/marvel http://app-01:5601/app/marvel
  ProxyPassReverse /app/marvel http://app-01:/app/marvel

  ProxyPass /api/marvel http://app-01:5601/api/marvel
  ProxyPassReverse /api/marvel http://app-01:/api/marvel

  ProxyPass /status http://app-01:5601/status
  ProxyPassReverse /status http://app-01:/status

  ProxyPass /api/status http://app-01:5601/api/status
  ProxyPassReverse /api/status http://app-01:5601/api/status

  ProxyPass /app/sense http://app-01:5601/app/sense
  ProxyPassReverse /app/sense http://app-01:5601/app/sense

```

--  
Niraj

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 3, 2017, 12:51am UTC](https://discuss.elastic.co/t/reverse-proxy-with-marvel/66322/4 "2017-01-03T00:51:00Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.