'"
]
}
[2023-03-23T20:20:27.596+00:00][55850][4004][app-server][WARN]: [pre-flight] Failed to connect to Elasticsearch backend. Make sure it is running and healthy.
```
---
### Author:  [@joemcelroy](https://discuss.elastic.co/u/joemcelroy)
#### Post date: [March 24, 2023, 8:08am UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/2 "2023-03-24T08:08:38Z")
is Elasticsearch running on https? From your configuration, looks like you're configured to use **http** ://127.0.0.1:9200 for elasticsearch.
---
### Author:  [@Neil\_Maffitt](https://discuss.elastic.co/u/Neil_Maffitt)
#### Post date: [March 24, 2023, 2:16pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/3 "2023-03-24T14:16:17Z")
Yep you are correct, sorry. I have updated the post to https and restarted. Getting same error but now request URL is [https://127.0.0.1:9200](https://127.0.0.1:9200). I have been working on this for some time now and have tried many things all have failed. I am assuming alot of people are successfuly running EP-8.6.2 without these issues. Thank you for the quick response.
---
### Author:  [@Sander\_Philipse](https://discuss.elastic.co/u/Sander_Philipse)
#### Post date: [March 27, 2023, 3:31pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/4 "2023-03-27T15:31:09Z")
This could be a number of issues, so it's hard to tell without a little more information. How are you running Enterprise Search and Elasticsearch? Are they in a Docker setup, or running just on your local machine as binaries?
One suggestion that might work: have you tried using [https://localhost:9200](https://localhost:9200) as the elasticsearch.host in your enterprise-search.yml?
---
### Author:  [@joemcelroy](https://discuss.elastic.co/u/joemcelroy)
#### Post date: [March 27, 2023, 4:06pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/5 "2023-03-27T16:06:16Z")
Are there any exceptions in the logs? Double check you have followed the SSL cert steps. Its a self signed cert thats created by Elasticsearch docker.
---
### Author:  [@neil.maffitt](https://discuss.elastic.co/u/neil.maffitt)
#### Post date: [March 29, 2023, 3:44pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/6 "2023-03-29T15:44:58Z")
This is not a docker install. The is a on prem red hat server. Tring to get Elastic Search 8.6.2 and Enterprise Search 8.6.2 running on the same box. Elastic Search 8.6.2 is running no problems using curl commands have put-post-get get data
example return data I added
curl --cacert /etc/elasticsearch/certs/http\_ca.crt -u elastic:password -X GET "[https://localhost:9200/index-name/\_search?pretty=true&q=\*:](https://localhost:9200/index-name/_search?pretty=true&q=*:)\*"
Have try localhost as suggested no change.
Is Kibana required for Enterprise Search 8.6.2 to run saw that as prerequisite somewhere Kibana not installed
---
### Author:  [@neil.maffitt](https://discuss.elastic.co/u/neil.maffitt)
#### Post date: [March 29, 2023, 3:51pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/7 "2023-03-29T15:51:27Z")
Elastic search http\_ca.crt was creates and works no problem with curl command.
I have this in the enterprise search yml file now
allow\_es\_settings\_modification:true
```auto
elasticsearch.host:https://localhost:9200
elasticsearch.username:elastic
elasticsearch.password:password
elasticsearch.ssl.enabled:true
elasticsearch.ssl.certificate_authority:/etc/elasticsearch/certs/http_ca.crt
```
Still not working.
thank you for response
---
### Author:  [@Sander\_Philipse](https://discuss.elastic.co/u/Sander_Philipse)
#### Post date: [March 29, 2023, 4:00pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/8 "2023-03-29T16:00:06Z")
Yes, Kibana is required to be able to run Enterprise Search, see:
> **[Run Enterprise Search server using downloads (packages) | Elastic Enterprise...](https://www.elastic.co/guide/en/enterprise-search/current/installation.html)**
What is the exact error you're getting after these changes?
---
### Author:  [@neil.maffitt](https://discuss.elastic.co/u/neil.maffitt)
#### Post date: [March 29, 2023, 5:38pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/9 "2023-03-29T17:38:04Z")
So enterprise should work without kibana?
In ep yml I have this
elasticsearch.ssl.certificate\_authority: /etc/elasticsearch/certs/http\_ca.crt
Getting this error
```auto
Invalid config file (/usr/share/enterprise-search/config/enterprise-search.yml):
The setting '#/elasticsearch/ssl/certificate_authority' is not valid: error reading file '/etc/elasticsearch/certs/http_ca.crt'
```
With CURL command works same path to http\_ca.crt and user elastic : password
```auto
curl --cacert /etc/elasticsearch/certs/http_ca.crt -u elastic: https://localhost:9200
{
"name" : "rofccs901a",
"cluster_name" : "elasticsearch",
"cluster_uuid" : "uS1qTEERSJmATh40KAV-Cw",
"version" : {
"number" : "8.6.2",
"build_flavor" : "default",
"build_type" : "rpm",
"build_hash" : "2d58d0f136141f03239816a4e360a8d17b6d8f29",
"build_date" : "2023-02-13T09:35:20.314882762Z",
"build_snapshot" : false,
"lucene_version" : "9.4.2",
"minimum_wire_compatibility_version" : "7.17.0",
"minimum_index_compatibility_version" : "7.0.0"
},
"tagline" : "You Know, for Search"
}
```
---
### Author:  [@Sander\_Philipse](https://discuss.elastic.co/u/Sander_Philipse)
#### Post date: [March 29, 2023, 6:05pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/10 "2023-03-29T18:05:01Z")
You do need to run Kibana to run Enterprise Search. It is a requirement.
To set up your certificate authority for Enterprise Search, you need to create a Java KeyStore. We’ve documented how to do that here:
[https://www.elastic.co/guide/en/enterprise-search/current/configure-ssl-tls.html](https://www.elastic.co/guide/en/enterprise-search/current/configure-ssl-tls.html)
---
### Author:  [@neil.maffitt](https://discuss.elastic.co/u/neil.maffitt)
#### Post date: [March 29, 2023, 6:23pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/11 "2023-03-29T18:23:52Z")
ok I will setup Kibana
I do have a java key store and have it set in the yml file
ent\_search.ssl.keystore.path: /usr/share/enterprise-search/config/JavaKeystrore.jks
So there must be an order to the start up/shut down
Startup
Elastic Search - Kibana - Enterprise Search
Shut down
Enterprise Search - Kibana - Elastic Search
---
### Author:  [@neil.maffitt](https://discuss.elastic.co/u/neil.maffitt)
#### Post date: [April 2, 2023, 7:21pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/12 "2023-04-02T19:21:40Z")
Ok kibana installed and running good
Java keystore with a CA cert in it create per link up above
Error says
"Failed to connect to Elasticsearch backend. Make sure it is running and healthy."
Elasticsearch IS running and healthy and Enterprise yml has correct es user/pwd
kibana.yml lines added
```auto
enterpriseSearch.host: https://server.host.edu:3002
enterpriseSearch.ssl.verificationMode: certificate
enterpriseSearch.ssl.certificateAuthorities: /usr/share/enterprise-search/config/server_ca_w_chain.cer
```
Lines added to enterprise.yml
```auto
ent_search.ssl.enabled: true
ent_search.ssl.keystore.path: /usr/share/enterprise-search/config/server.jks
ent_search.ssl.keystore.password: password
ent_search.ssl.keystore.key_password: password
ent_search.external_url: https://server.host.edu:3002
```
ERROR MESSAGE
```auto
"exception": "/usr/share/enterprise-search/lib/war/lib/middleware/request_logging_middleware.class:55: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target (Faraday::ClientError)\n",
"duration": 25.6,
"stack": [
```
FULL ERROR MESSAGE
```auto
[2023-04-02T19:07:04.634+00:00][80952][4004][app-server][WARN]: [pre-flight] Failed to connect to Elasticsearch backend. Make sure it is running and healthy.
[2023-04-02T19:07:04.634+00:00][80952][4004][app-server][INFO]: [pre-flight] Error: /usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/elasticsearch_checks.class:179: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target (Faraday::ClientError)
[2023-04-02T19:07:09.667+00:00][80952][4004][es][DEBUG]: {
"request": {
"url": "https://localhost:9200/",
"method": "get",
"headers": {
"Authorization": "[FILTERED]",
"Content-Type": "application/json",
"x-elastic-product-origin": "enterprise-search",
"User-Agent": "Faraday v1.10.2"
},
"params": null,
"body": null
},
"exception": "/usr/share/enterprise-search/lib/war/lib/middleware/request_logging_middleware.class:55: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target (Faraday::ClientError)\n",
"duration": 25.6,
"stack": [
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/elasticsearch.class:651:in `block in get_raw'",
"/usr/share/enterprise-search/lib/war/lib/apm_helpers.class:41:in `es_action_instrument'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/elasticsearch.class:749:in `instrument'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/elasticsearch.class:650:in `get_raw'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/elasticsearch_checks.class:134:in `check_es_connection_with_retries!'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/elasticsearch_checks.class:32:in `check_es_connection!'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/elasticsearch_checks.class:19:in `block in run!'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/elasticsearch_checks.class:18:in `run!'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/elasticsearch_checks.class:14:in `run!'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo.class:291:in `configure_elasticsearch!'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo.class:270:in `configure!'",
"/usr/share/enterprise-search/lib/war/config/application.class:20:in `'",
"/usr/share/enterprise-search/lib/war/config/application.rb:1:in `'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/cli/command.class:36:in `initialize'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/cli/command.class:10:in `new'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/cli/command.class:10:in `run_and_exit'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/cli.class:148:in `run_supported_command'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/cli.class:130:in `run_command'",
"/usr/share/enterprise-search/lib/war/shared_togo/lib/shared_togo/cli.class:112:in `run!'",
"bin/enterprise-search-internal:15:in `'"
]
}
```
---
### Author:  [@Sander\_Philipse](https://discuss.elastic.co/u/Sander_Philipse)
#### Post date: [April 3, 2023, 8:13am UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/13 "2023-04-03T08:13:37Z")
Hi @neil.maffitt, this error message tells me something is wrong with the keystore you generated:
> PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target (Faraday::ClientError)
I can't help you there, other than to point at the documentation to create a Java keystore: [Configure SSL/TLS | Enterprise Search documentation [8.11] | Elastic](https://www.elastic.co/guide/en/enterprise-search/current/configure-ssl-tls.html)
You may want to try the keytool inside [the Enterprise Search Docker image](https://www.elastic.co/guide/en/enterprise-search/current/docker.html) we provide, so we can be sure version mismatches aren't causing issues.
---
### Author:  [@neil.maffitt](https://discuss.elastic.co/u/neil.maffitt)
#### Post date: [April 3, 2023, 2:11pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/14 "2023-04-03T14:11:00Z")
Because "PKIX path building" failed is the error I have been battling all along (see original post) I followed "Configure SSL/TLS | Elastic Enterprise Search documentation [8.7] | Elastic
[/quote]" document closely and documented step by step.
Steps:
```auto
Generate private key
openssl genrsa -out filename.private.key 2048
Generate CSR file for SSL Certificate from setigo
openssl req -new -key filename.private.key -out filename.csr -subj '/CN=data/OU=data IT/O=data/L=data/ST=data/C=data'
Upload CSR to CA
Download Certificate mv (w/ chain), PEM encoded from CA
filenameu_ca_w_chain.cer
Generate p12 file with Certificate from CA
openssl pkcs12 -export -in filename_ca_w_chain.cer -inkey filename.private.key -out filename.p12 -name ent-search
Generate Java keystore file
keytool -importkeystore -destkeystore filename.jks -srckeystore filename.p12 -srcstoretype PKCS12 -storepass password -srcstorepass password
Optional view jks file
keytool -list -v -keystore rofccs901a.mayo.edu.jks
Alias name: ent-search
Creation date: Mar 30, 2023
Entry type: PrivateKeyEntry
Valid from: Wed Mar 29 19:00:00 CDT 2023 until: Fri Mar 29 18:59:59 CDT 2024
Certificate fingerprints:
SHA1: 88:70:C7:0E:59:0E:AB:DE:D4:53:79:C0:42:AF:63:63:C1:C6:F0:91
SHA256: EC:8D:93:E9:69:57:7A:99:A1:5C:8F:16:87:D5:DD:5A:2A:AA:32:E4:CE:63:FD:A8:8F:11:D2:40:17:83:25:C3
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Files created and used
filename.private.key
filename.csr
filename_ca_w_chain.cer
filename.p12
filename.jks
```
Please advise if you see a problem. Thanks
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 1, 2023, 2:11pm UTC](https://discuss.elastic.co/t/enterprise-search-not-starting-new-install-of-8-6-2/328394/15 "2023-05-01T14:11:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.