# Kibana 4.2 reverse proxy

**URL:** <https://discuss.elastic.co/t/kibana-4-2-reverse-proxy/33649>\
**Category:** Kibana\
**Created:** [November 3, 2015, 4:13pm UTC](https://discuss.elastic.co/t/kibana-4-2-reverse-proxy/33649 "2015-11-03T16:13:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Carlos\_Vega\_Moreno](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_vega_moreno/32/3773_2.png) [@Carlos\_Vega\_Moreno](https://discuss.elastic.co/u/Carlos_Vega_Moreno)\
**Post date:** [November 3, 2015, 4:13pm UTC](https://discuss.elastic.co/t/kibana-4-2-reverse-proxy/33649/1 "2015-11-03T16:13:07Z")

</div>

I updated kibana to the newest version and now the paths are relative instead of absolute so my reverse proxy is broken. Is there any way to fix it?

Is like this issue but none fixed it

> <https://github.com/elastic/kibana/issues/5230>

My previous nginx conf was:

```
    location /kibanaadmin/ {

    auth_basic "Restricted Access";
    auth_basic_user_file /etc/nginx/htpasswd.users;

    proxy_pass http://localhost:5601;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;

}

```

But it doesn't work anymore. Is there a fix?

---

<div class="post-metadata">

**Author:** ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)\
**Post date:** [November 5, 2015, 4:14am UTC](https://discuss.elastic.co/t/kibana-4-2-reverse-proxy/33649/2 "2015-11-05T04:14:48Z")

</div>

The fix is slated for 4.2.1, which is the next bugfix release we are working toward.

---

<div class="post-metadata">

**Author:** ![Carlos\_Vega\_Moreno](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_vega_moreno/32/3773_2.png) [@Carlos\_Vega\_Moreno](https://discuss.elastic.co/u/Carlos_Vega_Moreno)\
**Post date:** [November 5, 2015, 8:59am UTC](https://discuss.elastic.co/t/kibana-4-2-reverse-proxy/33649/3 "2015-11-05T08:59:29Z")

</div>

BUT, will be like the older releases? or a variation of the current approach. Just to know, thanks ! 😀

Greetings,

CV

---

<div class="post-metadata">

**Author:** ![Carlos\_Vega\_Moreno](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_vega_moreno/32/3773_2.png) [@Carlos\_Vega\_Moreno](https://discuss.elastic.co/u/Carlos_Vega_Moreno)\
**Post date:** [November 13, 2015, 11:53am UTC](https://discuss.elastic.co/t/kibana-4-2-reverse-proxy/33649/4 "2015-11-13T11:53:35Z")

</div>

I get an error with Timelion, maybe it has something to do with the reverse proxy. Is there any way to fix it?

 ![](https://us1.discourse-cdn.com/elastic/original/2X/6/620dbd3cdb9935bdf75f36bed69d4c9cd3f73740.png)

---

<div class="post-metadata">

**Author:** ![Carlos\_Vega\_Moreno](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_vega_moreno/32/3773_2.png) [@Carlos\_Vega\_Moreno](https://discuss.elastic.co/u/Carlos_Vega_Moreno)\
**Post date:** [November 13, 2015, 12:02pm UTC](https://discuss.elastic.co/t/kibana-4-2-reverse-proxy/33649/5 "2015-11-13T12:02:54Z")

</div>

Solved adding this to my nginx conf

> location /timelion {

> ```
> auth_basic "Restricted Access";
> auth_basic_user_file /etc/nginx/htpasswd.users;
> 
> ```

> ```
> proxy_pass http://localhost:5601/timelion;
> proxy_http_version 1.1;
> proxy_set_header Upgrade $http_upgrade;
> proxy_set_header Connection 'upgrade';
> proxy_set_header Host $host;
> proxy_cache_bypass $http_upgrade;
> 
> ```

> ```
> }
> 
> ```

---

<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:** [July 6, 2017, 2:09pm UTC](https://discuss.elastic.co/t/kibana-4-2-reverse-proxy/33649/6 "2017-07-06T14:09:09Z")

</div>