# Problem accessing Kibana through the browser

**URL:** <https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201>\
**Category:** Kibana\
**Created:** [October 3, 2019, 3:10pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201 "2019-10-03T15:10:44Z")\
**Posts on this page:** 11\
**Page:** 3

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [October 7, 2019, 10:32pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201/41 "2019-10-07T22:32:27Z")

</div>

I can help you verify that kibana is up and running and you can log in but I don't have much experience with nginx.

---

<div class="post-metadata">

**Author:** ![abuit01](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@abuit01](https://discuss.elastic.co/u/abuit01)\
**Post date:** [October 8, 2019, 1:40pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201/42 "2019-10-08T13:40:33Z")

</div>

Ok thanks,  
Do you know any way to generate authentication when accessing kibana?

---

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [October 8, 2019, 1:42pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201/43 "2019-10-08T13:42:45Z")

</div>

Can you explain more about generating authentication? I'm not sure what you mean.

---

<div class="post-metadata">

**Author:** ![abuit01](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@abuit01](https://discuss.elastic.co/u/abuit01)\
**Post date:** [October 8, 2019, 1:47pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201/44 "2019-10-08T13:47:00Z")

</div>

The credentials request to access the functionalities of kibana, which does not access directly. In order to maintain information security.

---

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [October 8, 2019, 1:49pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201/45 "2019-10-08T13:49:04Z")

</div>

Are you looking to modify or alter the build in login process in kibana?

---

<div class="post-metadata">

**Author:** ![abuit01](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@abuit01](https://discuss.elastic.co/u/abuit01)\
**Post date:** [October 8, 2019, 1:55pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201/46 "2019-10-08T13:55:37Z")

</div>

Something similar, I must do that when I enter the kibana address in the browser, a login is requested

---

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [October 8, 2019, 2:17pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201/47 "2019-10-08T14:17:15Z")

</div>

Can you be more specific?

---

<div class="post-metadata">

**Author:** ![abuit01](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@abuit01](https://discuss.elastic.co/u/abuit01)\
**Post date:** [October 8, 2019, 2:29pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201/48 "2019-10-08T14:29:03Z")

</div>

For example, if I want to enter kibana by 192.168.10.5:5601, I would access the kibana interface directly without a login process. I require that before loading the kibana interface, a username and password is requested to access the tool.

---

<div class="post-metadata">

**Author:** ![mattkime](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mattkime/32/43522_2.png) [@mattkime](https://discuss.elastic.co/u/mattkime)\
**Post date:** [October 8, 2019, 2:58pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201/49 "2019-10-08T14:58:06Z")

</div>

Unfortunately thats not something we support but you're welcome to figure out a solution that works for you.

---

<div class="post-metadata">

**Author:** ![alex\_polisevschi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_polisevschi/32/52431_2.png) [@alex\_polisevschi](https://discuss.elastic.co/u/alex_polisevschi)\
**Post date:** [October 9, 2019, 4:42pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201/50 "2019-10-09T16:42:22Z")

</div>

The security settings come with elasticsearch (xpack plugin), but as far as I know it's only available with a license.

Once you enable security in elasticsearch, kibana will request login credentials.

---

<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:** [November 6, 2019, 4:42pm UTC](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201/51 "2019-11-06T16:42:33Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/problem-accessing-kibana-through-the-browser/202201.md?page=2)
