# How to connect Kibana to Elasticsearch when http ssl is enabled

**URL:** <https://discuss.elastic.co/t/how-to-connect-kibana-to-elasticsearch-when-http-ssl-is-enabled/167827>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [February 11, 2019, 10:51am UTC](https://discuss.elastic.co/t/how-to-connect-kibana-to-elasticsearch-when-http-ssl-is-enabled/167827 "2019-02-11T10:51:36Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![li\_jessen2016](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/li_jessen2016/32/38817_2.png) [@li\_jessen2016](https://discuss.elastic.co/u/li_jessen2016)\
**Post date:** [February 19, 2019, 6:52am UTC](https://discuss.elastic.co/t/how-to-connect-kibana-to-elasticsearch-when-http-ssl-is-enabled/167827/21 "2019-02-19T06:52:21Z")

</div>

I see where the issue is. I set `server.ssl.certificate` and `server.ssl.key` in kibana.yml, which, according to online documents, is equal to setting `xpack.security.secureCookies` to true, whose default value is false.  
Then when I comment these two settings, which means `xpack.security.secureCookies` is set to false, such a warning disappears and the log on window comes out instead.

---

<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 19, 2019, 6:52am UTC](https://discuss.elastic.co/t/how-to-connect-kibana-to-elasticsearch-when-http-ssl-is-enabled/167827/22 "2019-03-19T06:52:23Z")

</div>

Closed on March 19, 2019, 6:52am UTC

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

[Previous page](https://discuss.elastic.co/t/how-to-connect-kibana-to-elasticsearch-when-http-ssl-is-enabled/167827.md?page=1)