# 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:** 1\ **Showing post:** 4
**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… --- _[View the full topic](https://discuss.elastic.co/t/kibana-6-4-0-showing-unexpected-page/196448)._