# Kibana-6-4-0-showing-unexpected-page **URL:** \ **Category:** Kibana\ **Created:** [August 23, 2019, 5:46am UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/196448 "2019-08-23T05:46:35Z")\ **Posts on this page:** 5\ **Page:** 1
**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:** [August 23, 2019, 5:46am UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/196448/1 "2019-08-23T05:46:36Z")
This is with reference to the existing issue I've posted earlier([Kibana 6.4.0 showing unexpected page](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/179329)). I did not get the solution yet so asking for the same. By any chance, can this setting be updated and really get reflected in the configuration/log? ---
**Author:** ![christophilus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christophilus/32/42991_2.png) [@christophilus](https://discuss.elastic.co/u/christophilus)\ **Post date:** [August 23, 2019, 3:36pm UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/196448/2 "2019-08-23T15:36:57Z")
I agree with Tyler's answer to the original question. The page is showing because of the timeout. The thing to do is to either increase the timeout (via config) or to figure out why the requests are so slow in the first place (likely culprits are network issues or insufficient resources in your Elastic cluster). ---
**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:** [August 23, 2019, 9:18pm UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/196448/3 "2019-08-23T21:18:37Z")
Hi @christophilus, thanks for looking into this. In my case, even if change the value of **elasticsearch.request\_timeout** to _60000_, the log is showing me , **Request timeout after 3000ms**. If I am not wrong , log should display the provided value? ---
**Author:** ![christophilus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christophilus/32/42991_2.png) [@christophilus](https://discuss.elastic.co/u/christophilus)\ **Post date:** [August 26, 2019, 3:24pm UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/196448/4 "2019-08-26T15:24:50Z")
This tells me the problem is not with Kibana, but somewhere in your network configuration. If you search the forums, you'll find others who had this problem ended up having to adjust their network settings. For example, here's an example where the MTUs were misconfigured: > [@ES Request Timeout after 30000ms](https://discuss.elastic.co/t/es-request-timeout-after-30000ms/38250): > > I've seem to have lost connection from kibana 4.3 to ES 2.1 while idling over xmas, wondering how to resolve this as ES says: [root@d1r1n1 ~]# curl -XGET "http://`hostname`:9200/\_cluster/health?pretty" { "cluster\_name" : "mxes\_data", "status" : "green", "timed\_out" : false, "number\_of\_nodes" : 14, "number\_of\_data\_nodes" : 14, "active\_primary\_shards" : 141, "active\_shards" : 282, "relocating\_shards" : 0, "initializing\_shards" : 0, "unassigned\_shards" : 0, "delayed\_unassigne… ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 23, 2019, 3:26pm UTC](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/196448/5 "2019-09-23T15:26:09Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.