# Kibana server is not ready yet, error : Unable to get issuer certificate
**URL:** https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-error-unable-to-get-issuer-certificate/313218
**Category:** Kibana
**Tags:** elastic-stack-security
**Created:** [August 30, 2022, 6:53am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-error-unable-to-get-issuer-certificate/313218 "2022-08-30T06:53:18Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Florian-LB](https://discuss.elastic.co/u/Florian-LB)
#### Post date: [August 30, 2022, 6:53am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-error-unable-to-get-issuer-certificate/313218/1 "2022-08-30T06:53:18Z")
Hello,
I’ve been struggling for some time with the SSL configuration of Kibana.
I need to set the elasticsearch.ssl.verificationMode on "full" or on "certificate" but Kibana is only working in "none".
When I start the service I get the following error :
“Unable to retrieve version information from Elasticsearch nodes. Unable to get issuer certificate.”
I must censor some parts of the configurations.
I change the certs for the ones from my company.
I’m working on the version 8.3.2
The system isn’t allowed to connect to the Internet for security reasons.
Here are the configuration of Elasticsearch and Kibana :
elasticsearch.yml :
```auto
cluster.name: " *******"
node.name: " ******* -1"
path.data: /elk/elasticsearch/data
path.logs: /elk/elasticsearch/log
http.port: ****
xpack.security.enabled: true
xpack.security.enrollment.enabled: true
xpack.security.http.ssl:
enabled: true
keystore.path: /etc/elasticsearch/certs/http.p12
xpack.security.transport.ssl:
enabled: true
verification_mode: certificate
keystore.path: /etc/elasticsearch/certs/elastic-certificates.p12
truststore.path: /etc/elasticsearch/certs/ *********.p12
cluster.initial_master_nodes: ["ELK"]
http.host: 0.0.0.0
xpack.monitoring.collection.enabled: true
```
kibana.yml :
```auto
server.port: ****
server.host: 0.0.0.0
server.name: *******
server.ssl.certificate: "/etc/kibana/certs/kibana-server.crt"
server.ssl.key: "/etc/kibana/certs/kibana-server.key"
server.ssl.enabled: true
elasticsearch.hosts: ["https:// ***.***. ***.*** : ****"]
elasticsearch.serviceAccountToken: " *************************************"
elasticsearch.ssl.certificateAuthorities: ["/etc/kibana/certs/elasticsearch-ca.pem"]
elasticsearch.ssl.verificationMode: full
logging.appenders.file.type: file
logging.appenders.file.fileName: /elk/kibana/log/kibana.log
logging.appenders.file.layout.type: json
logging.root.appenders: [default, file]
path.data: /elk/kibana/data
pid.file: /run/kibana/kibana.pid
```
I’m a bit new to Elastic especially to the SSL part so the solution to my problem might be simple but I don’t see it. I tried solutions from previous topics but they didn't work.
Thanks.
---
### Author:  [@Yang\_Wang](https://discuss.elastic.co/u/Yang_Wang)
#### Post date: [September 1, 2022, 1:38am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-error-unable-to-get-issuer-certificate/313218/2 "2022-09-01T01:38:29Z")
Your kibana is configured to trust
```auto
elasticsearch.ssl.certificateAuthorities: ["/etc/kibana/certs/elasticsearch-ca.pem"]
```
Is this the CA that is used to sign the following on the ES side
```auto
xpack.security.http.ssl:
enabled: true
keystore.path: /etc/elasticsearch/certs/http.p12
```
You said
> I change the certs for the ones from my company.
So it is possible that you HTTP cert is not signed by the above CA and hence not trusted by Kibana.
---
### Author:  [@Florian-LB](https://discuss.elastic.co/u/Florian-LB)
#### Post date: [September 1, 2022, 6:47am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-error-unable-to-get-issuer-certificate/313218/3 "2022-09-01T06:47:47Z")
Yes, the CA was used to sign the http cert.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 29, 2022, 6:48am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-error-unable-to-get-issuer-certificate/313218/4 "2022-09-29T06:48:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.