# Kibana 6.4.0 showing unexpected page

**URL:** <https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/179329>\
**Category:** Kibana\
**Created:** [May 2, 2019, 9:47am UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/179329 "2019-05-02T09:47:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![shiveshabhishek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shiveshabhishek/32/34533_2.png) [@shiveshabhishek](https://discuss.elastic.co/u/shiveshabhishek)\
**Post date:** [May 2, 2019, 9:47am UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/179329/1 "2019-05-02T09:47:23Z")

</div>

Hey all, I am running Kibana with elasticsearch 6.4. And suddenly I've started seeing this page:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/a/3a23be94aaf841498636e67a2d8c0966f9bebb62.png)  
Why is it getting shown in my default landing page and how to get rid of this?

---

<div class="post-metadata">

**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 2, 2019, 5:45pm UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/179329/2 "2019-05-02T17:45:03Z")

</div>

If a plugin goes into the red status, the status page will be shown. The most common case for that is the elasticsearch plugin times out when communicating with the cluster. When it first redirects to this page, is any plugin red, if so, what is the status? There should also be something in the Kibana logs

---

<div class="post-metadata">

**Author:** ![shiveshabhishek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shiveshabhishek/32/34533_2.png) [@shiveshabhishek](https://discuss.elastic.co/u/shiveshabhishek)\
**Post date:** [May 3, 2019, 7:08am UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/179329/3 "2019-05-03T07:08:29Z")

</div>

Hey @tylersmalley thanks for quick response!  
I looked into Kibana logs and found this :

`{"type":"log","@timestamp":"2019-05-03T06:48:58Z","tags":["status","plugin:elasticsearch@6.4.0-SNAPSHOT","error"],"pid":1,"state":"red","message":"Status changed from green to red - Request Timeout after 3000ms","prevState":"green","prevMsg":"Ready"}`  
Is it because of the above error log?

---

<div class="post-metadata">

**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 3, 2019, 2:11pm UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/179329/4 "2019-05-03T14:11:28Z")

</div>

Yup, that would do it. We're calling `_nodes/info` and it's taking more than 3 seconds to respond. This might be due to an increased ES or network load at this time, which should be addressed. But this timeout can also be increased.

This is set using the `elasticsearch.requestTimeout` option in the `kibana.yml`. My guess is this setting is already changed, as by default it's set to 30 seconds.

[https://www.elastic.co/guide/en/kibana/6.4/settings.html](https://www.elastic.co/guide/en/kibana/6.4/settings.html)

---

<div class="post-metadata">

**Author:** ![shiveshabhishek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shiveshabhishek/32/34533_2.png) [@shiveshabhishek](https://discuss.elastic.co/u/shiveshabhishek)\
**Post date:** [May 18, 2019, 4:16am UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/179329/5 "2019-05-18T04:16:49Z")

</div>

Thanks for the info @tylersmalley , But still, in logs I am getting `3000ms` (haven't changed anything in `kibana.yml` for increasing this value yet). I don't think that the default is set to `30000ms` . And one more thing.. My kibana is flooded with these logs 🙄:

```auto
{"type":"log","@timestamp":"2019-05-18T04:14:05Z","tags":["status","plugin:elasticsearch@6.4.0-SNAPSHOT","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Request Timeout after 3000ms"}
{"type":"log","@timestamp":"2019-05-18T04:14:18Z","tags":["status","plugin:elasticsearch@6.4.0-SNAPSHOT","error"],"pid":1,"state":"red","message":"Status changed from green to red - Request Timeout after 3000ms","prevState":"green","prevMsg":"Ready"}
{"type":"log","@timestamp":"2019-05-18T04:14:26Z","tags":["status","plugin:elasticsearch@6.4.0-SNAPSHOT","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Request Timeout after 3000ms"}
{"type":"log","@timestamp":"2019-05-18T04:14:37Z","tags":["status","plugin:elasticsearch@6.4.0-SNAPSHOT","error"],"pid":1,"state":"red","message":"Status changed from green to red - Request Timeout after 3000ms","prevState":"green","prevMsg":"Ready"}
{"type":"log","@timestamp":"2019-05-18T04:14:40Z","tags":["status","plugin:elasticsearch@6.4.0-SNAPSHOT","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Request Timeout after 3000ms"}
{"type":"log","@timestamp":"2019-05-18T04:14:51Z","tags":["status","plugin:elasticsearch@6.4.0-SNAPSHOT","error"],"pid":1,"state":"red","message":"Status changed from green to red - Request Timeout after 3000ms","prevState":"green","prevMsg":"Ready"}
{"type":"log","@timestamp":"2019-05-18T04:14:56Z","tags":["status","plugin:elasticsearch@6.4.0-SNAPSHOT","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Request Timeout after 3000ms"}

```

---

<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:** [June 15, 2019, 4:16am UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/179329/6 "2019-06-15T04:16:50Z")

</div>

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