# Install Issues

**URL:** <https://discuss.elastic.co/t/install-issues/67522>\
**Category:** Kibana\
**Created:** [November 29, 2016, 4:55pm UTC](https://discuss.elastic.co/t/install-issues/67522 "2016-11-29T16:55:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![CFDaddy](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@CFDaddy](https://discuss.elastic.co/u/CFDaddy)\
**Post date:** [November 29, 2016, 4:55pm UTC](https://discuss.elastic.co/t/install-issues/67522/1 "2016-11-29T16:55:23Z")

</div>

Just downloaded the most recent versions of Elasticsearch and Kibana (5.0.0), followed the install instructions and now can navigate to [http://localhost:5601](http://localhost:5601) and I see the Kibana interface. However, I get the following two issues in the Status Breakdown:  
D Status  
**ui settings Elasticsearch plugin is red**  
plugin\*\*:kibana@5.0.0\*\* Ready  
**plugin:elasticsearch@5.0.0 This version of Kibana requires Elasticsearch v5.0.0 on all nodes. I found the following incompatible nodes in your cluster: v1.7.1 @ inet[/127.0.0.1:9200] (169.254.165.214)**  
plugin:console@5.0.0 Ready  
plugin:timelion@5.0.0 Ready

The only issue I had with the instructions were that I could not get "sense" installed which after much searching in Google I found that I actually don't need it with the latest version of Kibana. Seems the install instructions are not complete and/or need some updating.

FYI, this is a brand new server install and I have never installed either of these products before so I'm not sure why Kibana is saying it see's a 1.7.1 version of Elasticsearch.

TIA,

Keith

---

<div class="post-metadata">

**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\
**Post date:** [December 1, 2016, 12:14am UTC](https://discuss.elastic.co/t/install-issues/67522/2 "2016-12-01T00:14:48Z")

</div>

What output do you get if you visit 127.0.0.1:9200 (or whatever the VM's IP is if this is a VM) in your browser?

---

<div class="post-metadata">

**Author:** ![CFDaddy](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@CFDaddy](https://discuss.elastic.co/u/CFDaddy)\
**Post date:** [December 1, 2016, 12:35am UTC](https://discuss.elastic.co/t/install-issues/67522/3 "2016-12-01T00:35:25Z")

</div>

I apologize for not responding earlier but I figured out the issue. So just in case anyone else stumbles upon this issue here is what happened.

The server in my lab I installed the Elastic stack on also has ColdFusion 2016 and the new ColdFusion API Manager. The API Manager uses Elasticsearch v1.7.1. So my inatll of Kibana was seeing the older version and alerting the errors. As this was just a development server I simply removed the API Manager install and Kibana was happy.

Thanks Matt for following up.

---

<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:** [December 29, 2016, 12:36am UTC](https://discuss.elastic.co/t/install-issues/67522/4 "2016-12-29T00:36:01Z")

</div>

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