Attempted to resurrect connection to dead ES instance, but got an error. java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors

I put the .cert file in elasticsearch and logstash .
My elasticsearch-kibana connection is working fins with ssl config.
But wil logstash ssl config it is not somehow connecting or contacting elasticsearch instance.

I have put my .cert file in /etc/ss/certs/ path .

Below is the error i am facing and logstash.yml and my output part of logstash.conf file.

[2019-09-27T20:31:07,219][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"https://logstash_system:xxxxxx@application.name.com:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [https://logstash_system:xxxxxx@application.name.com:9200/][Manticore::ClientProtocolException] PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors"}

http.host: "0.0.0.0"
xpack.monitoring.enabled: true
xpack.monitoring.elasticsearch.username: logstash_system
xpack.monitoring.elasticsearch.password: welcome123
xpack.monitoring.elasticsearch.hosts: [ 'https://application.name:9200' ]
xpack.monitoring.elasticsearch.ssl.certificate_authority: '/etc/ssl/certs/xyz.crt'

elasticsearch {
index => "%{name}-info-logs"
ssl => true
cacert => '/etc/ssl/certs/xyz.crt'
sniffing => false
user => logstash_system
password => welcome123
hosts => ["https://application.name:9200"]
}

I am not understanding , why it says that ? If i ping the same :
logstash_https://logstash_system:welcome123@application.name:9200 it gives me the elasticsearch data.

Why from logstash it is not connecting ?

I am running everything through docker.
I have also linked all docker containers with --link. Before ssl everything was working smoothly , with ssl in picture , may be I am missing something . Please guide me where I am doing wrong. I believe it has nothing to do with docker as before it was running properly without ssl.

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