# Kibana behind Haproxy : A basepath problem?

**URL:** <https://discuss.elastic.co/t/kibana-behind-haproxy-a-basepath-problem/161564>\
**Category:** Kibana\
**Created:** [December 19, 2018, 4:55pm UTC](https://discuss.elastic.co/t/kibana-behind-haproxy-a-basepath-problem/161564 "2018-12-19T16:55:19Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Oliv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oliv/32/111867_2.png) [@Oliv](https://discuss.elastic.co/u/Oliv)\
**Post date:** [December 20, 2018, 4:39pm UTC](https://discuss.elastic.co/t/kibana-behind-haproxy-a-basepath-problem/161564/4 "2018-12-20T16:39:48Z")

</div>

No, It doesn't I suppose because of the 127.0.0.1 param in the kibana config.  
Found some information on SELinux blocking ports for HAPROXY, I'm checking this out.

I will keep you posted of course 🙂

Of course if you have other ideas 🙂

EDIT : Kibana worked before the installation of the HAproxy, if needed I can post my original kibana config ( Information is on another pc.)

---

_[View the full topic](https://discuss.elastic.co/t/kibana-behind-haproxy-a-basepath-problem/161564)._