# Cannot reach Kibana on browser after installation

**URL:** <https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564>\
**Category:** Kibana\
**Created:** [November 25, 2015, 2:20pm UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564 "2015-11-25T14:20:11Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![oleksii](https://avatars.discourse-cdn.com/v4/letter/o/9de053/32.png) [@oleksii](https://discuss.elastic.co/u/oleksii)\
**Post date:** [November 25, 2015, 2:20pm UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/1 "2015-11-25T14:20:11Z")

</div>

Hello guys.

I am not a linux guru - just know how to do simple stuff. But I got a task to setup ELK.  
I am running Red Hat Enterprise Linux Server release 6.2

What I did so far:

1. Installed Elastisearch, Logstash and Kibana (2.1.0)
2. Installed Marvel plugin for Elasticsearch and Kibana
3. Changed **network.host** to **10.10.10.10** (lets assume this is IP address of the host where I installed it) in **elasticsearh.yml**.  
I had to change it from \*\*localhost \*\*as otherwise I could not reach it on the browser from my local machine. I use SSH to connect to the host.
4. I uncommented and changed this variables in **kibana.yml** :  
**server.port: 5601**  
**server.host: "10.10.10.10"**  
**elasticsearch.url: "[http://10.10.10.10:9200](http://10.10.10.10:9200)"**  
I tried to run it with defualt settings first, but it did not work.

What I have in the end:

- I can reach elastisearch on [http://10.10.10.10:9200/](http://10.10.10.10:9200/)

> {  
> "name" : "Fasaud",  
> "cluster\_name" : "elasticsearch",  
> "version" : {  
> "number" : "2.1.0",  
> "build\_hash" : "72cd1f1a3eee09505e036106146dc1949dc5dc87",  
> "build\_timestamp" : "2015-11-18T22:40:03Z",  
> "build\_snapshot" : false,  
> "lucene\_version" : "5.3.1"  
> },  
> "tagline" : "You Know, for Search"  
> }

- I cannot reach kibana on [http://10.10.10.10:5601/](http://10.10.10.10:5601/) - timeout.

Both services run on the same 10.10.10.10 host:

Guys, basing on this information, do you have any suggestions why I am able to reach elastisearch from my machine, but in the same time kibana returns me a timeout?  
What can I check in this case?

Thanks.

---

<div class="post-metadata">

**Author:** ![oleksii](https://avatars.discourse-cdn.com/v4/letter/o/9de053/32.png) [@oleksii](https://discuss.elastic.co/u/oleksii)\
**Post date:** [November 25, 2015, 2:22pm UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/2 "2015-11-25T14:22:07Z")

</div>

Kibana:

> log [13:07:19.864] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready  
> log [13:07:19.929] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
> log [13:07:19.940] [info][status][plugin:marvel] Status changed from uninitialized to yellow - Waiting for Elasticsearch  
> log [13:07:19.986] [info][status][plugin:kbn\_vislib\_vis\_types] Status changed from uninitialized to green - Ready  
> log [13:07:19.998] [info][status][plugin:markdown\_vis] Status changed from uninitialized to green - Ready  
> log [13:07:20.014] [info][status][plugin:metric\_vis] Status changed from uninitialized to green - Ready  
> log [13:07:20.027] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready  
> log [13:07:23.231] [info][status][plugin:elasticsearch] Status changed from yellow to green - Kibana index ready  
> log [13:07:23.237] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready  
> log [13:07:23.257] [info][status][plugin:table\_vis] Status changed from uninitialized to green - Ready  
> log [13:07:23.264] [info][status][plugin:marvel] Status changed from yellow to green - Marvel index ready  
> log [13:07:23.286] [info][listening] Server running at [http://10.10.10.10:5601](http://10.10.10.10:5601)

---

<div class="post-metadata">

**Author:** ![oleksii](https://avatars.discourse-cdn.com/v4/letter/o/9de053/32.png) [@oleksii](https://discuss.elastic.co/u/oleksii)\
**Post date:** [November 25, 2015, 2:23pm UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/3 "2015-11-25T14:23:05Z")

</div>

Elasticsearch:

> [2015-11-25 12:47:45,315][WARN][bootstrap] unable to install syscall filter: prctl(PR\_GET\_NO\_NEW\_PRIVS): Invalid argument  
> [2015-11-25 12:47:45,666][INFO][node] [Fasaud] version[2.1.0], pid[64108], build[72cd1f1/2015-11-18T22:40:03Z]  
> [2015-11-25 12:47:45,666][INFO][node] [Fasaud] initializing ...  
> [2015-11-25 12:47:46,051][INFO][plugins] [Fasaud] loaded [marvel-agent, license], sites   
> [2015-11-25 12:47:46,084][INFO][env] [Fasaud] using [1] data paths, mounts [[/home (/dev/mapper/VG01-HOME)]], net usable\_space [410.5mb], net total\_space [1007.8mb], spins? [possibly], types [ext3]  
> [2015-11-25 12:47:48,987][INFO][node] [Fasaud] initialized  
> [2015-11-25 12:47:48,987][INFO][node] [Fasaud] starting ...  
> [2015-11-25 12:47:49,070][INFO][transport] [Fasaud] publish\_address {10.10.10.10:9300}, bound\_addresses {10.10.10.10:9300}  
> [2015-11-25 12:47:49,081][INFO][discovery] [Fasaud] elasticsearch/9nqkzuLzQjGKuzA7OImP4w  
> [2015-11-25 12:47:52,127][INFO][cluster.service] [Fasaud] new\_master {Fasaud}{9nqkzuLzQjGKuzA7OImP4w}{10.10.10.10}{10.10.10.10:9300}, reason: zen-disco-join(elected\_as\_master, [0] joins received)  
> [2015-11-25 12:47:52,138][INFO][http] [Fasaud] publish\_address {10.10.10.10:9200}, bound\_addresses {10.10.10.10:9200}  
> [2015-11-25 12:47:52,138][INFO][node] [Fasaud] started  
> [2015-11-25 12:47:52,419][INFO][license.plugin.core] [Fasaud] license [958de414-958a-43f6-8523-ee19281d6ebe] - valid  
> [2015-11-25 12:47:52,422][ERROR][license.plugin.core] [Fasaud]
> 
> License will expire on [Friday, December 25, 2015]. If you have a new license, please update it.  
> Otherwise, please reach out to your support contact.
> 
> Commercial plugins operate with reduced functionality on license expiration:
> 
> - marvel
> - The agent will stop collecting cluster and indices metrics  
> [2015-11-25 12:47:52,482][INFO][gateway] [Fasaud] recovered [2] indices into cluster\_state  
> [2015-11-25 12:47:53,138][WARN][index.translog] [Fasaud] [.marvel-es-data][0] failed to delete temp file /home/user/elasticsearch/data/elasticsearch/nodes/0/indices/.marvel-es-data/0/translog/translog-7004757204317464298.tlog  
> java.nio.file.NoSuchFileException: /home/user/elasticsearch/data/elasticsearch/nodes/0/indices/.marvel-es-data/0/translog/translog-7004757204317464298.tlog  
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)  
> .......  
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
> at java.lang.Thread.run(Thread.java:745)  
> [2015-11-25 12:47:53,153][WARN][index.translog] [Fasaud] [.marvel-es-2015.11.25][0] failed to delete temp file /home/user/elasticsearch/data/elasticsearch/nodes/0/indices/.marvel-es-2015.11.25/0/translog/translog-4129335779084657074.tlog  
> java.nio.file.NoSuchFileException: /home/user/elasticsearch/data/elasticsearch/nodes/0/indices/.marvel-es-2015.11.25/0/translog/translog-4129335779084657074.tlog  
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)  
> ..........................  
> at java.lang.Thread.run(Thread.java:745)  
> [2015-11-25 12:48:53,724][INFO][cluster.metadata] [Fasaud] [.kibana] creating index, cause [api], templates , shards [1]/[1], mappings [config]  
> [2015-11-25 12:48:56,547][INFO][cluster.metadata] [Fasaud] [.kibana] create\_mapping [index-pattern]  
> [2015-11-25 12:48:56,793][INFO][cluster.metadata] [Fasaud] [.kibana] update\_mapping [config]

---

<div class="post-metadata">

**Author:** ![oleksii](https://avatars.discourse-cdn.com/v4/letter/o/9de053/32.png) [@oleksii](https://discuss.elastic.co/u/oleksii)\
**Post date:** [November 25, 2015, 7:59pm UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/4 "2015-11-25T19:59:34Z")

</div>

Can it be due to the fact taht nginx is not installed/running?

> [~]$ service nginx start  
> nginx: unrecognized service

From the guide:

> Because we configured Kibana to listen on localhost, we must set up a reverse proxy to allow external access to it. We will use Nginx for this purpose

But because I changed localhost to host's ip-address do I still need to use nginx?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 27, 2015, 6:38am UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/5 "2015-11-27T06:38:02Z")

</div>

What guide?

---

<div class="post-metadata">

**Author:** ![oleksii](https://avatars.discourse-cdn.com/v4/letter/o/9de053/32.png) [@oleksii](https://discuss.elastic.co/u/oleksii)\
**Post date:** [November 30, 2015, 9:08am UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/6 "2015-11-30T09:08:16Z")

</div>

"Helpful community" they said to me 🙂

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 30, 2015, 10:05am UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/7 "2015-11-30T10:05:53Z")

</div>

Not sure what you are implying there, but given you are referring to things we have no idea about and we are not mind readers, I am not sure what you expect us to do?

---

<div class="post-metadata">

**Author:** ![oleksii](https://avatars.discourse-cdn.com/v4/letter/o/9de053/32.png) [@oleksii](https://discuss.elastic.co/u/oleksii)\
**Post date:** [November 30, 2015, 10:52am UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/8 "2015-11-30T10:52:06Z")

</div>

Sorry then. What extra information needs to be added to make it more clear?  
I am trying to test ELK solution.

---

<div class="post-metadata">

**Author:** ![NilsBecker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nilsbecker/32/6243_2.png) [@NilsBecker](https://discuss.elastic.co/u/NilsBecker)\
**Post date:** [November 30, 2015, 11:14am UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/9 "2015-11-30T11:14:43Z")

</div>

What browser did you use?

---

<div class="post-metadata">

**Author:** ![oleksii](https://avatars.discourse-cdn.com/v4/letter/o/9de053/32.png) [@oleksii](https://discuss.elastic.co/u/oleksii)\
**Post date:** [November 30, 2015, 11:39am UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/10 "2015-11-30T11:39:50Z")

</div>

Guys, I have just tried it one more time - and it works.  
It has not been working for me for the previous few days. Can't explain it.

---

<div class="post-metadata">

**Author:** ![ahegazi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ahegazi/32/11614_2.png) [@ahegazi](https://discuss.elastic.co/u/ahegazi)\
**Post date:** [August 26, 2016, 11:38am UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/11 "2016-08-26T11:38:07Z")

</div>

guys,

I have got a similar issue as well, can't reach kibana 4.5 via browser (Chrome Version 52.0.2743.116 (64-bit)) however I am able to curl -XGET localhost:9200

would there be an issue especially I am trying to access it from local test network which everything is behind the firewall!

Thanks,

---

<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:** [July 6, 2017, 1:40pm UTC](https://discuss.elastic.co/t/cannot-reach-kibana-on-browser-after-installation/35564/12 "2017-07-06T13:40:13Z")

</div>


