# Not able to access Kibana

**URL:** <https://discuss.elastic.co/t/not-able-to-access-kibana/133553>\
**Category:** Kibana\
**Created:** [May 28, 2018, 1:35pm UTC](https://discuss.elastic.co/t/not-able-to-access-kibana/133553 "2018-05-28T13:35:00Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![abhat](https://avatars.discourse-cdn.com/v4/letter/a/8e8cbc/32.png) [@abhat](https://discuss.elastic.co/u/abhat)\
**Post date:** [May 28, 2018, 1:35pm UTC](https://discuss.elastic.co/t/not-able-to-access-kibana/133553/1 "2018-05-28T13:35:01Z")

</div>

Hi Team,

I have installed ELK stack on the Cent OS system.

Now I am trying to login to Kibana but I am seeing below page -  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/2/426e970470480afa843d121f33b81d53ffe72b0c.png)

Used below URL -  
[http://HOSTNAME:5601/](http://HOSTNAME:5601/)

Also used elastic stack domain that I used in the Nginx configuration.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/1/c17c954401a51b9212f99035fd73b56a5b58fcd5.png)

Just an FYI - Kibana , ElasticSearch and Logstash is showing up using below command

systemctl status kibana  
systemctl status elasticsearch  
systemctl status logstash

Any ideas what I am missing ?

Kind Regards,  
Asif Bhat

---

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [May 28, 2018, 1:52pm UTC](https://discuss.elastic.co/t/not-able-to-access-kibana/133553/2 "2018-05-28T13:52:32Z")

</div>

Hi,

if you setup a reverse proxy for Kibana, shouldn't you rather try to access `http://hostname` instead of `http://hostname:5601`? If you are trying to access Kibana via `hostname:5601` have you made sure it's really be accessible from the outside network, and not just within your server?

Cheers,  
Tim

---

<div class="post-metadata">

**Author:** ![abhat](https://avatars.discourse-cdn.com/v4/letter/a/8e8cbc/32.png) [@abhat](https://discuss.elastic.co/u/abhat)\
**Post date:** [May 28, 2018, 1:54pm UTC](https://discuss.elastic.co/t/not-able-to-access-kibana/133553/3 "2018-05-28T13:54:29Z")

</div>

I tried both -

[http://hostname](http://hostname)  
[http://hostname:5601](http://hostname:5601)

What setting I need to perform to make it accessible from outside network ?

---

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [May 28, 2018, 1:55pm UTC](https://discuss.elastic.co/t/not-able-to-access-kibana/133553/4 "2018-05-28T13:55:57Z")

</div>

I can't provide any details about your network configuration. Does Kibana respond, if you try to access it from the server host itself via `localhost:5601`?

---

<div class="post-metadata">

**Author:** ![abhat](https://avatars.discourse-cdn.com/v4/letter/a/8e8cbc/32.png) [@abhat](https://discuss.elastic.co/u/abhat)\
**Post date:** [May 28, 2018, 1:57pm UTC](https://discuss.elastic.co/t/not-able-to-access-kibana/133553/5 "2018-05-28T13:57:01Z")

</div>

Moreover when I am using only hostname I am getting below screen -

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/4/c4db91a152ee0eb2034a85da30a7a313a45b269a.png)

Entered kibanaadmin and the password but it is still showing the same window.

---

<div class="post-metadata">

**Author:** ![abhat](https://avatars.discourse-cdn.com/v4/letter/a/8e8cbc/32.png) [@abhat](https://discuss.elastic.co/u/abhat)\
**Post date:** [May 28, 2018, 2:01pm UTC](https://discuss.elastic.co/t/not-able-to-access-kibana/133553/6 "2018-05-28T14:01:43Z")

</div>

Any general setting from the ELK stack ?

---

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [May 28, 2018, 2:08pm UTC](https://discuss.elastic.co/t/not-able-to-access-kibana/133553/7 "2018-05-28T14:08:07Z")

</div>

That login is coming from your reverse proxy (and not from Kibana). It's coming from the line:

```auto
auth_basic_user_file /etc/nginx/.kibana-user

```

So you should provide the credentials, that are written within that file on the server?

Cheers,  
Tim

---

<div class="post-metadata">

**Author:** ![abhat](https://avatars.discourse-cdn.com/v4/letter/a/8e8cbc/32.png) [@abhat](https://discuss.elastic.co/u/abhat)\
**Post date:** [May 28, 2018, 2:14pm UTC](https://discuss.elastic.co/t/not-able-to-access-kibana/133553/8 "2018-05-28T14:14:35Z")

</div>

My Bad.

I was using the kibanaadmin instead of "admin".

Thanks a ton for your help.

---

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [May 28, 2018, 2:16pm UTC](https://discuss.elastic.co/t/not-able-to-access-kibana/133553/9 "2018-05-28T14:16:14Z")

</div>

Glad we could solve that issue so easily 🙂

Wish you a nice day,  
Tim

---

<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:** [June 25, 2018, 2:27pm UTC](https://discuss.elastic.co/t/not-able-to-access-kibana/133553/10 "2018-06-25T14:27:05Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
