# X-pack compatibility with ES and Kibana

**URL:** <https://discuss.elastic.co/t/x-pack-compatibility-with-es-and-kibana/80669>\
**Category:** Kibana\
**Created:** [March 30, 2017, 12:11pm UTC](https://discuss.elastic.co/t/x-pack-compatibility-with-es-and-kibana/80669 "2017-03-30T12:11:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lalitr](https://avatars.discourse-cdn.com/v4/letter/l/da6949/32.png) [@lalitr](https://discuss.elastic.co/u/lalitr)\
**Post date:** [March 30, 2017, 12:11pm UTC](https://discuss.elastic.co/t/x-pack-compatibility-with-es-and-kibana/80669/1 "2017-03-30T12:11:37Z")

</div>

Hi,

As per compatibility matrix here # [https://www.elastic.co/support/matrix#show\_compatibility](https://www.elastic.co/support/matrix#show_compatibility) i should be able to use something like below;  
Elasticsearch 5.1.1, Kibana 5.1.2 and X-pack 5.1.1.

But when we try to install x-pack 5.1.1 to Kibana 5.1.2 , the installation fails saying it requires exact match for the version. Which means we have to use same 5.1.1 version of all three products, is that correct ?

Thanks.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [March 30, 2017, 12:37pm UTC](https://discuss.elastic.co/t/x-pack-compatibility-with-es-and-kibana/80669/2 "2017-03-30T12:37:20Z")

</div>

Yes, that is correct.

---

<div class="post-metadata">

**Author:** ![lalitr](https://avatars.discourse-cdn.com/v4/letter/l/da6949/32.png) [@lalitr](https://discuss.elastic.co/u/lalitr)\
**Post date:** [March 30, 2017, 12:57pm UTC](https://discuss.elastic.co/t/x-pack-compatibility-with-es-and-kibana/80669/3 "2017-03-30T12:57:42Z")

</div>

Thanks for confirming - you want to get that reflected in the [https://www.elastic.co/support/matrix#show\_compatibility](https://www.elastic.co/support/matrix#show_compatibility), should people confuse .x with any version instead.

---

<div class="post-metadata">

**Author:** ![skearns](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skearns/32/125945_2.png) [@skearns](https://discuss.elastic.co/u/skearns)\
**Post date:** [March 30, 2017, 1:58pm UTC](https://discuss.elastic.co/t/x-pack-compatibility-with-es-and-kibana/80669/4 "2017-03-30T13:58:52Z")

</div>

There's slightly more to the story 🙂

As a best practice, if you can run the same version of all parts of the stack, that's ideal. If, for some reason, you cannot, then upgrade ES first.

Unless you are installing these plugins in an offline environment, simply running `bin/elasticsearch-plugin install x-pack` and `bin/kibana-plugin install x-pack` in the respective ES and Kibana home directories will download and install the proper x-pack versions.

If you're in an offline environment, ES requires plugins to be have version numbers that match the ES version, so if you have ES 5.1.1, you need x-pack 5.1.1. Kibana has the same rule, the Kibana plugin must match the Kibana version.

Finally, ES 5.1.x should work with Kibana 5.1.x. It's just that the plugins for each must exactly match.

---

<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:** [April 27, 2017, 1:58pm UTC](https://discuss.elastic.co/t/x-pack-compatibility-with-es-and-kibana/80669/5 "2017-04-27T13:58:58Z")

</div>

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