# Unable to connect kibana after encryption?

**URL:** <https://discuss.elastic.co/t/unable-to-connect-kibana-after-encryption/24767>\
**Category:** Kibana\
**Created:** [July 2, 2015, 6:28am UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-after-encryption/24767 "2015-07-02T06:28:36Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)\
**Post date:** [July 6, 2015, 9:38pm UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-after-encryption/24767/23 "2015-07-06T21:38:46Z")

</div>

After reviewing the Shield documentation, it appears that one cannot use self-signed certs in conjunction with Shield: [https://www.elastic.co/guide/en/shield/current/ssl-tls.html](https://www.elastic.co/guide/en/shield/current/ssl-tls.html)

The message you're getting implies that your cert is self-signed, rather than signed by a CA... is that the case?  
`
{"@timestamp":"2015-07-03T08:30:43.887Z","level":"error","node_env":"production","error":"Request error, retrying -- DEPTH_ZERO_SELF_SIGNED_CERT"}
{"@timestamp":"2015-07-03T08:30:43.982Z","level":"warn","message":"Unable to revive connection: https://admin_es:akhilesh@localhost:9200/","node_env":"production"}
{"@timestamp":"2015-07-03T08:30:43.983Z","level":"warn","message":"No living connections","node_env":"production"}
`

---

<div class="post-metadata">

**Author:** ![simianhacker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simianhacker/32/3383_2.png) [@simianhacker](https://discuss.elastic.co/u/simianhacker)\
**Post date:** [July 7, 2015, 12:41am UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-after-encryption/24767/24 "2015-07-07T00:41:03Z")

</div>

Looks like you're trying to use a self signed certificate that either hasn't been signed by your own CA or you haven't included your CA in the Kibana configs.

---

<div class="post-metadata">

**Author:** ![Akhilesh\_Anb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akhilesh_anb/32/4343_2.png) [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)\
**Post date:** [July 7, 2015, 5:16am UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-after-encryption/24767/25 "2015-07-07T05:16:43Z")

</div>

yes, im getting the same error as self-signed... I generated the CA as per that link only...

---

<div class="post-metadata">

**Author:** ![Akhilesh\_Anb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akhilesh_anb/32/4343_2.png) [@Akhilesh\_Anb](https://discuss.elastic.co/u/Akhilesh_Anb)\
**Post date:** [July 9, 2015, 9:15am UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-after-encryption/24767/26 "2015-07-09T09:15:07Z")

</div>

I included the ca certificate in kibana configuration also.. still not working

---

<div class="post-metadata">

**Author:** ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)\
**Post date:** [July 9, 2015, 2:00pm UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-after-encryption/24767/27 "2015-07-09T14:00:57Z")

</div>

Are you sure you signed the certificate with the CA you configured? Our theory based on the error message you are receiving is that while the CA exists, the certificate you are using is not signed with it.

---

<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 6, 2017, 2:16pm UTC](https://discuss.elastic.co/t/unable-to-connect-kibana-after-encryption/24767/28 "2017-07-06T14:16:44Z")

</div>

Closed on July 6, 2017, 2:16pm UTC



[Previous page](https://discuss.elastic.co/t/unable-to-connect-kibana-after-encryption/24767.md?page=1)
