# Bind kibana's server.host to multiple interfaces (both localhost and 192.168.0.0/16)

**URL:** <https://discuss.elastic.co/t/bind-kibanas-server-host-to-multiple-interfaces-both-localhost-and-192-168-0-0-16/229789>\
**Category:** Kibana\
**Created:** [April 25, 2020, 8:28pm UTC](https://discuss.elastic.co/t/bind-kibanas-server-host-to-multiple-interfaces-both-localhost-and-192-168-0-0-16/229789 "2020-04-25T20:28:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![archon810](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/archon810/32/67033_2.png) [@archon810](https://discuss.elastic.co/u/archon810)\
**Post date:** [April 25, 2020, 8:28pm UTC](https://discuss.elastic.co/t/bind-kibanas-server-host-to-multiple-interfaces-both-localhost-and-192-168-0-0-16/229789/1 "2020-04-25T20:28:01Z")

</div>

Hi,

I'd like to be able to access kibana by typing in localhost:5601 as well as MACHINE\_HOST\_NAME:5601.

Elastic can do it easily with `network.host: [_site_, _local_]`. But I haven't found a way to do this in kibana.

I found [https://stackoverflow.com/questions/34661210/how-to-bind-kibana-to-multiple-host-names-ips](https://stackoverflow.com/questions/34661210/how-to-bind-kibana-to-multiple-host-names-ips), which suggests `0.0.0.0` but ideally I'd like it to be only bound to localhost and eth0:1, which is 192.168.0.0/16 (private) and not the public IP.

I also cross-posted this here [https://github.com/elastic/kibana/issues/64484](https://github.com/elastic/kibana/issues/64484).

Please advise.

Thanks.

---

<div class="post-metadata">

**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\
**Post date:** [April 27, 2020, 8:07pm UTC](https://discuss.elastic.co/t/bind-kibanas-server-host-to-multiple-interfaces-both-localhost-and-192-168-0-0-16/229789/2 "2020-04-27T20:07:17Z")

</div>

hi @archon810

for now, I would track the discussion for the enhancement there [https://github.com/elastic/kibana/issues/64484](https://github.com/elastic/kibana/issues/64484)

In the meantime, perhaps putting a reverse proxy between the user and kibana could help you achieve this: (?YMMV)

e.g.: with nginx, configure `listen` only for localhost and that private IP:  
[http://nginx.org/en/docs/http/ngx\_http\_core\_module.html#listen](http://nginx.org/en/docs/http/ngx_http_core_module.html#listen)

---

<div class="post-metadata">

**Author:** ![archon810](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/archon810/32/67033_2.png) [@archon810](https://discuss.elastic.co/u/archon810)\
**Post date:** [April 27, 2020, 9:14pm UTC](https://discuss.elastic.co/t/bind-kibanas-server-host-to-multiple-interfaces-both-localhost-and-192-168-0-0-16/229789/3 "2020-04-27T21:14:32Z")

</div>

For now I am using `0.0.0.0` and making sure there is a firewall active and blocking access to the outside world, but in the longer term, it'd be good to see the feature implemented without having to resort to reverse proxies.

---

<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:** [May 25, 2020, 9:14pm UTC](https://discuss.elastic.co/t/bind-kibanas-server-host-to-multiple-interfaces-both-localhost-and-192-168-0-0-16/229789/4 "2020-05-25T21:14:33Z")

</div>

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