# Unable to login to kibana on chrome

**URL:** <https://discuss.elastic.co/t/unable-to-login-to-kibana-on-chrome/96645>\
**Category:** Kibana\
**Created:** [August 10, 2017, 4:30pm UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana-on-chrome/96645 "2017-08-10T16:30:01Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![Stacey\_Gammon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stacey_gammon/32/14025_2.png) [@Stacey\_Gammon](https://discuss.elastic.co/u/Stacey_Gammon)\
**Post date:** [August 31, 2017, 1:36pm UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana-on-chrome/96645/21 "2017-08-31T13:36:39Z")

</div>

Yes, navigating to `http://localhost:5601/api/xpack/v1/info` should bring you first to the login screen, then redirect you to a screen with a JSON object that has some license and login information.

Without being able to reproduce the issue myself, I'm a bit at a loss as to what to try next. I haven't heard of any other reports of logins working on some browsers but not others.

@Brandon_Kobel - maybe you can try to dig in a little bit next week since you've done some of the SSL work? Or @kimjoar - maybe someone on your team would have some more security/login expertise and could give this a look?

---

<div class="post-metadata">

**Author:** ![a5a](https://avatars.discourse-cdn.com/v4/letter/a/a87d85/32.png) [@a5a](https://discuss.elastic.co/u/a5a)\
**Post date:** [August 31, 2017, 4:01pm UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana-on-chrome/96645/22 "2017-08-31T16:01:33Z")

</div>

Hi! Just jumping in here with a suggestion. We have had an issue before that looks very similar, and this was resolved with the fix described here:

> <https://github.com/elastic/kibana/issues/6719#issuecomment-204448145>

Give that a try @samphibian?

-a5a

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [September 1, 2017, 10:44am UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana-on-chrome/96645/23 "2017-09-01T10:44:24Z")

</div>

Hi @samphibian,

I've just posted a question for you at the [issue you filled](https://github.com/elastic/kibana/issues/13505#issuecomment-326549397) . Could you please take a look?

Thanks,  
Oleg

---

<div class="post-metadata">

**Author:** ![parth126](https://avatars.discourse-cdn.com/v4/letter/p/258eb7/32.png) [@parth126](https://discuss.elastic.co/u/parth126)\
**Post date:** [September 3, 2017, 2:11pm UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana-on-chrome/96645/24 "2017-09-03T14:11:28Z")

</div>

@Bargs thanks for the suggestion.

I am facing a similar issue. But in my case the user authentication works when done via a curl request.  
There are no entries corresponding to the failed login attempts using kibana, so I am assuming those requests are not actually reaching elasticsearch.

Any suggestions about what the issue might be?

This issue cropped up only after I had to restart my kibana server. After that no users are being recognised by kibana.

---

<div class="post-metadata">

**Author:** ![samphibian](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@samphibian](https://discuss.elastic.co/u/samphibian)\
**Post date:** [September 5, 2017, 6:48pm UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana-on-chrome/96645/25 "2017-09-05T18:48:58Z")

</div>

Hi @a5a!  
We had cors.allow-origins set to allow the urls that were calling it, but changing that to "\*" allows us to now log in. I haven't had a chance to test the iframe to see if it's still throwing errors or not. When we initially set it up, we would get CORS errors about addresses not being permitted; any idea why we weren't getting any errors other than unauthorized?

---

<div class="post-metadata">

**Author:** ![a5a](https://avatars.discourse-cdn.com/v4/letter/a/a87d85/32.png) [@a5a](https://discuss.elastic.co/u/a5a)\
**Post date:** [September 15, 2017, 2:34pm UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana-on-chrome/96645/26 "2017-09-15T14:34:23Z")

</div>

@samphibian Are you asking about why you weren't getting other kinds of errors? What other kinds of errors were you expecting?

---

<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:** [October 13, 2017, 2:34pm UTC](https://discuss.elastic.co/t/unable-to-login-to-kibana-on-chrome/96645/27 "2017-10-13T14:34:38Z")

</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/unable-to-login-to-kibana-on-chrome/96645.md?page=1)
