# "Unable to revive connection: http://localhost:9200/" & No living connections

**URL:** <https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200-no-living-connections/170086>\
**Category:** Kibana\
**Created:** [February 27, 2019, 1:39am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200-no-living-connections/170086 "2019-02-27T01:39:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mugdha](https://avatars.discourse-cdn.com/v4/letter/m/df705f/32.png) [@mugdha](https://discuss.elastic.co/u/mugdha)\
**Post date:** [February 27, 2019, 1:39am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200-no-living-connections/170086/1 "2019-02-27T01:39:08Z")

</div>

I created DNS entries in route 53 for my elasticsearch data machines and after that i was observing this in my kibana status:

```
Feb 27 01:25:02 elasticsearch-client-node-2 kibana[1026]: {"type":"log","@timestamp":"2019-02-27T01:25:02Z","tags":["warning","elasticsearch","admin"],"pid":1026,"message":"Unable to revive connection: http://localhost:9200/"}
Feb 27 01:25:02 elasticsearch-client-node-2 kibana[1026]: {"type":"log","@timestamp":"2019-02-27T01:25:02Z","tags":["warning","elasticsearch","admin"],"pid":1026,"message":"No living connections"}

```

I have commented elasticsearch.hosts in kibana .yml.  
also:  
curl -i [http://localhost:5601](http://localhost:5601)  
HTTP/1.1 503 Service Unavailable  
retry-after: 30  
content-type: text/html; charset=utf-8  
cache-control: no-cache  
content-length: 30  
Date: Wed, 27 Feb 2019 01:47:57 GMT  
Connection: keep-alive

Please help

---

<div class="post-metadata">

**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\
**Post date:** [February 27, 2019, 2:26pm UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200-no-living-connections/170086/2 "2019-02-27T14:26:03Z")

</div>

`elasticsearch.hosts` should point to the network location of the elasticsearch deployment. What is that configuration right now in the `kibana.yml`? It defaults to `localhost:9200`. Change in the .yml also require a restart of Kibana.

---

<div class="post-metadata">

**Author:** ![mugdha](https://avatars.discourse-cdn.com/v4/letter/m/df705f/32.png) [@mugdha](https://discuss.elastic.co/u/mugdha)\
**Post date:** [February 28, 2019, 2:29am UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200-no-living-connections/170086/3 "2019-02-28T02:29:43Z")

</div>

i have my instances on GCP and I created route 53 entries (data-nodes) for logstash pipeline so pore 9200 is unavailable.

what am I missing here?

---

<div class="post-metadata">

**Author:** ![mugdha](https://avatars.discourse-cdn.com/v4/letter/m/df705f/32.png) [@mugdha](https://discuss.elastic.co/u/mugdha)\
**Post date:** [February 28, 2019, 8:44pm UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200-no-living-connections/170086/4 "2019-02-28T20:44:30Z")

</div>

```
# Kibana is served by a back end server. This setting specifies the port to use.
#server.port: 5601

# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
# The default is 'localhost', which usually means remote machines will not be able to connect.
# To allow connections from remote users, set this parameter to a non-loopback address.
#server.host: "localhost"

# Enables you to specify a path to mount Kibana at if you are running behind a proxy.
# Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath
# from requests it receives, and to prevent a deprecation warning at startup.
# This setting cannot end in a slash.
#server.basePath: ""

# Specifies whether Kibana should rewrite requests that are prefixed with
# `server.basePath` or require that they are rewritten by your reverse proxy.
# This setting was effectively always `false` before Kibana 6.3 and will
# default to `true` starting in Kibana 7.0.
#server.rewriteBasePath: false

# The maximum payload size in bytes for incoming server requests.
#server.maxPayloadBytes: 1048576

# The Kibana server's name. This is used for display purposes.
#server.name: "your-hostname"

# The URLs of the Elasticsearch instances to use for all your queries.
elasticsearch.hosts: ["http://localhost:9200"]

# When this setting's value is true Kibana uses the hostname specified in the server.host
# setting. When the value of this setting is false, Kibana uses the hostname of the host
# that connects to this Kibana instance.
#elasticsearch.preserveHost: true

# Kibana uses an index in Elasticsearch to store saved searches, visualizations and
# dashboards. Kibana creates a new index if the index doesn't already exist.
#kibana.index: ".kibana"

# The default application to load.
#kibana.defaultAppId: "home"

# If your Elasticsearch is protected with basic authentication, these settings provide
# the username and password that the Kibana server uses to perform maintenance on the Kibana
# index at startup. Your Kibana users still need to authenticate with Elasticsearch, which
# is proxied through the Kibana server.
#elasticsearch.username: "user"
#elasticsearch.password: "pass"

# Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.
# These settings enable SSL for outgoing requests from the Kibana server to the browser.
#server.ssl.enabled: false
#server.ssl.certificate: /path/to/your/server.crt
#server.ssl.key: /path/to/your/server.key

# Optional settings that provide the paths to the PEM-format SSL certificate and key files.
# These files validate that your Elasticsearch backend uses the same key files.
#elasticsearch.ssl.certificate: /path/to/your/client.crt
#elasticsearch.ssl.key: /path/to/your/client.key

# Optional setting that enables you to specify a path to the PEM file for the certificate
# authority for your Elasticsearch instance.
#elasticsearch.ssl.certificateAuthorities: ["/path/to/your/CA.pem"]

# To disregard the validity of SSL certificates, change this setting's value to 'none'.
#elasticsearch.ssl.verificationMode: full

# Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of
# the elasticsearch.requestTimeout setting.
#elasticsearch.pingTimeout: 1500

# Time in milliseconds to wait for responses from the back end or Elasticsearch. This value
# must be a positive integer.
#elasticsearch.requestTimeout: 30000

# List of Kibana client-side headers to send to Elasticsearch. To send *no* client-side
# headers, set this value to [] (an empty list).
#elasticsearch.requestHeadersWhitelist: [authorization]

# Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten
# by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration.
#elasticsearch.customHeaders: {}

# Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.
#elasticsearch.shardTimeout: 30000

# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.
#elasticsearch.startupTimeout: 5000

# Logs queries sent to Elasticsearch. Requires logging.verbose set to true.
#elasticsearch.logQueries: false

# Specifies the path where Kibana creates the process ID file.
#pid.file: /var/run/kibana.pid

# Enables you specify a file where Kibana stores log output.
#logging.dest: stdout

# Set the value of this setting to true to suppress all logging output.
#logging.silent: false

# Set the value of this setting to true to suppress all logging output other than error messages.
#logging.quiet: false

# Set the value of this setting to true to log all events, including system usage information
# and all requests.
#logging.verbose: false

# Set the interval in milliseconds to sample system and process performance
# metrics. Minimum is 100ms. Defaults to 5000.
#ops.interval: 5000

# Specifies locale to be used for all localizable strings, dates and number formats.
#i18n.locale: "en"
# Disable Machine Learning - we don't support that yet.
xpack.ml.enabled: false
xpack.security.enabled: false
```

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 28, 2019, 8:44pm UTC](https://discuss.elastic.co/t/unable-to-revive-connection-http-localhost-9200-no-living-connections/170086/5 "2019-03-28T20:44:31Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.