# Cannot Start kibana

**URL:** <https://discuss.elastic.co/t/cannot-start-kibana/57517>\
**Category:** Kibana\
**Created:** [August 8, 2016, 6:28pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517 "2016-08-08T18:28:05Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![sv2c](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@sv2c](https://discuss.elastic.co/u/sv2c)\
**Post date:** [August 8, 2016, 6:28pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/1 "2016-08-08T18:28:06Z")

</div>

Elasticsearch: 1.7.4  
Kibana: 4.1.0

> kibana  
> {"name":"Kibana","hostname":"Goble004","pid":10872,"level":50,"err":{"message":"Request Timeout after 5000ms","name":"Error","stack":"Error: Request Timeout after 5000ms\n at null. (C:\Users\svelupula\kibana-4.1.0-windows\src\node\_modules\elasticsearch\src\lib\transport.js:282:15)\n at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)"},"msg":"","time":"2016-08-08T17:56:42.879Z","v":0}  
> {"name":"Kibana","hostname":"Goble004","pid":10872,"level":60,"err":{"message":"Request Timeout after 5000ms","name":"Error","stack":"Error: Request Timeout after 5000ms\n at null. (C:\Users\svelupula\kibana-4.1.0-windows\src\node\_modules\elasticsearch\src\lib\transport.js:282:15)\n at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)"},"msg":"","time":"2016-08-08T17:56:42.891Z","v":0}

---

<div class="post-metadata">

**Author:** ![BigFunger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigfunger/32/7323_2.png) [@BigFunger](https://discuss.elastic.co/u/BigFunger)\
**Post date:** [August 9, 2016, 3:22pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/2 "2016-08-09T15:22:52Z")

</div>

Can you provide some more details on your setup?

Are you running both Elasticsearch and Kibana on the same machine?  
Are you able to query Elasticsearch outside of Kibana?

---

<div class="post-metadata">

**Author:** ![sv2c](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@sv2c](https://discuss.elastic.co/u/sv2c)\
**Post date:** [August 9, 2016, 6:11pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/3 "2016-08-09T18:11:47Z")

</div>

ES and kibana is on the same machine. ES is configured with shield. I can hit ES:9200 and can see the ES page.

---

<div class="post-metadata">

**Author:** ![BigFunger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigfunger/32/7323_2.png) [@BigFunger](https://discuss.elastic.co/u/BigFunger)\
**Post date:** [August 9, 2016, 6:27pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/4 "2016-08-09T18:27:43Z")

</div>

It’s a generic timeout error, basically it took longer than 5 seconds for the cluster to respond to the query.

Check your cluster state.

If you back up your Elasticsearch cluster and try it with a fresh install of Elasticsearch, do you get the same error?

Is this behavior that recently emerged, or has your stack install never worked correctly?

---

<div class="post-metadata">

**Author:** ![sv2c](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@sv2c](https://discuss.elastic.co/u/sv2c)\
**Post date:** [August 9, 2016, 6:43pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/5 "2016-08-09T18:43:13Z")

</div>

I have installed both ES and kibana yesterday so both are new installs. So far, kibana has never (well only a day since I installed it) worked for me.

---

<div class="post-metadata">

**Author:** ![sv2c](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@sv2c](https://discuss.elastic.co/u/sv2c)\
**Post date:** [August 9, 2016, 6:46pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/6 "2016-08-09T18:46:21Z")

</div>

ES page says "\_cluster health: not connected"

[http://localhost:9200/\_cluster/health?pretty=true](http://localhost:9200/_cluster/health?pretty=true)  
{  
"cluster\_name" : "elasticsearch",  
"status" : "green",  
"timed\_out" : false,  
"number\_of\_nodes" : 1,  
"number\_of\_data\_nodes" : 1,  
"active\_primary\_shards" : 0,  
"active\_shards" : 0,  
"relocating\_shards" : 0,  
"initializing\_shards" : 0,  
"unassigned\_shards" : 0,  
"delayed\_unassigned\_shards" : 0,  
"number\_of\_pending\_tasks" : 0,  
"number\_of\_in\_flight\_fetch" : 0  
}

---

<div class="post-metadata">

**Author:** ![BigFunger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigfunger/32/7323_2.png) [@BigFunger](https://discuss.elastic.co/u/BigFunger)\
**Post date:** [August 9, 2016, 6:48pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/7 "2016-08-09T18:48:01Z")

</div>

Can we eliminate Shield from the picture to start with?

You should be able to disable it in ES by adding `shield.enabled: false` to your elasticsearch.yml file

---

<div class="post-metadata">

**Author:** ![BigFunger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigfunger/32/7323_2.png) [@BigFunger](https://discuss.elastic.co/u/BigFunger)\
**Post date:** [August 9, 2016, 6:49pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/8 "2016-08-09T18:49:00Z")

</div>

You also said that you had Shield enabled on Elasticsearch, do you also have it installed on Kibana?

---

<div class="post-metadata">

**Author:** ![sv2c](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@sv2c](https://discuss.elastic.co/u/sv2c)\
**Post date:** [August 9, 2016, 6:49pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/9 "2016-08-09T18:49:49Z")

</div>

I don't have shield installed/configuread on kibana

---

<div class="post-metadata">

**Author:** ![BigFunger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigfunger/32/7323_2.png) [@BigFunger](https://discuss.elastic.co/u/BigFunger)\
**Post date:** [August 9, 2016, 6:50pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/10 "2016-08-09T18:50:39Z")

</div>

Is there a reason why you're running those specific versions?

---

<div class="post-metadata">

**Author:** ![BigFunger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigfunger/32/7323_2.png) [@BigFunger](https://discuss.elastic.co/u/BigFunger)\
**Post date:** [August 9, 2016, 6:52pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/11 "2016-08-09T18:52:43Z")

</div>

If you need to run the 4.1 line, there is a [4.1.11 release](https://download.elastic.co/kibana/kibana/kibana-4.1.11-windows.zip). Not sure if it will solve your specific problem, but it'll make the feedback I'm getting from my team more accurate. 😉

---

<div class="post-metadata">

**Author:** ![sv2c](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@sv2c](https://discuss.elastic.co/u/sv2c)\
**Post date:** [August 9, 2016, 6:55pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/12 "2016-08-09T18:55:32Z")

</div>

Without shield, ES health cluster is connected and shows green.

Actually thinking what I did.. In Kibana, I did this to configure shield:

**esusers useradd kuser -r kuser -p pass**

**changed the kibana.yml and updated the user and password:**  
elasticsearch.username: kuser  
elasticsearch.password: pass

---

<div class="post-metadata">

**Author:** ![BigFunger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigfunger/32/7323_2.png) [@BigFunger](https://discuss.elastic.co/u/BigFunger)\
**Post date:** [August 9, 2016, 7:02pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/13 "2016-08-09T19:02:31Z")

</div>

I apologize, but I'm slightly confused. Are you telling me things that you initially configured in order to create the issue, or did you find a solution to your problem?

Are you able to upgrade to 4.1.11?

---

<div class="post-metadata">

**Author:** ![sv2c](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@sv2c](https://discuss.elastic.co/u/sv2c)\
**Post date:** [August 9, 2016, 7:05pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/14 "2016-08-09T19:05:37Z")

</div>

With version 4.1.0: When I configured ES with shield I also configured kibana with the same info.

4.1.11: I just downloaded this and I see same errors. ES is 1.7.4

---

<div class="post-metadata">

**Author:** ![BigFunger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigfunger/32/7323_2.png) [@BigFunger](https://discuss.elastic.co/u/BigFunger)\
**Post date:** [August 9, 2016, 7:12pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/15 "2016-08-09T19:12:26Z")

</div>

Please bare with me, as I am trying to reproduce your scenario. I downloaded Kibana 4.1.11, and ES 1.7.4 and have them up and running and talking to each other. (Which it sounds like you did as well)

How did you install Shield? (I want to make sure I follow the same steps)

---

<div class="post-metadata">

**Author:** ![sv2c](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@sv2c](https://discuss.elastic.co/u/sv2c)\
**Post date:** [August 9, 2016, 7:20pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/16 "2016-08-09T19:20:36Z")

</div>

My OS is Windows 7.

to install shield I did this:  
bin/plugin install elasticsearch/license/latest  
bin/plugin install elasticsearch/shield/latest

---

<div class="post-metadata">

**Author:** ![sv2c](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@sv2c](https://discuss.elastic.co/u/sv2c)\
**Post date:** [August 9, 2016, 7:23pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/17 "2016-08-09T19:23:07Z")

</div>

I have elasticsearch-head installed as well..

command:  
elasticsearch1.7.4/bin/plugin -install mobz/elasticsearch-head/1.7

---

<div class="post-metadata">

**Author:** ![sv2c](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@sv2c](https://discuss.elastic.co/u/sv2c)\
**Post date:** [August 9, 2016, 7:38pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/18 "2016-08-09T19:38:50Z")

</div>

So I restarted from scratch, I re installed both kibana and ES (into a different directory than before). Just downloaded ES 1.7.4 (tried 1.7.5 as well) and Kibana 4.1.11 and ran both on the same machine.

kibana does not start, timeout Errors as before.

---

<div class="post-metadata">

**Author:** ![BigFunger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bigfunger/32/7323_2.png) [@BigFunger](https://discuss.elastic.co/u/BigFunger)\
**Post date:** [August 9, 2016, 8:10pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/19 "2016-08-09T20:10:18Z")

</div>

Here are the steps that I took.

1. Downloaded [Elasticsearch 1.7.4](https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-1.7.4.zip)
2. Downloaded [Kibana 4.1.11](https://download.elastic.co/kibana/kibana/kibana-4.1.11-windows.zip)
3. Unzipped them to respective folders
4. Installed license to Elasticsearch:  
`./bin/plugin install elasticsearch/license/latest`
5. Installed Shield to Elasticsearch:  
`./bin/plugin install elasticsearch/shield/latest`
6. Added a kibana user to Shield:  
`./bin/shield/esusers useradd kuser -r kibana4 -p password`
7. Added a kibana server user to Shield:  
`./bin/shield/esusers useradd kserver -r kibana4_server -p password`
8. Modified my `kibana.yml` file to configure the kibana server credentials:

```auto
# If your Elasticsearch is protected with basic auth, this is the user credentials
# used by the Kibana server to perform maintence on the kibana_index at statup. Your Kibana
# users will still need to authenticate with Elasticsearch (which is proxied thorugh
# the Kibana server)
kibana_elasticsearch_username: kserver
kibana_elasticsearch_password: password

```

1. Start Elasticsearch  
`.\bin\elasticsearch`
2. Start Kibana (in kibana folder)  
`.\bin\kibana`

I was able to log in with the kibana user credentials. Are you able to get this far (without installing the third-party plugin)?

---

<div class="post-metadata">

**Author:** ![sv2c](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@sv2c](https://discuss.elastic.co/u/sv2c)\
**Post date:** [August 9, 2016, 8:34pm UTC](https://discuss.elastic.co/t/cannot-start-kibana/57517/20 "2016-08-09T20:34:38Z")

</div>

Re ran these exact steps letter to letter. Same error. kibana does not start.

[Next page](https://discuss.elastic.co/t/cannot-start-kibana/57517.md?page=2)
