# Kibana Red timeout on healthy cluster **URL:** \ **Category:** Kibana\ **Created:** [May 28, 2018, 9:49pm UTC](https://discuss.elastic.co/t/kibana-red-timeout-on-healthy-cluster/133587 "2018-05-28T21:49:04Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\ **Post date:** [May 28, 2018, 9:49pm UTC](https://discuss.elastic.co/t/kibana-red-timeout-on-healthy-cluster/133587/1 "2018-05-28T21:49:05Z")
Hi running Kibana 6.2.4 Kibana was working fine and now I'm getting. plugin:elasticsearch@6.2.4 Request Timeout after 30000ms The cluster is 100% healthy. I also have another window open of the same Kibana UI but I have not refreshed the browser yet and I can see my dashboard executing just fine. ---
**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\ **Post date:** [May 28, 2018, 10:03pm UTC](https://discuss.elastic.co/t/kibana-red-timeout-on-healthy-cluster/133587/2 "2018-05-28T22:03:05Z")
Everything seems to go green except the elasticsearch plugin? ``` {"type":"log","@timestamp":"2018-05-28T21:43:55Z","tags":["status","plugin:elasticsearch@6.2.4","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"} ... {"type":"log","@timestamp":"2018-05-28T21:44:07Z","tags":["reporting","warning"],"pid":1,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml"} ... {"type":"log","@timestamp":"2018-05-28T21:44:37Z","tags":["status","plugin:elasticsearch@6.2.4","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - Request Timeout after 30000ms","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2018-05-28T21:44:38Z","tags":["license","info","xpack"],"pid":1,"message":"Imported license information from Elasticsearch for the [data] cluster: mode: basic | status: active | expiry date: 2019-05-22T23:59:59+00:00"} {"type":"log","@timestamp":"2018-05-28T21:44:38Z","tags":["status","plugin:xpack_main@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Request Timeout after 30000ms"} {"type":"log","@timestamp":"2018-05-28T21:44:38Z","tags":["status","plugin:searchprofiler@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Request Timeout after 30000ms"} {"type":"log","@timestamp":"2018-05-28T21:44:38Z","tags":["status","plugin:ml@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Request Timeout after 30000ms"} {"type":"log","@timestamp":"2018-05-28T21:44:38Z","tags":["status","plugin:tilemap@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Request Timeout after 30000ms"} {"type":"log","@timestamp":"2018-05-28T21:44:38Z","tags":["status","plugin:watcher@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Request Timeout after 30000ms"} {"type":"log","@timestamp":"2018-05-28T21:44:38Z","tags":["status","plugin:graph@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Request Timeout after 30000ms"} {"type":"log","@timestamp":"2018-05-28T21:44:38Z","tags":["status","plugin:reporting@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Request Timeout after 30000ms"} {"type":"log","@timestamp":"2018-05-28T21:44:38Z","tags":["info","monitoring-ui","kibana-monitoring"],"pid":1,"message":"Stopping all Kibana monitoring collectors"} {"type":"log","@timestamp":"2018-05-28T21:44:40Z","tags":["license","info","xpack"],"pid":1,"message":"Imported license information from Elasticsearch for the [monitoring] cluster: mode: basic | status: active | expiry date: 2019-05-22T23:59:59+00:00"} {"type":"log","@timestamp":"2018-05-28T21:45:04Z","tags":["status","plugin:security@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2018-05-28T21:45:04Z","tags":["security","warning"],"pid":1,"message":"Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml"} ... {"type":"log","@timestamp":"2018-05-28T21:45:04Z","tags":["status","plugin:grokdebugger@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2018-05-28T21:45:04Z","tags":["status","plugin:dashboard_mode@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2018-05-28T21:45:04Z","tags":["status","plugin:logstash@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2018-05-28T21:45:04Z","tags":["status","plugin:apm@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2018-05-28T21:45:04Z","tags":["status","plugin:console@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2018-05-28T21:45:04Z","tags":["status","plugin:metrics@6.2.4","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2018-05-28T21:45:04Z","tags":["listening","info"],"pid":1,"message":"Server running at http://0:5601"} ``` ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [May 29, 2018, 10:40pm UTC](https://discuss.elastic.co/t/kibana-red-timeout-on-healthy-cluster/133587/3 "2018-05-29T22:40:05Z")
It's timing out when reaching out to Elasticsearch for it's health check. This is usually do to network issues or a cluster which can not respond in a timely manner (30 seconds)/ ---
**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\ **Post date:** [May 30, 2018, 1:52am UTC](https://discuss.elastic.co/t/kibana-red-timeout-on-healthy-cluster/133587/4 "2018-05-30T01:52:38Z")
Cluster seemed healthy and \_cat/health was instant ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [May 31, 2018, 2:24am UTC](https://discuss.elastic.co/t/kibana-red-timeout-on-healthy-cluster/133587/5 "2018-05-31T02:24:52Z")
> [@javadevmtl](#): > > [http://0:5601](http://0:5601)" this is ok? ---
**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\ **Post date:** [May 31, 2018, 12:51pm UTC](https://discuss.elastic.co/t/kibana-red-timeout-on-healthy-cluster/133587/6 "2018-05-31T12:51:46Z")
What check does Kibana run? If \_cat/health was 100% and green what else would cause this? ---
**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\ **Post date:** [June 4, 2018, 3:20pm UTC](https://discuss.elastic.co/t/kibana-red-timeout-on-healthy-cluster/133587/7 "2018-06-04T15:20:41Z")
Is Elasticsearch and Kibana on separate machines? This might be a networking issue. Here is the health check which is ran: [https://github.com/elastic/kibana/blob/master/src/core\_plugins/elasticsearch/lib/health\_check.js](https://github.com/elastic/kibana/blob/master/src/core_plugins/elasticsearch/lib/health_check.js) Mostly it's similar to the following requests: `curl -X HEAD http://localhost:9200/` `curl http://localhost:9200/_nodes/info` ---
**Author:** ![javadevmtl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javadevmtl/32/45613_2.png) [@javadevmtl](https://discuss.elastic.co/u/javadevmtl)\ **Post date:** [June 4, 2018, 4:10pm UTC](https://discuss.elastic.co/t/kibana-red-timeout-on-healthy-cluster/133587/8 "2018-06-04T16:10:13Z")
Yes, they are. Ok I'll keep that in mind next time it happens. Thanks ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 2, 2018, 4:10pm UTC](https://discuss.elastic.co/t/kibana-red-timeout-on-healthy-cluster/133587/9 "2018-07-02T16:10:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.