# Can't log in to Kibana

**URL:** <https://discuss.elastic.co/t/cant-log-in-to-kibana/121940>\
**Category:** Kibana\
**Created:** [February 28, 2018, 9:01pm UTC](https://discuss.elastic.co/t/cant-log-in-to-kibana/121940 "2018-02-28T21:01:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zachy](https://avatars.discourse-cdn.com/v4/letter/z/9d8465/32.png) [@zachy](https://discuss.elastic.co/u/zachy)\
**Post date:** [February 28, 2018, 9:01pm UTC](https://discuss.elastic.co/t/cant-log-in-to-kibana/121940/1 "2018-02-28T21:01:34Z")

</div>

I am running an Elasticsearch cluster with 3 nodes. 2 are data nodes and one is the co-ordinating node. There is currently no data being sent to Elasticsearch yet.

I have secured my Elasticsearch cluster with HTTPS and TLS/SSL connection using self-signed certificates.

I am running an instance of Kibana to listen to the co-ordinating node. However when I start up kibana I get this error from my log:

{"type":"log","@timestamp":"2018-02-28T21:00:16Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: https://:9200/"}

I can visit the log in page for Kibana and get this error message: "Login is currently disabled. Administrators should consult the Kibana logs for more details."

As a result I am unable to log in. In my elasticsearch.yml and kibana.yml i have set my user and pass to be the same (elastic and changeme)

Any help would be appreciated!

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [March 1, 2018, 7:17pm UTC](https://discuss.elastic.co/t/cant-log-in-to-kibana/121940/2 "2018-03-01T19:17:08Z")

</div>

> Login is currently disabled

So it sounds like you're trying to use the X-Pack security feature. Usually when Kibana shows that message, it's because it can't talk to Elasticsearch or you have an invalid license. Based on the log message you posted, it seems like you're dealing with the former.

Interestingly, there's no hostname in the log output. Are you setting a custom hostname in the kibana.yml? And can you share the other settings you've got in there (without the security keys or any other sensitive data)?

---

<div class="post-metadata">

**Author:** ![zachy](https://avatars.discourse-cdn.com/v4/letter/z/9d8465/32.png) [@zachy](https://discuss.elastic.co/u/zachy)\
**Post date:** [March 1, 2018, 7:34pm UTC](https://discuss.elastic.co/t/cant-log-in-to-kibana/121940/4 "2018-03-01T19:34:20Z")

</div>

@Joe_Fleming

Regarding the log message, it does show the hostname. I just blanked it out for privacy. So it should read something like "Unable to revive connection: https://\<\<_hostname_\>\>:9200"

Here is what I got in my kibana.yml

server.name: kibana  
server.host: "0.0.0.0"  
elasticsearch.url: "https://\<\<_hostname_\>\>:9200"  
elasticsearch.username: "{{ kibana\_username }}"  
elasticsearch.password: "{{ kibana\_password }}"

{{ kibana\_username }} and {{ kibana\_password }} resolves to elastic and changeme respectively.

---

<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:** [March 29, 2018, 7:34pm UTC](https://discuss.elastic.co/t/cant-log-in-to-kibana/121940/5 "2018-03-29T19:34:30Z")

</div>

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