# Can not access kibana\_ip:5601, but kibana service seems to be running?

**URL:** <https://discuss.elastic.co/t/can-not-access-kibana-ip-5601-but-kibana-service-seems-to-be-running/64204>\
**Category:** Kibana\
**Created:** [October 27, 2016, 8:41pm UTC](https://discuss.elastic.co/t/can-not-access-kibana-ip-5601-but-kibana-service-seems-to-be-running/64204 "2016-10-27T20:41:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ZillaG](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zillag/32/10505_2.png) [@ZillaG](https://discuss.elastic.co/u/ZillaG)\
**Post date:** [October 27, 2016, 8:41pm UTC](https://discuss.elastic.co/t/can-not-access-kibana-ip-5601-but-kibana-service-seems-to-be-running/64204/1 "2016-10-27T20:41:28Z")

</div>

kibana v4.5.4  
ES v2.4.1

I have Kibana hooked up to one of my ES servers on my ES cluster, and I see these logs when I start the service

```
{"type":"log","@timestamp":"2016-10-27T20:19:12+00:00","tags":["listening","info"],"pid":6584,"message":"Server running at http://0.0.0.0:5601"}
{"type":"log","@timestamp":"2016-10-27T20:19:12+00:00","tags":["status","plugin:elasticsearch","info"],"pid":6584,"name":"plugin:elasticsearch","state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}

```

I can even do this.

```
curl https://es_ip_address:9200/_cat/indices?v --cacert /etc/pki/logstash/root-ca.pem -u user:pw
health status index pri rep docs.count docs.deleted store.size pri.store.size 
green open .kibana 1 2 1 0 9.5kb 3.1kb 
green open searchguard 1 2 0 0 207.7kb 69.2kb 

```

But i can't access the kibana page? Anything else I can look at?

---

<div class="post-metadata">

**Author:** ![ZillaG](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zillag/32/10505_2.png) [@ZillaG](https://discuss.elastic.co/u/ZillaG)\
**Post date:** [October 27, 2016, 9:41pm UTC](https://discuss.elastic.co/t/can-not-access-kibana-ip-5601-but-kibana-service-seems-to-be-running/64204/2 "2016-10-27T21:41:25Z")

</div>

BTW, in this case, Kibana is on a DIFFERENT server from my ES cluster. IOW, I have the following server configuration:

- 3 servers for ES cluster, all master & data
- 1 server, separate from above 3 ES servers, that run Kibana and Logstash. nginx is also running on this server

---

<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:** [October 28, 2016, 7:52am UTC](https://discuss.elastic.co/t/can-not-access-kibana-ip-5601-but-kibana-service-seems-to-be-running/64204/3 "2016-10-28T07:52:03Z")

</div>

Firewall? Can you telnet to the port from another machine?

---

<div class="post-metadata">

**Author:** ![ZillaG](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zillag/32/10505_2.png) [@ZillaG](https://discuss.elastic.co/u/ZillaG)\
**Post date:** [October 28, 2016, 3:42pm UTC](https://discuss.elastic.co/t/can-not-access-kibana-ip-5601-but-kibana-service-seems-to-be-running/64204/4 "2016-10-28T15:42:18Z")

</div>

In my case, I'm setting this up in AWS, and my instance belonged to a private subnet. I set up an internet-facing elastic load balancer (ELB) which forwarded http:80 traffic to http:5601, and it worked.

Just to answer your question, firewall service was not installed on the server, and SELinux was disabled.

---

<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:35pm UTC](https://discuss.elastic.co/t/can-not-access-kibana-ip-5601-but-kibana-service-seems-to-be-running/64204/5 "2017-07-06T13:35:20Z")

</div>