# Fatal Error -- Kibana: Unable to connect to Elasticsearch **URL:** \ **Category:** Kibana\ **Created:** [August 4, 2015, 6:33am UTC](https://discuss.elastic.co/t/fatal-error-kibana-unable-to-connect-to-elasticsearch/26777 "2015-08-04T06:33:24Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![syakirharis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/syakirharis/32/4011_2.png) [@syakirharis](https://discuss.elastic.co/u/syakirharis)\ **Post date:** [August 4, 2015, 6:33am UTC](https://discuss.elastic.co/t/fatal-error-kibana-unable-to-connect-to-elasticsearch/26777/1 "2015-08-04T06:33:24Z")
Please help me, i am new to this ELK ![](http://i.imgur.com/Chyfefe.png) ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [August 4, 2015, 6:50am UTC](https://discuss.elastic.co/t/fatal-error-kibana-unable-to-connect-to-elasticsearch/26777/2 "2015-08-04T06:50:50Z")
Is Elasticsearch running? On the same machine as Kibana? Did you change anything in your Kibana configuration? What if you visit [http://hostname:9200](http://hostname:9200) (where hostname is the machine where Elasticsearch should be running)? ---
**Author:** ![syakirharis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/syakirharis/32/4011_2.png) [@syakirharis](https://discuss.elastic.co/u/syakirharis)\ **Post date:** [August 4, 2015, 7:56am UTC](https://discuss.elastic.co/t/fatal-error-kibana-unable-to-connect-to-elasticsearch/26777/3 "2015-08-04T07:56:32Z")
elasticsearch is running.. ![](http://i.imgur.com/JHtezOp.png) I didn't change anything in Kibana configuration, but I do shutdown some nodes using kopf, then suddenly this thing happens, before that Kibana can't load any data from elasticsearch, now it shows that kind of message in my first post of this thread. ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [August 4, 2015, 7:58am UTC](https://discuss.elastic.co/t/fatal-error-kibana-unable-to-connect-to-elasticsearch/26777/4 "2015-08-04T07:58:19Z")
Next time, please copy/paste text when you can instead of posting screenshots. Sure, ES is running but with a 503 status. That's bad. Is there anything interesting in your ES logs that could explain what's going on? ---
**Author:** ![syakirharis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/syakirharis/32/4011_2.png) [@syakirharis](https://discuss.elastic.co/u/syakirharis)\ **Post date:** [August 4, 2015, 8:05am UTC](https://discuss.elastic.co/t/fatal-error-kibana-unable-to-connect-to-elasticsearch/26777/5 "2015-08-04T08:05:29Z")
I am clueless right now.. what should I do? 😭 Kibana: Unable to connect to Elasticsearch Error: Unable to connect to Elasticsearch Error: unknown error at respond ([http://103.18.3.245:5601/index.js?\_b=6004:81693:15](http://103.18.3.245:5601/index.js?_b=6004:81693:15)) at checkRespForFailure ([http://103.18.3.245:5601/index.js?\_b=6004:81659:7](http://103.18.3.245:5601/index.js?_b=6004:81659:7)) at [http://103.18.3.245:5601/index.js?\_b=6004:80322:7](http://103.18.3.245:5601/index.js?_b=6004:80322:7) at wrappedErrback ([http://103.18.3.245:5601/index.js?\_b=6004:20897:78](http://103.18.3.245:5601/index.js?_b=6004:20897:78)) at wrappedErrback ([http://103.18.3.245:5601/index.js?\_b=6004:20897:78](http://103.18.3.245:5601/index.js?_b=6004:20897:78)) at wrappedErrback ([http://103.18.3.245:5601/index.js?\_b=6004:20897:78](http://103.18.3.245:5601/index.js?_b=6004:20897:78)) at [http://103.18.3.245:5601/index.js?\_b=6004:21030:76](http://103.18.3.245:5601/index.js?_b=6004:21030:76) at Scope.$eval ([http://103.18.3.245:5601/index.js?\_b=6004:22017:28](http://103.18.3.245:5601/index.js?_b=6004:22017:28)) at Scope.$digest ([http://103.18.3.245:5601/index.js?\_b=6004:21829:31](http://103.18.3.245:5601/index.js?_b=6004:21829:31)) at Scope.$apply ([http://103.18.3.245:5601/index.js?\_b=6004:22121:24](http://103.18.3.245:5601/index.js?_b=6004:22121:24)) ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [August 4, 2015, 8:10am UTC](https://discuss.elastic.co/t/fatal-error-kibana-unable-to-connect-to-elasticsearch/26777/6 "2015-08-04T08:10:36Z")
Look in your Elasticsearch logs. They're typically stored in /var/log/elasticsearch. ---
**Author:** ![syakirharis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/syakirharis/32/4011_2.png) [@syakirharis](https://discuss.elastic.co/u/syakirharis)\ **Post date:** [August 4, 2015, 8:20am UTC](https://discuss.elastic.co/t/fatal-error-kibana-unable-to-connect-to-elasticsearch/26777/7 "2015-08-04T08:20:18Z")
> [@magnusbaeck](#): > > /var/log/elasticsearch [2015-06-27 00:36:32,193][DEBUG][http.netty] [esnode] Caught exception while handling client http traffic, closing connection [$ java.nio.channels.ClosedChannelException at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.cleanUpWriteBuffer(AbstractNioWorker.java:433) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.writeFromUserCode(AbstractNioWorker.java:128) at org.elasticsearch.common.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java$ at org.elasticsearch.common.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:36) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.ja$ at org.elasticsearch.common.netty.channel.Channels.write(Channels.java:725) at org.elasticsearch.common.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:71) at org.elasticsearch.common.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendDownstream(DefaultChannelPipeline.ja$ at org.elasticsearch.http.netty.pipelining.HttpPipeliningHandler.handleDownstream(HttpPipeliningHandler.java:87) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendDownstream(DefaultChannelPipeline.java:591) . . . [2015-06-27 14:09:31,695][DEBUG][cluster.service] [esnode] processing [zen-disco-receive(from master [[esnode1][EApdsfvGT-mqegUtMxp3uQ][dnslogger00][inet[/10.61.132.42:9300]]{master=true}])]: execute [2015-06-27 14:09:31,695][DEBUG][cluster.service] [esnode] cluster state updated, version [72], source [zen-disco-receive(from master [[esnode1][EApdsfvGT-mqegUtMxp3uQ][dnslogger00][inet[/10.61.132.42:9300]]{master=true}])] [2015-06-27 14:09:31,695][DEBUG][cluster.service] [esnode] set local cluster state to version 72 [2015-06-27 14:09:31,700][DEBUG][cluster.service] [esnode] processing [zen-disco-receive(from master [[esnode1][EApdsfvGT-mqegUtMxp3uQ][dnslogger00][inet[/10.61.132.42:9300]]{master=true}])]: done applying updated cluster\_state (version: 72) [2015-06-27 14:09:37,755][DEBUG][discovery.zen.publish] [esnode] received cluster state version 73 [2015-06-27 14:09:37,756][DEBUG][cluster.service] [esnode] processing [zen-disco-receive(from master [[esnode1][EApdsfvGT-mqegUtMxp3uQ][dnslogger00][inet[/10.61.132.42:9300]]{master=true}])]: execute [2015-06-27 14:09:37,756][DEBUG][cluster.service] [esnode] cluster state updated, version [73], source [zen-disco-receive(from master [[esnode1][EApdsfvGT-mqegUtMxp3uQ][dnslogger00][inet[/10.61.132.42:9300]]{master=true}])] [2015-06-27 14:09:37,756][DEBUG][cluster.service] [esnode] set local cluster state to version 73 [2015-06-27 14:09:37,761][DEBUG][cluster.service] [esnode] processing [zen-disco-receive(from master [[esnode1][EApdsfvGT-mqegUtMxp3uQ][dnslogger00][inet[/10.61.132.42:9300]]{master=true}])]: done applying updated cluster\_state (version: 73) [2015-06-27 14:57:19,690][INFO][node] [esnode] stopping ... [2015-06-27 14:57:19,710][DEBUG][discovery.zen.fd] [esnode] [master] stopping fault detection against master [[esnode1][EApdsfvGT-mqegUtMxp3uQ][dnslogger00][inet[/10.61.132.42:9300]]{master=true}], reason [zen disco stop] [2015-06-27 14:57:19,771][DEBUG][marvel.agent] [esnode] shutting down worker, exporting pending event [2015-06-27 14:57:19,771][DEBUG][marvel.agent] [esnode] worker shutdown [2015-06-27 14:57:19,772][INFO][node] [esnode] stopped [2015-06-27 14:57:19,772][INFO][node] [esnode] closing ... [2015-06-27 14:57:19,785][INFO][node] [esnode] closed ---
**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:** [August 4, 2015, 10:43pm UTC](https://discuss.elastic.co/t/fatal-error-kibana-unable-to-connect-to-elasticsearch/26777/8 "2015-08-04T22:43:30Z")
Why did you remove some nodes? ---
**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, 2:15pm UTC](https://discuss.elastic.co/t/fatal-error-kibana-unable-to-connect-to-elasticsearch/26777/9 "2017-07-06T14:15:21Z")