# Unable to revive connection: http://localhost:9200 **URL:** \ **Category:** Kibana\ **Created:** [November 19, 2019, 5:54am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435 "2019-11-19T05:54:25Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![pyerunka](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@pyerunka](https://discuss.elastic.co/u/pyerunka)\ **Post date:** [November 19, 2019, 5:54am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/1 "2019-11-19T05:54:25Z")
Hello, Can anyone help me in this?? Currently i have configured ES cluster. After that when i was trying to start kibana, it is giving me below mentioned error: > log [05:01:29.789] [warning][admin][elasticsearch] Unable to revive connection: [http://localhost:9200/](http://localhost:9200/) I am working on ES version 7.4.2. Regards, Priyanka ---
**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\ **Post date:** [November 19, 2019, 9:59am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/2 "2019-11-19T09:59:45Z")
Hi @pyerunka, To find the culprit a bit more information about your setup will be helpful. - Are you running Elasticsearch and Kibana on the same host? - Are you using docker? - Are you reaching Elasticsearch on the same host you are running Kibana on when using curl: `curl -v http://localhost:9200`? - Could you copy/paste your complete startup log? ---
**Author:** ![pyerunka](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@pyerunka](https://discuss.elastic.co/u/pyerunka)\ **Post date:** [November 19, 2019, 10:18am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/3 "2019-11-19T10:18:09Z")
Hello @flash1293, Thanks for your reply!!! 1. Yes, i am running ES and kibana on same host. 2. No i am not using docker. 3.Yes i can reach to ES on the same host where i am running kibana. 3. Please find below startup log: > log [10:05:38.802] [info][plugins-system] Setting up [4] plugins: [security,inspector,data,translations] > log [10:05:38.810] [info][plugins][security] Setting up plugin > log [10:05:38.813] [warning][config][plugins][security] Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidatedon restart, please set xpack.security.encryptionKey in kibana.yml > log [10:05:38.814] [warning][config][plugins][security] Session cookies willbe transmitted over insecure connections. This is not recommended. > log [10:05:38.909] [info][data][plugins] Setting up plugin > log [10:05:38.910] [info][plugins][translations] Setting up plugin > log [10:05:38.912] [info][plugins-system] Starting [3] plugins: [security,data,translations] > log [10:06:16.154] [info][status][plugin:kibana@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.161] [info][status][plugin:elasticsearch@7.4.2] Status changedfrom uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.164] [info][status][plugin:xpack\_main@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.174] [info][status][plugin:telemetry@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.176] [info][status][plugin:graph@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.187] [info][status][plugin:monitoring@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.192] [info][status][plugin:spaces@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.227] [info][status][plugin:security@7.4.2] Status changed fromuninitialized to green - Ready > log [10:06:16.230] [info][status][plugin:searchprofiler@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.234] [info][status][plugin:ml@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.285] [info][status][plugin:tilemap@7.4.2] Status changed fromuninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.288] [info][status][plugin:watcher@7.4.2] Status changed fromuninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.300] [info][status][plugin:grokdebugger@7.4.2] Status changedfrom uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.307] [info][status][plugin:dashboard\_mode@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.383] [info][status][plugin:interpreter@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.386] [info][status][plugin:tile\_map@7.4.2] Status changed fromuninitialized to green - Ready > log [10:06:16.390] [info][status][plugin:task\_manager@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.394] [info][status][plugin:maps@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.415] [info][status][plugin:canvas@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.421] [info][status][plugin:license\_management@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.424] [info][status][plugin:cloud@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.428] [info][status][plugin:index\_management@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.444] [info][status][plugin:console@7.4.2] Status changed fromuninitialized to green - Ready > log [10:06:16.451] [info][status][plugin:index\_lifecycle\_management@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.464] [info][status][plugin:metrics@7.4.2] Status changed fromuninitialized to green - Ready > log [10:06:16.501] [info][status][plugin:infra@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.505] [info][status][plugin:rollup@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.514] [info][siem] Plugin initializing > log [10:06:16.544] [info][siem] Plugin done initializing > log [10:06:16.547] [info][status][plugin:siem@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.553] [info][status][plugin:remote\_clusters@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.559] [info][status][plugin:cross\_cluster\_replication@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.581] [info][status][plugin:upgrade\_assistant@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.617] [info][status][plugin:uptime@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.622] [info][status][plugin:oss\_telemetry@7.4.2] Status changedfrom uninitialized to green - Ready > log [10:06:16.626] [info][status][plugin:file\_upload@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.631] [warning][encrypted\_saved\_objects] Generating a random key for xpack.encrypted\_saved\_objects.encryptionKey. To be able to decrypt encrypted saved objects attributes after restart, please set xpack.encrypted\_saved\_objects.encryptionKey in kibana.yml > log [10:06:16.634] [info][status][plugin:encrypted\_saved\_objects@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:16.650] [info][status][plugin:snapshot\_restore@7.4.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [10:06:16.664] [info][status][plugin:kibana\_react@7.4.2] Status changedfrom uninitialized to green - Ready > log [10:06:16.670] [info][status][plugin:region\_map@7.4.2] Status changed from uninitialized to green - Ready > log [10:06:17.990] [error][admin][elasticsearch] Request error, retrying HEAD [http://localhost:9200/.apm-agent-configuration](http://localhost:9200/.apm-agent-configuration) =\> connect ECONNREFUSED 127.0.0.1:9200 > log [10:06:18.090] [error][admin][elasticsearch] Request error, retrying GET [http://localhost:9200/\_nodes?filter\_path=nodes.\*.version%2Cnodes.\*.http.publish\_address%2Cnodes.\*.ip](http://localhost:9200/_nodes?filter_path=nodes.*.version%2Cnodes.*.http.publish_address%2Cnodes.*.ip) =\> connect ECONNREFUSED 127.0.0.1:9200 > log [10:06:19.183] [warning][admin][elasticsearch] Unable to revive connection: [http://localhost:9200/](http://localhost:9200/) > log [10:06:19.185] [warning][admin][elasticsearch] No living connections Could not create APM Agent configuration: No Living connections > log [10:06:19.188] [warning][admin][elasticsearch] Unable to revive connection: [http://localhost:9200/](http://localhost:9200/) > log [10:06:19.189] [warning][admin][elasticsearch] No living connections Regards, Priyanka ---
**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\ **Post date:** [November 19, 2019, 10:23am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/4 "2019-11-19T10:23:59Z")
Seems like Elasticsearch is not picking up the connection Kibana tries to initiate. Could you run `curl -v http://localhost:9200`and post the response? Besides that could you provide your `kibana.yml` and `elasticsearch.yml`? ---
**Author:** ![pyerunka](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@pyerunka](https://discuss.elastic.co/u/pyerunka)\ **Post date:** [November 19, 2019, 10:36am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/5 "2019-11-19T10:36:26Z")
Hello @flash1293, Thanks for reply!!! I tried for curl -v [http://localhost:9200](http://localhost:9200) > Rebuilt URL to: [http://localhost:9200/](http://localhost:9200/) > Hostname was NOT found in DNS cache > Trying _._._._ (I am hiding Ip address)... > Connected to Localhost (_._._._) port 9200 > GET / HTTP/1.1 > User-Agent: curl/7.37.0 > Host: Localhost:9200 > Accept: _/_ > HTTP/1.1 200 OK > content-type: application/json; charset=UTF-8 > content-length: 530 > > "name" : "Master-node", > "cluster\_name" : "InTouch", > "cluster\_uuid" : "gzXXocd1T7WVqeNeZrwLKw", > "version" : { > "number" : "7.4.2", > "build\_flavor" : "default", > "build\_type" : "zip", > "build\_hash" : "2f90bbf7b93631e52bafb59b3b049cb44ec25 > "build\_date" : "2019-10-28T20:40:44.881551Z", > "build\_snapshot" : false, > "lucene\_version" : "8.2.0", > "minimum\_wire\_compatibility\_version" : "6.8.0", > "minimum\_index\_compatibility\_version" : "6.0.0-beta1" > }, > "tagline" : "You Know, for Search" And i have not updated anything in kibana.yml file. Means that file is as it is when we download kibana from [Elastic.co](http://Elastic.co). Please find Elasticsearch.yml file: > cluster.name: InTouch > cluster.remote.connect: false > network.host: [abcd.com](http://abcd.com) > transport.host: [abcd.com](http://abcd.com) > transport.tcp.port: 9300-9400 > node.name: Master-node > discovery.zen.minimum\_master\_nodes: 1 > node.master: true > node.data: false > node.ingest: true > discovery.zen.ping.unicast.hosts: [[abcd.com](http://abcd.com), [xyz.com](http://xyz.com)] > cluster.initial\_master\_nodes: ["Master-node"] > bootstrap.memory\_lock: true Regards, Priyanka ---
**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\ **Post date:** [November 19, 2019, 10:55am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/6 "2019-11-19T10:55:01Z")
Hm, maybe the `network.host: abcd.com` setting prevents Elasticsearch to bind the local loopback address. In the debug output from curl you see that curl is translating `localhost` into something else than `127.0.0.1`, but Kibana apparently can't do this lookup (probably due to host aliases or something like that). There are probably two ways to resolve this - either use the same host name for your elasticsearch cluster as curl or other consumers (the ip curl used or `abcd.com`) - or explicitly also bind Elasticsearch to the loopback interface in addition to the public one. You should be able to do this by setting `network.bind_host` to `_local_ ` and `abcd.com` and `network.publish_host` to `abcd.com` instead of setting `network.host` [https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html#advanced-network-settings](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html#advanced-network-settings) Let me know whether that helps ---
**Author:** ![pyerunka](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@pyerunka](https://discuss.elastic.co/u/pyerunka)\ **Post date:** [November 19, 2019, 11:00am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/7 "2019-11-19T11:00:04Z")
Hello @flash1293, I am purposely changed network.host to [abcd.com](http://abcd.com). I do not want to showcase it as security concerns. I am using host name same as elasticsearch cluster as curl. Regards, Priyanka ---
**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\ **Post date:** [November 19, 2019, 11:04am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/8 "2019-11-19T11:04:59Z")
All right, let me know when you run into further problems. ---
**Author:** ![pyerunka](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@pyerunka](https://discuss.elastic.co/u/pyerunka)\ **Post date:** [November 20, 2019, 9:24am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/9 "2019-11-20T09:24:51Z")
Hello @flash1293, Thanks for your great help!!! My issue has been resolved. I am able to start kibana. I changed `network.bind_host` to `_local_` and `network.publish_host` to `abcd.com` instead of setting `network.host`as mentioned in above comment. Regards, Priyanka ---
**Author:** ![pyerunka](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@pyerunka](https://discuss.elastic.co/u/pyerunka)\ **Post date:** [November 21, 2019, 10:02am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/10 "2019-11-21T10:02:25Z")
Hello @flash1293, This issue is resolved on my master node. I am not able to start kibana on my data node also. I am getting same error as i have mentioned in earlier comments. Can you help me in this? Regards, Priyanka ---
**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\ **Post date:** [December 3, 2019, 11:13am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/11 "2019-12-03T11:13:48Z")
You can try to add `_site_` instead of `_local_` to the list of hosts. Then hosts in the same local network should also be able to connect ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 31, 2019, 11:26am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200/208435/12 "2019-12-31T11:26:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.