# Completely disable Kibana Timeout **URL:** \ **Category:** Kibana\ **Created:** [March 18, 2016, 12:46am UTC](https://discuss.elastic.co/t/completely-disable-kibana-timeout/44781 "2016-03-18T00:46:49Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Raggyman](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@Raggyman](https://discuss.elastic.co/u/Raggyman)\ **Post date:** [March 18, 2016, 12:46am UTC](https://discuss.elastic.co/t/completely-disable-kibana-timeout/44781/1 "2016-03-18T00:46:49Z")
We are running on not so good hardware (business choice.... why would monitoring be important?) , so am placed in a position where I want to increase the time out for Kibana. I am running 4.4.2 and for some reason it seems to ignore the timeout value when I increase it. One of the other annoying things, is when a query does time out, Kibana then throws the status page saying that a query took more than 30 seconds. Don't really care about that, because that query has been and gone, but then you can't actually do anything useful with Kibana for a while afterwards, as it wants you to know that a timeout has occurred. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [March 18, 2016, 2:17am UTC](https://discuss.elastic.co/t/completely-disable-kibana-timeout/44781/2 "2016-03-18T02:17:21Z")
You can't disable it without hacking the code. You can increase the timeout to some crazy number if you want, take a look at the options here - [https://www.elastic.co/guide/en/kibana/current/kibana-server-properties.html](https://www.elastic.co/guide/en/kibana/current/kibana-server-properties.html) ---
**Author:** ![Raggyman](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@Raggyman](https://discuss.elastic.co/u/Raggyman)\ **Post date:** [March 18, 2016, 3:06am UTC](https://discuss.elastic.co/t/completely-disable-kibana-timeout/44781/3 "2016-03-18T03:06:32Z")
I am setting `elasticsearch.requestTimeout: 900000` however in the kibana dashboard it still reports `plugin:elasticsearch Request Timeout after 30000ms` It just also seems that once it encounters a timeout error, you can't get it to do another search for a while. ---
**Author:** ![gh0stid](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@gh0stid](https://discuss.elastic.co/u/gh0stid)\ **Post date:** [August 5, 2016, 3:30pm UTC](https://discuss.elastic.co/t/completely-disable-kibana-timeout/44781/4 "2016-08-05T15:30:59Z")
im running in the same problem.. no solution at all ? ---
**Author:** ![Melpheos](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@Melpheos](https://discuss.elastic.co/u/Melpheos)\ **Post date:** [January 30, 2017, 1:50pm UTC](https://discuss.elastic.co/t/completely-disable-kibana-timeout/44781/5 "2017-01-30T13:50:43Z")
Same issue here. Despite changing the parameter is Kibana.yml file, the timeout stays at 30s ---
**Author:** ![JustinCrossman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/justincrossman/32/17322_2.png) [@JustinCrossman](https://discuss.elastic.co/u/JustinCrossman)\ **Post date:** [April 13, 2017, 5:17am UTC](https://discuss.elastic.co/t/completely-disable-kibana-timeout/44781/6 "2017-04-13T05:17:35Z")
Same issue here. I'm using a Bitnami ELK stack via AWS so perhaps it's more involved? E.g. there is an overriding config? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:32pm UTC](https://discuss.elastic.co/t/completely-disable-kibana-timeout/44781/7 "2017-07-06T13:32:17Z")