# Facing some issue building kibana **URL:** \ **Category:** Kibana\ **Created:** [August 21, 2017, 10:49am UTC](https://discuss.elastic.co/t/facing-some-issue-building-kibana/97751 "2017-08-21T10:49:19Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [August 21, 2017, 10:49am UTC](https://discuss.elastic.co/t/facing-some-issue-building-kibana/97751/1 "2017-08-21T10:49:19Z")
Hi , I am getting the following error messages on Kibana log: og [10:47:37.026] [warning][admin][elasticsearch] Unable to revive connection: [http://localhost:9229/](http://localhost:9229/) log [10:47:37.026] [warning][admin][elasticsearch] No living connections log [10:47:39.533] [warning][admin][elasticsearch] Unable to revive connection: [http://localhost:9229/](http://localhost:9229/) log [10:47:39.533] [warning][admin][elasticsearch] No living connections log [10:47:39.534] [warning][admin][elasticsearch] Unable to revive connection: [http://localhost:9229/](http://localhost:9229/) log [10:47:39.534] [warning][admin][elasticsearch] No living connections log [10:47:42.085] [warning][admin][elasticsearch] Unable to revive connection: [http://localhost:9229/](http://localhost:9229/) log [10:47:42.085] [warning][admin][elasticsearch] No living connections log [10:47:42.124] [warning][admin][elasticsearch] Unable to revive connection: [http://localhost:9229/](http://localhost:9229/) And on Kibana Dashboard it says: Status Breakdown ID Status ui settings Elasticsearch plugin is red plugin:kibana@5.5.1 Ready plugin:elasticsearch@5.5.1 Unable to connect to Elasticsearch at [http://localhost:9229](http://localhost:9229). plugin:xpack\_main@5.5.1 Unable to connect to Elasticsearch at [http://localhost:9229](http://localhost:9229). plugin:monitoring@5.5.1 Ready plugin:searchprofiler@5.5.1 Unable to connect to Elasticsearch at [http://localhost:9229](http://localhost:9229). plugin:ml@5.5.1 No Living connections plugin:tilemap@5.5.1 Unable to connect to Elasticsearch at [http://localhost:9229](http://localhost:9229). plugin:watcher@5.5.1 Unable to connect to Elasticsearch at [http://localhost:9229](http://localhost:9229). plugin:grokdebugger@5.5.1 Ready plugin:console@5.5.1 Ready plugin:metrics@5.5.1 Ready plugin:timelion@5.5.1 Ready ---
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [August 21, 2017, 10:50am UTC](https://discuss.elastic.co/t/facing-some-issue-building-kibana/97751/2 "2017-08-21T10:50:01Z")
I am using version 5.5.1 for both Elasticsearch and Kibana ---
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [August 21, 2017, 10:57am UTC](https://discuss.elastic.co/t/facing-some-issue-building-kibana/97751/3 "2017-08-21T10:57:48Z")
![kibana1](https://us1.discourse-cdn.com/elastic/original/3X/1/b/1b74cdc459923500ab3572cccd45d221a3f3902c.PNG) ---
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [August 21, 2017, 11:05am UTC](https://discuss.elastic.co/t/facing-some-issue-building-kibana/97751/4 "2017-08-21T11:05:20Z")
Here is my yml file: elasticsearch.yml ```auto xpack.security.enabled: false xpack.graph.enabled: false xpack.watcher.enabled: false ``` kibana.yml ```auto pack.security.enabled: false xpack.graph.enabled: false xpack.reporting.enabled: false elasticsearch.url: "http://localhost:9229" # connects to the proxy in front of elasticsearch elasticsearch.username: "elastic" elasticsearch.password: "password-for-proxy-in-front-of-elasticsearch" server.host: "localhost" ``` If I replace 9229 port with 9200 in kibana.yml. I new error appearing 🙂 Access Denied You are not authorized to access Monitoring. To use Monitoring, you need the privileges granted by both the `kibana_user` and `monitoring_user` roles. If you are attempting to access a dedicated monitoring cluster, this might be because you are logged in as a user that is not configured on the monitoring cluster. ---
**Author:** ![cjcenizal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cjcenizal/32/11216_2.png) [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)\ **Post date:** [August 21, 2017, 6:33pm UTC](https://discuss.elastic.co/t/facing-some-issue-building-kibana/97751/5 "2017-08-21T18:33:44Z")
Hmm, OK! I think we can figure this out. First, it seems like when Kibana's server is trying to connect to Elasticsearch, the proxy is failing to forward from port 9229 to Elasticsearch's port behind the proxy (9200). Are you connecting to Kibana directly, i.e. on localhost:5601? If so, can you try putting Kibana behind the proxy as well, and changing the config in kibana.yml to `elasticsearch.url: "http://localhost:9200"`? Thanks, CJ ---
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [August 22, 2017, 3:24am UTC](https://discuss.elastic.co/t/facing-some-issue-building-kibana/97751/6 "2017-08-22T03:24:49Z")
Many Thanks !! It works. One more question for you 🙂 On monitoring tab on Kibana , Elasticsearch "Health" status is yellow . Any idea what's wrong here , ideally it should be green. **Kibana log says:** log [03:13:44.197] [info][status][plugin:xpack\_main@5.5.1] Status changed fr om yellow to green - Ready log [03:13:44.199] [info][status][plugin:searchprofiler@5.5.1] Status change d from yellow to green - Ready log [03:13:44.200] [info][status][plugin:tilemap@5.5.1] Status changed from yellow to green - Ready log [03:13:44.203] [info][status][plugin:watcher@5.5.1] Status changed from yellow to green - Ready log [03:13:44.210] [info][status][plugin:timelion@5.5.1] Status changed from uninitialized to green - Ready log [03:13:44.241] [info][license][xpack] Imported license information from Elasticsearch for [monitoring] cluster: mode: trial | status: active | expiry da te: 2017-09-17T15:05:17+05:30 log [03:13:44.242] [info][listening] Server running at [http://localhost:5601](http://localhost:5601) log [03:13:44.247] [info][status][ui settings] Status changed from uninitial ized to green - Ready log [03:13:44.252] [info][status][plugin:monitoring@5.5.1] Status changed fr om green to yellow - Waiting for Monitoring Health Check log [03:13:44.339] [info][status][plugin:monitoring@5.5.1] Status changed fr om yellow to green - Ready **Elastisearch Log says:** [2017-08-22T08:51:32,105][INFO][o.e.c.r.a.DiskThresholdMonitor] [Wm-GSOZ] low d isk watermark [85%] exceeded on [Wm-GSOZ9QAi-DGOTTPy2aA][Wm-GSOZ][/servers/scrat ch03/niraj/ELK/elasticsearch-5.5.1/data/nodes/0] free: 1.4tb[14.3%], replicas wi ll not be assigned to this node [2017-08-22T08:52:02,202][INFO][o.e.c.r.a.DiskThresholdMonitor] [Wm-GSOZ] low d isk watermark [85%] exceeded on [Wm-GSOZ9QAi-DGOTTPy2aA][Wm-GSOZ][/servers/scrat ch03/niraj/ELK/elasticsearch-5.5.1/data/nodes/0] free: 1.4tb[14.3%], replicas wi ll not be assigned to this node [2017-08-22T08:52:32,472][INFO][o.e.c.r.a.DiskThresholdMonitor] [Wm-GSOZ] low d isk watermark [85%] exceeded on [Wm-GSOZ9QAi-DGOTTPy2aA][Wm-GSOZ][/servers/scrat ch03/niraj/ELK/elasticsearch-5.5.1/data/nodes/0] free: 1.4tb[14.3%], replicas wi ll not be assigned to this node [2017-08-22T08:53:02,572][INFO][o.e.c.r.a.DiskThresholdMonitor] [Wm-GSOZ] low d isk watermark [85%] exceeded on [Wm-GSOZ9QAi-DGOTTPy2aA][Wm-GSOZ][/servers/scrat ch03/niraj/ELK/elasticsearch-5.5.1/data/nodes/0] free: 1.4tb[14.3%], replicas wi ll not be assigned to this node ---
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [August 22, 2017, 4:18am UTC](https://discuss.elastic.co/t/facing-some-issue-building-kibana/97751/7 "2017-08-22T04:18:45Z")
Got the answer for this. Please ignore. ---
**Author:** ![niraj\_pandey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niraj_pandey/32/44034_2.png) [@niraj\_pandey](https://discuss.elastic.co/u/niraj_pandey)\ **Post date:** [August 22, 2017, 4:45am UTC](https://discuss.elastic.co/t/facing-some-issue-building-kibana/97751/8 "2017-08-22T04:45:38Z")
Can you let me know the procudure to change the default threshold limit from 85% to 90%. Thanks Niraj ---
**Author:** ![cjcenizal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cjcenizal/32/11216_2.png) [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)\ **Post date:** [August 22, 2017, 6:52pm UTC](https://discuss.elastic.co/t/facing-some-issue-building-kibana/97751/9 "2017-08-22T18:52:27Z")
From [the docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/disk-allocator.html), it looks like you can customize these settings with a query like this: ```auto PUT _cluster/settings { "persisten": { "cluster.routing.allocation.disk.watermark.low": "80%", "cluster.routing.allocation.disk.watermark.high": "50gb", "cluster.info.update.interval": "1m" } } ``` See [Cluster update settings docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-update-settings.html) for more information on "persistent" vs "transient" settings. Thanks, CJ ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 19, 2017, 6:52pm UTC](https://discuss.elastic.co/t/facing-some-issue-building-kibana/97751/10 "2017-09-19T18:52:31Z")
Closed on September 19, 2017, 6:52pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.