# Unable to connect to elasticsearch with x-pack
**URL:** https://discuss.elastic.co/t/unable-to-connect-to-elasticsearch-with-x-pack/165639
**Category:** Logstash
**Tags:** elastic-stack-security
**Created:** [January 24, 2019, 6:23pm UTC](https://discuss.elastic.co/t/unable-to-connect-to-elasticsearch-with-x-pack/165639 "2019-01-24T18:23:14Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@ashalabh](https://discuss.elastic.co/u/ashalabh)
#### Post date: [January 24, 2019, 6:23pm UTC](https://discuss.elastic.co/t/unable-to-connect-to-elasticsearch-with-x-pack/165639/1 "2019-01-24T18:23:15Z")
Sending Logstash logs to /home/elastic/logstash/logs which is now configured via log4j2.properties
[2019-01-24T12:50:23,035][WARN][logstash.config.source.multilocal] Ignoring the 'pipelines.yml' file because modules or command line options are specified
[2019-01-24T12:50:23,066][INFO][logstash.runner] Starting Logstash {"logstash.version"=\>"6.5.4"}
[2019-01-24T12:50:28,551][INFO][logstash.pipeline] Starting pipeline {:pipeline\_id=\>"main", "pipeline.workers"=\>2, "pipeline.batch.size"=\>125, "pipeline.batch.delay"=\>50}
[2019-01-24T12:50:28,804][WARN][logstash.outputs.elasticsearch] \*\* WARNING \*\* Detected UNSAFE options in elasticsearch output configuration!
\*\* WARNING \*\* You have enabled encryption but DISABLED certificate verification.
\*\* WARNING \*\* To make sure your data is secure change :ssl\_certificate\_verification to true
[2019-01-24T12:50:29,209][ERROR][logstash.pipeline] Error registering plugin {:pipeline\_id=\>"main", :plugin=\>"#LogStash::OutputDelegator:0x4a4f938b", :error=\>"signed fields invalid", :thread=\>"#\"}
[2019-01-24T12:50:29,220][ERROR][logstash.pipeline] Pipeline aborted due to error {:pipeline\_id=\>"main", :exception=\>java.security.cert.CertificateParsingException: signed fields invalid, :backtrace=\>["sun.security.x509.X509CertImpl.parse(sun/security/x509/X509CertImpl.java:1791)", "sun.security.x509.X509CertImpl.(sun/security/x509/X509CertImpl.java:195)", "sun.security.provider.X509Factory.parseX509orPKCS7Cert(sun/security/provider/X509Factory.java:471)", "sun.security.provider.X509Factory.engineGenerateCertificates(sun/security/provider/X509Factory.java:356)", "java.security.cert.CertificateFactory.generateCertificates(java/security/cert/CertificateFactory.java:462)", "java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)", "org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:423)", "org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:290)", "home.elastic.logstash.vendor.bundle.jruby.$2\_dot\_3\_dot\_0.gems.manticore\_minus\_0\_dot\_6\_dot\_4\_minus\_java.lib.manticore.client.block in setup\_trust\_store(/home/elastic/logstash/vendor/bundle/jruby/2.3.0/gems/manticore-0.6.4-ja
############ truncated the log intentionally because of size limit ##########
\_core.lib.logstash.pipeline.block in start(/home/elastic/logstash/logstash-core/lib/logstash/pipeline.rb:160)", "org.jruby.RubyProc.call(org/jruby/RubyProc.java:289)", "org.jruby.RubyProc.call(org/jruby/RubyProc.java:246)", "java.lang.Thread.run(java/lang/Thread.java:748)"], :thread=\>"#\"}
[2019-01-24T12:50:29,251][ERROR][logstash.agent] Failed to execute action {:id=\>:main, :action\_type=\>LogStash::ConvergeResult::FailedAction, :message=\>"Could not execute action: PipelineAction::Create, action\_result: false", :backtrace=\>nil}
[2019-01-24T12:50:29,606][INFO][logstash.agent] Successfully started Logstash API endpoint {:port=\>9600}
---
### Author:  [@ikakavas](https://discuss.elastic.co/u/ikakavas)
#### Post date: [January 24, 2019, 9:41pm UTC](https://discuss.elastic.co/t/unable-to-connect-to-elasticsearch-with-x-pack/165639/2 "2019-01-24T21:41:31Z")
Hi,
Please don't post unformatted logs like that as these tend to be very hard to read.
Instead paste the text and format it with \ icon, and check the preview
window to make sure it's properly formatted before posting it. This makes it
more likely that your question will receive a useful answer.
It would be great if you could update your post to solve this.
This message:
```auto
[2019-01-24T12:50:29,209][ERROR][logstash.pipeline] Error registering plugin {:pipeline_id=>"main", :plugin=>"#LogStash::OutputDelegator:0x4a4f938b", :error=>"signed fields invalid", :thread=>"#"}
```
seems to imply that there is PKCS12 keystore that logstash tries to read as though it's a PEM encoded certificate. Please share the relevant section of your Elasticsearch output plugin
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 21, 2019, 9:41pm UTC](https://discuss.elastic.co/t/unable-to-connect-to-elasticsearch-with-x-pack/165639/3 "2019-02-21T21:41:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.