# Can not login on kibana after upgrade to 6.3

**URL:** <https://discuss.elastic.co/t/can-not-login-on-kibana-after-upgrade-to-6-3/136718>\
**Category:** Kibana\
**Created:** [June 20, 2018, 2:50pm UTC](https://discuss.elastic.co/t/can-not-login-on-kibana-after-upgrade-to-6-3/136718 "2018-06-20T14:50:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lsy](https://avatars.discourse-cdn.com/v4/letter/l/b2d939/32.png) [@lsy](https://discuss.elastic.co/u/lsy)\
**Post date:** [June 20, 2018, 2:50pm UTC](https://discuss.elastic.co/t/can-not-login-on-kibana-after-upgrade-to-6-3/136718/1 "2018-06-20T14:50:42Z")

</div>

The previous version I used was 6.24.  
After I upgraded the elasticsearch and kibana to 6.3, the login is disable( can not input the username and password).

When I removed `xpack.security.enabled: true` in the elasticsearch.yml, It still don't work.

The only way enter the kibana is :  
removed `xpack.security.enabled: true` in the elasticsearch.yml and  
change the `elasticsearch.username` and `elasticsearch.password` to `elasticsearch.username: elastic` and `elasticsearch.password: changeme`.  
However, the Login page disappeared after I did that.

it's weird because I used `bin/elasticsearch-setup-passwords interactive` to change all of ELK's password when I used 6.24 version.

How could I login on the kibana when I use xpack.security?

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [June 21, 2018, 2:21am UTC](https://discuss.elastic.co/t/can-not-login-on-kibana-after-upgrade-to-6-3/136718/2 "2018-06-21T02:21:55Z")

</div>

There's lots of things that might cause this, and it's not clear from your post exactly how you upgraded and what settings you are running with.

Regarding your upgrade:

- How did you perform your upgrade?
- Are you using the same data directory as you used on 6.2.4?
- Did you change any configuration?

Can you connect to the Elasticsearch server using curl (or a similar tool)?

- Does `curl -uelastic http://localhost:9200/` work?

Check `GET /_xpack` on your elasticsearch server.

- what license type is it reporting?
- what does it report for the `enabled` & `allowed` states on the security feature?

---

<div class="post-metadata">

**Author:** ![lsy](https://avatars.discourse-cdn.com/v4/letter/l/b2d939/32.png) [@lsy](https://discuss.elastic.co/u/lsy)\
**Post date:** [June 21, 2018, 3:21pm UTC](https://discuss.elastic.co/t/can-not-login-on-kibana-after-upgrade-to-6-3/136718/3 "2018-06-21T15:21:00Z")

</div>

1. I used deb to upgrade
2. I use the same data directory
3. I don't change any configuration.
4. the license I use is trial, and security is allowed. But I disabled the security because it's the only way to use kibana.
5. When I input `curl -uelastic http://localhost:9200/`, it required the elastic password. And the result is connection refused

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [June 21, 2018, 11:49pm UTC](https://discuss.elastic.co/t/can-not-login-on-kibana-after-upgrade-to-6-3/136718/4 "2018-06-21T23:49:19Z")

</div>

> [@lsy](#):
>
> When I input `curl -uelastic http://localhost:9200/` , it required the elastic password. And the result is connection refuse

What do the Elasticsearch logs say?

---

<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 19, 2018, 11:49pm UTC](https://discuss.elastic.co/t/can-not-login-on-kibana-after-upgrade-to-6-3/136718/5 "2018-07-19T23:49:26Z")

</div>

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