# Kibana Errors

**URL:** <https://discuss.elastic.co/t/kibana-errors/84036>\
**Category:** Kibana\
**Created:** [April 28, 2017, 4:23pm UTC](https://discuss.elastic.co/t/kibana-errors/84036 "2017-04-28T16:23:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![urbans](https://avatars.discourse-cdn.com/v4/letter/u/ecae2f/32.png) [@urbans](https://discuss.elastic.co/u/urbans)\
**Post date:** [April 28, 2017, 4:23pm UTC](https://discuss.elastic.co/t/kibana-errors/84036/1 "2017-04-28T16:23:21Z")

</div>

Having issues with kibana.

I am new to Elastic Search and all. So not sure what to look for and such.

Any help would be appreciated.

FIRST ISSUE:

Status Breakdown  
ID Status  
ui settings Elasticsearch plugin is red  
plugin:kibana@5.3.0 Ready  
plugin:elasticsearch@5.3.0 Request Timeout after 30000ms  
plugin:console@5.3.0 Ready  
plugin:timelion@5.3.0 Ready

SECOND ISSUE (nothing loads, just this text):

Status: {{ ui.serverStateMessage }} {{ [ui.name](http://ui.name) }}  
Status Breakdown

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [April 28, 2017, 9:24pm UTC](https://discuss.elastic.co/t/kibana-errors/84036/2 "2017-04-28T21:24:16Z")

</div>

- What is the health status of Elasticsearch?
  - `GET /_cat/health?v`
  - [https://www.elastic.co/guide/en/elasticsearch/reference/5.3/cat-health.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.3/cat-health.html))

- Is the node configured as `elasticsearch.url` in the configuration reachable from the Kibana server machine?
  - Try hitting the `_cat/health` API in curl from the command line on the machine that runs Kibana

---

<div class="post-metadata">

**Author:** ![urbans](https://avatars.discourse-cdn.com/v4/letter/u/ecae2f/32.png) [@urbans](https://discuss.elastic.co/u/urbans)\
**Post date:** [May 1, 2017, 3:41pm UTC](https://discuss.elastic.co/t/kibana-errors/84036/3 "2017-05-01T15:41:36Z")

</div>

I run 3 node cluster.

ES runs on elk01 / elk02 / elk03  
Logstash runs on elk01  
Kibana runs on elk03

[root@elk03 ~]# curl -XGET 'localhost:9200/\_cat/health?v'  
epoch timestamp cluster status node.total node.data shards pri relo init unassign pending\_tasks max\_task\_wait\_time active\_shards\_percent  
1493653187 11:39:47 unicalogs\_us green 3 3 232 116 0 0 0 0 - 100.0%

Kibana just has to hit it via localhost.

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [May 2, 2017, 10:31pm UTC](https://discuss.elastic.co/t/kibana-errors/84036/4 "2017-05-02T22:31:46Z")

</div>

- What has changed between the "First Issue" and the "Second Issue"?
- Restart Kibana and watch the Kibana logs while it starts up. Any warnings or errors showing up?
- Are there any warnings or errors showing up in the Elasticsearch or Logstash logs?

---

<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 30, 2017, 10:38pm UTC](https://discuss.elastic.co/t/kibana-errors/84036/5 "2017-05-30T22:38:36Z")

</div>

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