# Why coordinator node and kibana server must be on the same host

**URL:** <https://discuss.elastic.co/t/why-coordinator-node-and-kibana-server-must-be-on-the-same-host/128481>\
**Category:** Elasticsearch\
**Created:** [April 18, 2018, 8:25am UTC](https://discuss.elastic.co/t/why-coordinator-node-and-kibana-server-must-be-on-the-same-host/128481 "2018-04-18T08:25:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![makibroshett](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/makibroshett/32/106322_2.png) [@makibroshett](https://discuss.elastic.co/u/makibroshett)\
**Post date:** [April 18, 2018, 8:25am UTC](https://discuss.elastic.co/t/why-coordinator-node-and-kibana-server-must-be-on-the-same-host/128481/1 "2018-04-18T08:25:10Z")

</div>

Hi,

In the docs, and various examples found on the web, it is mentionned that both the Kibana server and coordinating ES instance should be on the same host. Is it in order to save an actual round-trip between the two kibana and the ES coordinator, or are there stronger reasons than this ?

Thanks for your help,

Olivier

---

<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 16, 2018, 8:25am UTC](https://discuss.elastic.co/t/why-coordinator-node-and-kibana-server-must-be-on-the-same-host/128481/2 "2018-05-16T08:25:16Z")

</div>

Closed on May 16, 2018, 8:25am UTC

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