# Enable HTTPS in kibana: Something went wrong
**URL:** https://discuss.elastic.co/t/enable-https-in-kibana-something-went-wrong/236352
**Category:** Elastic Security
**Created:** [June 9, 2020, 1:53pm UTC](https://discuss.elastic.co/t/enable-https-in-kibana-something-went-wrong/236352 "2020-06-09T13:53:53Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@elisavet](https://discuss.elastic.co/u/elisavet)
#### Post date: [June 9, 2020, 1:53pm UTC](https://discuss.elastic.co/t/enable-https-in-kibana-something-went-wrong/236352/1 "2020-06-09T13:53:53Z")
Hi!
I have enabled HTTPS in kibana, but when I connect to the url [https://ip:5601](https://ip:5601) I get an indication that the connection to the site is not secure. Pls see the image.
Why does this happen? What can I do to resolve it?
Thank you,
Elisavet
---
### Author:  [@Xavier\_Mouligneau](https://discuss.elastic.co/u/Xavier_Mouligneau)
#### Post date: [June 9, 2020, 7:05pm UTC](https://discuss.elastic.co/t/enable-https-in-kibana-something-went-wrong/236352/2 "2020-06-09T19:05:24Z")
Hi Elisavet,
can you try this advice from this topic [How to enable HTTPS for kibana?](https://discuss.elastic.co/t/how-to-enable-https-for-kibana/124226/2) ?
Best,
Xavier
---
### Author:  [@Frank\_Hassanabad](https://discuss.elastic.co/u/Frank_Hassanabad)
#### Post date: [June 10, 2020, 5:03am UTC](https://discuss.elastic.co/t/enable-https-in-kibana-something-went-wrong/236352/3 "2020-06-10T05:03:42Z")
Hi @elisavet,
It looks like perhaps you have setup `https://ip` to be a custom host name that you created with a custom self signed certificate?
You look to be blocking out what the actual host name is but if you click on `Certificate (Invalid)` in that screen shot Chrome will give you more information about why it thinks that certificate is invalid.
Although Chrome is complaining about the certificate being invalid that does not mean you do not have a valid and good `https` connection happening. It just means that Chrome does not trust the certificate from the connection.
Here are some pointers if you did use a self signed certificate with an IP such as 192.168.0.x
- Browsers in general do not like it when people sign their own certificates with an IP. They always want a host name and something to resolve that host name such as DNS, /etc/hosts, etc...
- After using a host name of some type, browsers still will not trust the certificate until you take the additional step of signing the certificate using a Root Certificate Authority or Intermediate Authority and adding that to your browsers trust store.
There's a lot of articles around getting Chrome to trust your self signed certificate from google searching:
[https://www.google.com/search?q=how%20to%20get%20chrome%20to%20trust%20a%20self%20signed%20certificate](https://www.google.com/search?q=how%20to%20get%20chrome%20to%20trust%20a%20self%20signed%20certificate)
But if you are in a large organization it's typically best to ask your IT department for information on how to get a valid certificate for your computer as usually they will assign a host name and can create certificates that are already trusted for that particular host name.
Let us know how it goes! Good luck. ☘
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 4, 2022, 8:01am UTC](https://discuss.elastic.co/t/enable-https-in-kibana-something-went-wrong/236352/4 "2022-11-04T08:01:45Z")