# Kibana: "No living connections" **URL:** \ **Category:** Kibana\ **Created:** [August 23, 2019, 5:08pm UTC](https://discuss.elastic.co/t/kibana-no-living-connections/196567 "2019-08-23T17:08:41Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![jonaspreisler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonaspreisler/32/37421_2.png) [@jonaspreisler](https://discuss.elastic.co/u/jonaspreisler)\ **Post date:** [August 23, 2019, 5:08pm UTC](https://discuss.elastic.co/t/kibana-no-living-connections/196567/1 "2019-08-23T17:08:41Z")
I added Elasticsearch locally and to my Ubuntu server. Now I downloaded Kibana and try to open it with 'bin/kibana'. I try to visit [http://localhost:5601/](http://localhost:5601/) and get a huge list that keeps growing until I press 'ctrl + c' (the long response in the bottom). I also try to open my Rails server so it's open meanwhile, but changes nothing. After that I try to add 'server.host: "localhost"' which changes nothing. Then I change it to 'server.host: "0.0.0.0"' and still nothing. Then I try it to 'server.host: "127.0.0.1"' and 'server.host: "193.69.47.103"' (which is my Ubuntu IP address) and still the same long response. I want to run Kibana locally and after deploy it to Ubuntu. Anyone knows what to do? Thanks 🙂 ``` jonass-MacBook-Pro:kibana jonaspreisler$ bin/kibana log [16:50:47.102] [info][plugins-system] Setting up [1] plugins: [translations] log [16:50:47.112] [info][plugins][translations] Setting up plugin log [16:50:47.114] [info][plugins-system] Starting [1] plugins: [translations] log [16:51:24.462] [info][status][plugin:kibana@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.478] [info][status][plugin:elasticsearch@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.481] [info][status][plugin:xpack_main@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.499] [info][status][plugin:telemetry@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.501] [info][status][plugin:graph@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.518] [info][status][plugin:monitoring@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.524] [info][status][plugin:spaces@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.538] [warning][security] Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml log [16:51:24.563] [warning][security] Session cookies will be transmitted over insecure connections. This is not recommended. log [16:51:24.613] [info][status][plugin:security@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.615] [info][status][plugin:searchprofiler@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.619] [info][status][plugin:ml@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.701] [info][status][plugin:tilemap@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.703] [info][status][plugin:watcher@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.725] [info][status][plugin:grokdebugger@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.733] [info][status][plugin:dashboard_mode@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.735] [info][status][plugin:logstash@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.747] [info][status][plugin:beats_management@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.777] [info][status][plugin:apm_oss@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.826] [info][status][plugin:apm@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.830] [info][status][plugin:code@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.832] [info][status][plugin:tile_map@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.836] [info][status][plugin:task_manager@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.844] [info][status][plugin:maps@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.857] [info][status][plugin:interpreter@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.874] [info][status][plugin:canvas@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.882] [info][status][plugin:license_management@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.886] [info][status][plugin:cloud@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.890] [info][status][plugin:index_management@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.917] [info][status][plugin:console@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.920] [info][status][plugin:console_extensions@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.926] [info][status][plugin:notifications@7.3.1] Status changed from uninitialized to green - Ready log [16:51:24.957] [info][status][plugin:index_lifecycle_management@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:24.982] [info][status][plugin:metrics@7.3.1] Status changed from uninitialized to green - Ready log [16:51:25.039] [info][status][plugin:infra@7.3.1] Status changed from uninitialized to green - Ready log [16:51:25.042] [info][status][plugin:rollup@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:51:25.054] [info][siem] Plugin initializing log [16:51:25.102] [info][siem] Plugin done initializing log [16:51:25.103] [info][status][plugin:siem@7.3.1] Status changed from uninitialized to green - Ready ``` ---
**Author:** ![christophilus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christophilus/32/42991_2.png) [@christophilus](https://discuss.elastic.co/u/christophilus)\ **Post date:** [August 23, 2019, 7:53pm UTC](https://discuss.elastic.co/t/kibana-no-living-connections/196567/2 "2019-08-23T19:53:12Z")
That looks like a normal startup log, unless I'm missing something. Is there a specific part of that log that you think is wrong? ---
**Author:** ![jonaspreisler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jonaspreisler/32/37421_2.png) [@jonaspreisler](https://discuss.elastic.co/u/jonaspreisler)\ **Post date:** [August 24, 2019, 8:32am UTC](https://discuss.elastic.co/t/kibana-no-living-connections/196567/3 "2019-08-24T08:32:52Z")
Yes this part: log [08:31:01.948] [warning][admin][elasticsearch] No living connections And when I visit [http://localhost:5601/:](http://localhost:5601/:) ![21](https://us1.discourse-cdn.com/elastic/original/3X/9/a/9a8d6275c32c1cad9e6dacd59ec96d2c33e25532.png) Full terminal response: [https://paste.ofcode.org/jZv8QvB9XFVadnTGRUy9Na](https://paste.ofcode.org/jZv8QvB9XFVadnTGRUy9Na) ---
**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\ **Post date:** [August 24, 2019, 4:10pm UTC](https://discuss.elastic.co/t/kibana-no-living-connections/196567/4 "2019-08-24T16:10:36Z")
post your kibana.yml file and elasticsearch.yml file. without comment section. something you might have miss in that. you should see something like this. [root]# netstat -an |grep 5601 tcp 0 0 \:5601 0.0.0.0:\* LISTEN ---
**Author:** ![mbelaloui](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mbelaloui/32/49140_2.png) [@mbelaloui](https://discuss.elastic.co/u/mbelaloui)\ **Post date:** [August 25, 2019, 4:26pm UTC](https://discuss.elastic.co/t/kibana-no-living-connections/196567/5 "2019-08-25T16:26:13Z")
Hello every one, Seems that the elasticsearch is not started or not well configured with the correct ip in the kibana .yml Please post your elasticsearch, kibana yml file #elasticforme. Mehdi. ---
**Author:** ![RamyaGowda](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ramyagowda/32/27440_2.png) [@RamyaGowda](https://discuss.elastic.co/u/RamyaGowda)\ **Post date:** [August 25, 2019, 4:34pm UTC](https://discuss.elastic.co/t/kibana-no-living-connections/196567/6 "2019-08-25T16:34:15Z")
Hi @jonaspreisler , Kibana is trying to connect to ES server at **localhost:9200** , Are you sure that your Elasticsearch is up and running . Can you provide "[http://localhost:9200](http://localhost:9200)" output ---
**Author:** ![christophilus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christophilus/32/42991_2.png) [@christophilus](https://discuss.elastic.co/u/christophilus)\ **Post date:** [August 26, 2019, 3:21pm UTC](https://discuss.elastic.co/t/kibana-no-living-connections/196567/7 "2019-08-26T15:21:32Z")
Thanks for providing the log. It looks to me like you're running Kibana with x-pack against an Elasticsearch cluster that is not running x-pack. I think that's the problem. I think you either need to run x-pack on both or on neither. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 23, 2019, 3:21pm UTC](https://discuss.elastic.co/t/kibana-no-living-connections/196567/8 "2019-09-23T15:21:36Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.