# Kibana can't startup successfully after enable ssl and xpack in elasticsearch6.7.1 **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-security\ **Created:** [April 20, 2019, 1:39pm UTC](https://discuss.elastic.co/t/kibana-cant-startup-successfully-after-enable-ssl-and-xpack-in-elasticsearch6-7-1/177716 "2019-04-20T13:39:29Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![sunweiconfidence](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@sunweiconfidence](https://discuss.elastic.co/u/sunweiconfidence)\ **Post date:** [April 20, 2019, 1:39pm UTC](https://discuss.elastic.co/t/kibana-cant-startup-successfully-after-enable-ssl-and-xpack-in-elasticsearch6-7-1/177716/1 "2019-04-20T13:39:29Z")
``` my configuration for kibana is below: server.port: 5601 server.host: "0.0.0.0" server.name: "MyPc1" elasticsearch.hosts: ["https://MyPc1:9500"] kibana.index: ".kibana" kibana.defaultAppId: "discover" elasticsearch.username: "elastic" elasticsearch.password: "pass1234" server.ssl.enabled: true elasticsearch.ssl.ca: "C:/ELK/kibana-6.7.1-windows-x86_64/config/certs/MyPc1.crt" server.ssl.key: "C:/ELK/kibana-6.7.1-windows-x86_64/config/certs/MyPc1.key" server.ssl.certificate: "C:/ELK/kibana-6.7.1-windows-x86_64/config/certs/MyPc1.crt" elasticsearch.ssl.certificateAuthorities: ["C:/ELK/kibana-6.7.1-windows-x86_64/config/certs/MyPc1.pem"] elasticsearch.ssl.verificationMode: 'certificate' elasticsearch.requestTimeout: 1000000 i18n.locale: "en" indent preformatted text by 4 spaces xpack.security.enabled: false xpack.security.audit.enabled: false xpack.monitoring.enabled: true xpack.monitoring.elasticsearch.hosts: ["https://MyPc1:9500"] xpack.monitoring.elasticsearch.ssl.verificationMode: "certificate" xpack.monitoring.elasticsearch.ssl.certificateAuthorities: ["C:/ELK/kibana-6.7.1-windows-x86_64/config/certs/MyPc1.pem"] xpack.security.encryptionKey: "aaaabbbbccccddddeeeeffffgggghhhh" xpack.reporting.encryptionKey: "aaaaaaaabbbbbbbbccccccccdddddddd" I enable ssl in elasticsearch6.7.1, and configure xpack in elasticsearch.yml, xpack i use clause to active trial version,still meet with below error when run kibana.bat in kibana bin folder: ["error","elasticsearch","data"],"pid":4780,"message":"Request error, retrying\nGET https://sunwei:9500/_xpack => self signed certificate in certificate chain"} {"type":"log","@timestamp":"2019-04-20T13:19:30Z","tags":["warning","elasticsearch","data"],"pid":4780,"message":"Unable to revive connection: https://sunwei:9500/"} {"type":"log","@timestamp":"2019-04-20T13:19:30Z","tags":["warning","elasticsearch","data"],"pid":4780,"message":"No living connections"} {"type":"log","@timestamp":"2019-04-20T13:19:30Z","tags":["license","warning","xpack"],"pid":4780,"message":"License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. Error: No Living connections"} {"type":"log","@timestamp":"2019-04-20T13:19:30Z","tags":["status","plugin:xpack_main@6.7.1","error"],"pid":4780,"state":"red","message":"Status changed from red to red - No Living connections","prevState":"red","prevMsg":"Unable to connect to Elasticsearch."} {"type":"log","@timestamp":"2019-04-20T13:19:30Z","tags":["status","plugin:graph@6.7.1","error"],"pid":4780,"state":"red","message":"Status changed from red to red - No Living connections","prevState":"red","prevMsg":"Unable to connect to Elasticsearch."} {"type":"log","@timestamp":"2019-04-20T13:19:30Z","tags":["status","plugin:spaces@6.7.1","error"],"pid":4780,"state":"red","message":"Status changed from red to red - No Living connections","prevState":"red","prevMsg":"Unable to connect to Elasticsearch."} {"type":"log","@timestamp":"2019-04-20T13:19:30Z","tags":["status","plugin:searchprofiler@6.7.1","error"],"pid":4780,"state":"red","message":"Status changed from red to red - No Living connections","prevState":"red","prevMsg":"Unable to connect to Elasticsearch."}[quote="sunweiconfidence, post:1, topic:177716, full:true"] indent preformatted text by 4 spaces ``` ---
**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:** [April 20, 2019, 3:17pm UTC](https://discuss.elastic.co/t/kibana-cant-startup-successfully-after-enable-ssl-and-xpack-in-elasticsearch6-7-1/177716/2 "2019-04-20T15:17:09Z")
Can you please reformat your post using the `` button or ``` to format the logs and configuration snippets? It is really hard to read through this as it is now. You can use the preview panel on the right to make sure it looks ok ---
**Author:** ![sunweiconfidence](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@sunweiconfidence](https://discuss.elastic.co/u/sunweiconfidence)\ **Post date:** [April 20, 2019, 3:36pm UTC](https://discuss.elastic.co/t/kibana-cant-startup-successfully-after-enable-ssl-and-xpack-in-elasticsearch6-7-1/177716/3 "2019-04-20T15:36:43Z")
has format text ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [April 21, 2019, 5:53am UTC](https://discuss.elastic.co/t/kibana-cant-startup-successfully-after-enable-ssl-and-xpack-in-elasticsearch6-7-1/177716/4 "2019-04-21T05:53:26Z")
What does your Elasticsearch config look like? ---
**Author:** ![sunweiconfidence](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@sunweiconfidence](https://discuss.elastic.co/u/sunweiconfidence)\ **Post date:** [April 21, 2019, 1:06pm UTC](https://discuss.elastic.co/t/kibana-cant-startup-successfully-after-enable-ssl-and-xpack-in-elasticsearch6-7-1/177716/5 "2019-04-21T13:06:47Z")
hi, below is my configuration for elasticsearch: cluster.name: mynewes671 node.name: MyPc1 network.host: MyPc1 http.port: 9500 transport.tcp.port: 9501 #action.destructive\_requires\_name: true http.cors.enabled: true http.cors.allow-origin: "\*" node.master: true node.data: true http.cors.allow-headers: Authorization,X-Requested-With,Content-Length,Content-Type http.type: security4 xpack.security.enabled: true xpack.security.http.ssl.enabled: true xpack.security.http.ssl.keystore.path: "certs/MyPc1.p12" xpack.security.http.ssl.truststore.path: "certs/MyPc1.p12" xpack.security.http.ssl.supported\_protocols: TLSv1.2 xpack.monitoring.exporters: id1: type: http host: ["[http://MyPc1:9500](http://MyPc1:9500)"] auth.username: elastic auth.password: pass1234 xpack.security.audit.enabled: true xpack.monitoring.enabled: true xpack.monitoring.collection.cluster.stats.timeout: 30m xpack.monitoring.collection.index.stats.timeout: 30m xpack.monitoring.collection.index.recovery.active\_only: true xpack.monitoring.collection.index.recovery.timeout: 30m xpack.monitoring.history.duration: 3650d indent preformatted text by 4 spaces ---
**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:** [April 22, 2019, 10:02am UTC](https://discuss.elastic.co/t/kibana-cant-startup-successfully-after-enable-ssl-and-xpack-in-elasticsearch6-7-1/177716/6 "2019-04-22T10:02:13Z")
Please take the extra few minutes every time you post to format your posts. You make it difficult for people that might want to try and help you to get to understand what the issue might be. What is the relation between `C:/ELK/kibana-6.7.1-windows-x86_64/config/certs/MyPc1.pem` and `certs/MyPc1.p12` ? Have you exported the `pem` file from the `PKCS#12` container ? And if so, what was the command that you used to do it ? Can you also share the relevant part of your elasticsearch.log ? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 20, 2019, 10:02am UTC](https://discuss.elastic.co/t/kibana-cant-startup-successfully-after-enable-ssl-and-xpack-in-elasticsearch6-7-1/177716/7 "2019-05-20T10:02:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.