# 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:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\
**Post date:** [February 18, 2019, 4:08pm UTC](https://discuss.elastic.co/t/how-to-connect-kibana-to-elasticsearch-when-http-ssl-is-enabled/167827/17 "2019-02-18T16:08:27Z")

</div>

> [@li\_jessen2016](#):
>
> You mean that the kibana don't need to set `server.ssl.enabled:true` to have secured connection to elasticsearch via `https://elasticsearch-hostname:9200` ? Yes, it's true.

I'm glad we can finally agree on something 🙂

> [@li\_jessen2016](#):
>
> Yes, it's true. But under this circumstance, when you use browser to connect to kibana server via `http:kibana-hostname:5601` , it would display that "a secured connection is required for log in".

Can we also agree that this has _NOTHING_ to do with how kibana communicates with Elasticsearch and as such with the `xpack.security. enabled: true` in or the `elasticsearch.url` settings ?

The "circumstance" you mention is the missing `server.ssl.enabled:true` and this error only has to do with that. I explained to you why this error occurs in my answer in [What does "A secure connection is required for log in" mean? - #2 by ikakavas](https://discuss.elastic.co/t/what-does-a-secure-connection-is-required-for-log-in-mean/168355/2)

> [@li\_jessen2016](#):
>
> So from a client point of view, besides the browser, do you have any other ways to implement the functions of kibana, say, visualization of data search result?

There is no need for provoking questions. The only thing we have been trying to explain to you is that the way that Kibana communicates with Elasticsearch (via TLS on `https://elasticsearch-hostname:9200` or plain http on `http://elasticsearch-hostname:9200` ) has _NOTHING_ to do with the error above. Can we just agree upon that and move on ? 🙂

---

_[View the full topic](https://discuss.elastic.co/t/how-to-connect-kibana-to-elasticsearch-when-http-ssl-is-enabled/167827)._