# Added corp certs instead of self certs now - "Kibana server is not ready yet"

**URL:** https://discuss.elastic.co/t/added-corp-certs-instead-of-self-certs-now-kibana-server-is-not-ready-yet/295260
**Category:** Kibana
**Tags:** elastic-stack-security
**Created:** [January 24, 2022, 5:17pm UTC](https://discuss.elastic.co/t/added-corp-certs-instead-of-self-certs-now-kibana-server-is-not-ready-yet/295260 "2022-01-24T17:17:03Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![g0nz0](https://avatars.discourse-cdn.com/v4/letter/g/b5e925/32.png) [@g0nz0](https://discuss.elastic.co/u/g0nz0)
#### Post date: [January 24, 2022, 5:17pm UTC](https://discuss.elastic.co/t/added-corp-certs-instead-of-self-certs-now-kibana-server-is-not-ready-yet/295260/1 "2022-01-24T17:17:03Z")

</div>

Hello,

I'm trying to use our own certs with ELK but when I use them instead of the working self certs I get the error "Kibana server is not ready yet" when I go to the website.

With the self certs I just use [https://ipaddress:5601](https://ipaddress:5601)

With the the proper certs I am trying [https://domain.com:5601](https://domain.com:5601)

I can ping the FQDN and also curl it and it says the certificate is valid. I'm wondering if it's my kibana.yaml?

> **[kibanav2 - Pastebin.com](https://pastebin.com/dXNMg9V5)**
>
> Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

Thanks

---

<div class="post-metadata">

### Author: ![grumo35](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grumo35/32/59451_2.png) [@grumo35](https://discuss.elastic.co/u/grumo35)
#### Post date: [January 25, 2022, 9:44am UTC](https://discuss.elastic.co/t/added-corp-certs-instead-of-self-certs-now-kibana-server-is-not-ready-yet/295260/2 "2022-01-25T09:44:39Z")

</div>

How do you curl it ?

Please show what is the error message in your web browser, also you need to configure this in kibana.yml :

```auto
server.ssl.enabled: true
server.ssl.certificate: /etc/kibana/certs/XX.crt
server.ssl.key: /etc/kibana/certs/XX.key

# Needed to make sure the certificate is from a "trusted" issuer 
elasticsearch.ssl.certificateAuthorities: /path/to/corp.crt 

```

You should also put the correct server-name in server.name ( FQDN )

---

<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: [February 22, 2022, 9:44am UTC](https://discuss.elastic.co/t/added-corp-certs-instead-of-self-certs-now-kibana-server-is-not-ready-yet/295260/3 "2022-02-22T09:44:52Z")

</div>

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