# Elastic user works for ES API but not Kibana **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-security\ **Created:** [January 31, 2022, 2:34am UTC](https://discuss.elastic.co/t/elastic-user-works-for-es-api-but-not-kibana/295792 "2022-01-31T02:34:46Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![shlant](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@shlant](https://discuss.elastic.co/u/shlant)\ **Post date:** [January 31, 2022, 2:34am UTC](https://discuss.elastic.co/t/elastic-user-works-for-es-api-but-not-kibana/295792/1 "2022-01-31T02:34:46Z")
I have set up ES and Kibana as per [Secure Elasticsearch with TLS encryption and role-based access control | Elastic Blog](https://www.elastic.co/blog/getting-started-with-elasticsearch-security) I can hit /\_cluster/health with both elastic and kibana users. When I try and log in on the kibana UI, neither of those users work. I can't find anything in the logs other than: ```auto This Kibana instance defines an older template version (6081699) than is currently in Elasticsearch (6082399). Because of the potential for non-backwards compatible changes, this Kibana instance will only be able to claim scheduled tasks with \"kibana.apiVersion\ ``` I banged my head for a while trying to do something about that but from what I have read, it's not a major issue. On the ES side, I can see that kibana is connecting to ES: ```auto [2022-01-31T02:02:56,901][INFO][o.e.c.m.MetaDataIndexTemplateService] [52.54.64.234] adding template [kibana_index_template:.kibana] for index patterns [.kibana] [2022-01-31T02:02:56,919][INFO][o.e.c.r.a.AllocationService] [52.54.64.234] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.kibana_1][0]] ...]). [2022-01-31T02:02:59,780][INFO][o.e.c.m.MetaDataIndexTemplateService] [52.54.64.234] adding template [kibana_index_template:.kibana] for index patterns [.kibana] ``` Elasticsearch.yml: ```auto bootstrap.memory_lock: false cluster.name: dev discovery.zen.ping.unicast.hosts: elasticsearch-dev-1.node.consul,elasticsearch-dev-2.node.consul,elasticsearch-dev-3.node.consul network.bind_host: 0.0.0.0 network.publish_host: 10.0.2.139 node.data: true node.master: true node.name: x.x.x.x #################################### Paths #################################### # Path to directory containing configuration (this file and logging.yml): path.data: /var/lib/elasticsearch path.logs: /var/log/elasticsearch action.auto_create_index: true xpack.security.enabled: true xpack.security.transport.ssl.enabled: true xpack.security.transport.ssl.verification_mode: "certificate" xpack.security.transport.ssl.key: "/etc/elasticsearch/certs/internal_key.pem" xpack.security.transport.ssl.certificate: "/etc/elasticsearch/certs/internal_cert.pem" xpack.security.transport.ssl.certificate_authorities: "/etc/elasticsearch/certs/internal_ca.pem" ``` Kibana.yml: ```auto server.port: 5601 server.host: "0.0.0.0" elasticsearch.url: http://elasticsearch-dev-1.node.consul:9200 kibana.index: ".kibana" elasticsearch.username: "kibana" elasticsearch.password: "" ``` Any idea why I can't log into kibana with credentials that are clearly valid? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 31, 2022, 3:04am UTC](https://discuss.elastic.co/t/elastic-user-works-for-es-api-but-not-kibana/295792/2 "2022-01-31T03:04:33Z")
> [@shlant](#): > > When I try and log in on the kibana UI, neither of those users work. What do your browser's console tools show as the response? ---
**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:** [January 31, 2022, 3:57am UTC](https://discuss.elastic.co/t/elastic-user-works-for-es-api-but-not-kibana/295792/3 "2022-01-31T03:57:57Z")
> [@shlant](#): > > On the ES side, I can see that kibana is connecting to ES: > > ```auto > [2022-01-31T02:02:56,901][INFO][o.e.c.m.MetaDataIndexTemplateService] [52.54.64.234] adding template [kibana_index_template:.kibana] for index patterns [.kibana] > [2022-01-31T02:02:56,919][INFO][o.e.c.r.a.AllocationService] [52.54.64.234] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.kibana_1][0]] ...]). > [2022-01-31T02:02:59,780][INFO][o.e.c.m.MetaDataIndexTemplateService] [52.54.64.234] adding template [kibana_index_template:.kibana] for index patterns [.kibana] > > ``` Those log messages only tell you that the Kibana index has been created, it doesn't tell you whether Kibana connected to ES ---
**Author:** ![shlant](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@shlant](https://discuss.elastic.co/u/shlant)\ **Post date:** [February 1, 2022, 6:21am UTC](https://discuss.elastic.co/t/elastic-user-works-for-es-api-but-not-kibana/295792/4 "2022-02-01T06:21:41Z")
> [@warkolm](#): > > What do your browser's console tools show as the response? ![Screen Shot 2022-02-01 at 2.20.11 PM](https://us1.discourse-cdn.com/elastic/original/3X/2/5/259fa533b079563fb63a33b2df3567824846b010.png) ---
**Author:** ![shlant](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@shlant](https://discuss.elastic.co/u/shlant)\ **Post date:** [February 1, 2022, 6:28am UTC](https://discuss.elastic.co/t/elastic-user-works-for-es-api-but-not-kibana/295792/5 "2022-02-01T06:28:05Z")
> [@TimV](#): > > Those log messages only tell you that the Kibana index has been created, it doesn't tell you whether Kibana connected to ES How about these? ```auto Jan 28 03:08:40 elasticsearch-dev-1 kibana[11859]: {"type":"log","@timestamp":"2022-01-28T03:08:40Z","tags":["info","migrations"],"pid":11859,"message":"Creating index .kibana_1."} Jan 28 03:08:40 elasticsearch-dev-1 kibana[11859]: {"type":"log","@timestamp":"2022-01-28T03:08:40Z","tags":["info","migrations"],"pid":11859,"message":"Pointing alias .kibana to .kibana_1."} Jan 28 03:08:40 elasticsearch-dev-1 kibana[11859]: {"type":"log","@timestamp":"2022-01-28T03:08:40Z","tags":["info","migrations"],"pid":11859,"message":"Finished in 128ms."} Jan 28 03:08:40 elasticsearch-dev-1 kibana[11859]: {"type":"log","@timestamp":"2022-01-28T03:08:40Z","tags":["listening","info"],"pid":11859,"message":"Server running at http://0.0.0.0:5601"} Jan 28 03:08:40 elasticsearch-dev-1 kibana[11859]: {"type":"log","@timestamp":"2022-01-28T03:08:40Z","tags":["status","plugin:spaces@6.8.16","info"],"pid":11859,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} ``` ---
**Author:** ![shlant](https://avatars.discourse-cdn.com/v4/letter/s/3d9bf3/32.png) [@shlant](https://discuss.elastic.co/u/shlant)\ **Post date:** [February 4, 2022, 5:18am UTC](https://discuss.elastic.co/t/elastic-user-works-for-es-api-but-not-kibana/295792/6 "2022-02-04T05:18:39Z")
bump 🙏 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 4, 2022, 5:19am UTC](https://discuss.elastic.co/t/elastic-user-works-for-es-api-but-not-kibana/295792/7 "2022-03-04T05:19:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.