# Unable to receive connection: http://localhost:9200/ **URL:** \ **Category:** Kibana\ **Created:** [November 8, 2016, 6:55am UTC](https://discuss.elastic.co/t/unable-to-receive-connection-http-localhost-9200/65307 "2016-11-08T06:55:59Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![perrylu21](https://avatars.discourse-cdn.com/v4/letter/p/f475e1/32.png) [@perrylu21](https://discuss.elastic.co/u/perrylu21)\ **Post date:** [November 8, 2016, 6:55am UTC](https://discuss.elastic.co/t/unable-to-receive-connection-http-localhost-9200/65307/1 "2016-11-08T06:55:59Z")
I use ELK 5.0.0 stack on windows 7(32-bits). logstash-5.0.0 elasticsearch-5.0.0 kibana-5.0.0-windows-x86 logstash and elasticsearch can start without error. But when I start kibana, it always shows ```auto [elasticsearch] No living connections [elasticsearch] Unable to receive connections: http://localhost:9200/ ``` If I navigate to [http://localhost:9200/](http://localhost:9200/), the message can be received without problem, which means elasticsearch is working well. Can somebody help check my configuration file of kibana? ```auto # Enables you to specify a path to mount Kibana at if you are running behind a proxy. This only affects # the URLs generated by Kibana, your proxy is expected to remove the basePath value before forwarding requests # to Kibana. This setting cannot end in a slash. #server.basePath: "" # 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: "perry-kibana" # The URL of the Elasticsearch instance to use for all your queries. # elasticsearch.url: "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: "discover" # 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" # Paths to the PEM-format SSL certificate and SSL key files, respectively. These # files enable SSL for outgoing requests from the Kibana server to the browser. #server.ssl.cert: /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.cert: /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.ca: /path/to/your/CA.pem # To disregard the validity of SSL certificates, change this setting’s value to false. elasticsearch.ssl.verify: false # 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: 0 # Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying. #elasticsearch.startupTimeout: 5000 # 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 ``` ---
**Author:** ![lukas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas/32/6812_2.png) [@lukas](https://discuss.elastic.co/u/lukas)\ **Post date:** [November 8, 2016, 8:20pm UTC](https://discuss.elastic.co/t/unable-to-receive-connection-http-localhost-9200/65307/2 "2016-11-08T20:20:47Z")
Nothing immediately sticks out to me, but I'm curious if you just use the default configuration if things work or if you get the same error. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 6, 2016, 8:21pm UTC](https://discuss.elastic.co/t/unable-to-receive-connection-http-localhost-9200/65307/3 "2016-12-06T20:21:17Z")
Closed on December 6, 2016, 8:21pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.