# ElasticSearch Linux startup failed. Procedure

**URL:** <https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [March 4, 2022, 1:52am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799 "2022-03-04T01:52:57Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![zx\_emo](https://avatars.discourse-cdn.com/v4/letter/z/e19adc/32.png) [@zx\_emo](https://discuss.elastic.co/u/zx_emo)\
**Post date:** [March 4, 2022, 1:52am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/1 "2022-03-04T01:52:57Z")

</div>

Elasticsearch has been deployed to Linux and I have encountered a problem with the certificate signing. After following the steps to resolve these problems, I get an exception when I start Elasticsearch. How do I resolve this problem?

\</\>  
uncaught exception in thread [main]  
org.Elasticsearch.bootstrap.StartupException: org.Elasticsearch.ElasticsearchSecurityException: failed to load SSL configuration [xpack.security.transport.ssl] - the truststore [/usr/software/es/Elasticsearch-8.0.1/config/certs/elastic-stack-ca.p12] does not contain any trusted certificate entries

\</\>  
org.Elasticsearch.ElasticsearchSecurityException: failed to load SSL configuration [xpack.security.transport.ssl] - the truststore [/usr/software/es/Elasticsearch-8.0.1/config/certs/elastic-stack-ca.p12] does not contain any trusted certificate entries  
Likely root cause: org.Elasticsearch.common.ssl.SslConfigException: the truststore [/usr/software/es/Elasticsearch-8.0.1/config/certs/elastic-stack-ca.p12] does not contain any trusted certificate entries

---

<div class="post-metadata">

**Author:** ![casterQ](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/casterq/32/93257_2.png) [@casterQ](https://discuss.elastic.co/u/casterQ)\
**Post date:** [March 4, 2022, 2:42am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/2 "2022-03-04T02:42:08Z")

</div>

you can follow this doc，get your P12 file, and add it in your Elasticsearch.yml

> **[Set up basic security for the Elastic Stack | Elasticsearch Guide \[8.0\] |...](https://www.elastic.co/guide/en/elasticsearch/reference/8.0/security-basic-setup.html#encrypt-internode-communication)**

---

<div class="post-metadata">

**Author:** ![zx\_emo](https://avatars.discourse-cdn.com/v4/letter/z/e19adc/32.png) [@zx\_emo](https://discuss.elastic.co/u/zx_emo)\
**Post date:** [March 4, 2022, 3:08am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/3 "2022-03-04T03:08:57Z")

</div>

Thanks for your help. I'll give it a try

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [March 4, 2022, 3:26am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/4 "2022-03-04T03:26:03Z")

</div>

> [@zx\_emo](#):
>
> certs/elastic-stack-ca.p12] does not contain any trusted certificate entries

You are attempting to use a CA key-pair as a truststore. That doesn't work - the idea of this CA is that it is the key to control your cluster, you usually don't want to have lots of copies of it lying around.

If you follow the docs mentioned above you'll see that the correct setup is:

```auto
xpack.security.transport.ssl.truststore.path: elastic-certificates.p12

```

---

<div class="post-metadata">

**Author:** ![zx\_emo](https://avatars.discourse-cdn.com/v4/letter/z/e19adc/32.png) [@zx\_emo](https://discuss.elastic.co/u/zx_emo)\
**Post date:** [March 4, 2022, 6:58am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/5 "2022-03-04T06:58:16Z")

</div>

Why am I prompted with password error after I have configured the path as instructed in the document?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/c/6c4af38aa9a998eca841311d121f8476b50f9d35.png)

---

<div class="post-metadata">

**Author:** ![zx\_emo](https://avatars.discourse-cdn.com/v4/letter/z/e19adc/32.png) [@zx\_emo](https://discuss.elastic.co/u/zx_emo)\
**Post date:** [March 4, 2022, 6:59am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/6 "2022-03-04T06:59:33Z")

</div>

\</\>  
org.Elasticsearch.bootstrap.StartupException: org.Elasticsearch.ElasticsearchSecurityException: failed to load SSL configuration [xpack.security.transport.ssl] - cannot read configured [PKCS12] keystore (as a truststore) [/usr/software/es/Elasticsearch-8.0.1/config/certs/elastic-certificates.p12] - this is usually caused by an incorrect password; (a keystore password was provided)  
\</\>

---

<div class="post-metadata">

**Author:** ![casterQ](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/casterq/32/93257_2.png) [@casterQ](https://discuss.elastic.co/u/casterQ)\
**Post date:** [March 4, 2022, 7:08am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/7 "2022-03-04T07:08:13Z")

</div>

here you need input the password when you set by `./bin/elasticsearch-certutil cert --ca elastic-stack-ca.p12`

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/a/fa4a132e1a2b619b7cbf9e13aaf663adb6ee3a82.png)

---

<div class="post-metadata">

**Author:** ![zx\_emo](https://avatars.discourse-cdn.com/v4/letter/z/e19adc/32.png) [@zx\_emo](https://discuss.elastic.co/u/zx_emo)\
**Post date:** [March 4, 2022, 8:38am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/8 "2022-03-04T08:38:16Z")

</div>

First of all, thank you for your help. I successfully started ElasticSerarch according to your instructions. However, there was an exception when I started ElasticSerarch

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/4/b4f53d84e8d3db003a0da5481bbe93cea9e1ef9e.png)

---

<div class="post-metadata">

**Author:** ![casterQ](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/casterq/32/93257_2.png) [@casterQ](https://discuss.elastic.co/u/casterQ)\
**Post date:** [March 4, 2022, 9:50am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/9 "2022-03-04T09:50:09Z")

</div>

I think this is a conf error or file problem，maybe you can follow doc try it all over again

---

<div class="post-metadata">

**Author:** ![zx\_emo](https://avatars.discourse-cdn.com/v4/letter/z/e19adc/32.png) [@zx\_emo](https://discuss.elastic.co/u/zx_emo)\
**Post date:** [March 4, 2022, 10:01am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/10 "2022-03-04T10:01:25Z")

</div>

@casterQ Thank you for your comments. I will check them carefully

---

<div class="post-metadata">

**Author:** ![YouveGotMeowxy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/youvegotmeowxy/32/103253_2.png) [@YouveGotMeowxy](https://discuss.elastic.co/u/YouveGotMeowxy)\
**Post date:** [March 20, 2022, 9:47am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/11 "2022-03-20T09:47:30Z")

</div>

I followed the instructions on this page:

[Set up basic security for the Elastic Stack | Elasticsearch Guide [8.1] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.1/security-basic-setup.html)

via logging into the cline of the already running ES container, and everything went well, except upon restart of the container (I'm running ES in Docker) it says:

- today at 4:43:00 AMorg.Elasticsearch.ElasticsearchSecurityException: failed to load SSL configuration [xpack.security.transport.ssl] - cannot read configured [PKCS12] keystore (as a truststore) [/usr/share/Elasticsearch/config/elastic-certificates.p12] - **this is usually caused by an incorrect password; (no password was provided)**

I am guessing that for some reason the saving of the password to the stores didn't persist through restart of the container?

I did follow all of the examples for setting up the container and mounted a volume to store data. My entire volumes section in my compose looks like this (_you can see the data volume as the 4th mounted volume_):

```auto
      volumes:
        - '/opt/docker/configs/elasticsearch/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml:rw' # Config
        - '/opt/docker/configs/elasticsearch/config/elastic-certificates.p12:/usr/share/elasticsearch/config/elastic-certificates.p12:rw' # Cert
        - '/mnt/e/Docker/Logs/elasticsearch:/usr/share/elasticsearch/logs:rw' # Logs
        - '/mnt/e/Docker/Elasticsearch/data:/usr/share/elasticsearch/data:rw' # Data
        - '/mnt/e/Docker/Elasticsearch/backup:/usr/share/elasticsearch/backup:rw' # Backup

```

How does one fix this issue?

---

<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:** [April 17, 2022, 9:47am UTC](https://discuss.elastic.co/t/elasticsearch-linux-startup-failed-procedure/298799/12 "2022-04-17T09:47:33Z")

</div>

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