# Logstash error after installing ssl **URL:** \ **Category:** Logstash\ **Tags:** elastic-stack-security\ **Created:** [November 9, 2020, 6:14pm UTC](https://discuss.elastic.co/t/logstash-error-after-installing-ssl/254807 "2020-11-09T18:14:10Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Cosmin\_Ciobanu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cosmin_ciobanu/32/78696_2.png) [@Cosmin\_Ciobanu](https://discuss.elastic.co/u/Cosmin_Ciobanu)\ **Post date:** [November 9, 2020, 6:14pm UTC](https://discuss.elastic.co/t/logstash-error-after-installing-ssl/254807/1 "2020-11-09T18:14:11Z")
[ERROR] 2020-11-09 10:08:12.337 [[main]-pipeline-manager] javapipeline - Pipeline error {:pipeline\_id=\>"main", :exception=\>#\, :backtrace=\>["/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/manticore-0.7.0-java/lib/manticore/response.rb:37:in `block in initialize'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/manticore-0.7.0-java/lib/manticore/response.rb:79:in `call'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http\_client/manticore\_adapter.rb:74:in `perform_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:332:in `perform\_request\_to\_url'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:261:in `health_check_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:270:in `block in healthcheck!'", "org/jruby/RubyHash.java:1415:in `each'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:266:in `healthcheck!'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:382:in `update_urls'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:82:in `update\_initial\_urls'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:76:in `start'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client.rb:302:in `build\_pool'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http\_client.rb:64:in `initialize'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client_builder.rb:105:in `create\_http\_client'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http\_client\_builder.rb:101:in `build'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch.rb:307:in `build\_client'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/common.rb:23:in `register'", "org/logstash/config/ir/compiler/OutputStrategyExt.java:126:in `register'", "org/logstash/config/ir/compiler/AbstractOutputDelegatorExt.java:68:in `register'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:228:in `block in register\_plugins'", "org/jruby/RubyArray.java:1809:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:227:in `register\_plugins'", "/usr/share/logstash/logstash-core/lib/logstash/java\_pipeline.rb:585:in `maybe_setup_out_plugins'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:240:in `start\_workers'", "/usr/share/logstash/logstash-core/lib/logstash/java\_pipeline.rb:185:in `run'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:137:in `block in start'"], "pipeline.sources"=\>["/etc/logstash/conf.d/filebeat-pipeline.conf"], :thread=\>"#\"} [INFO] 2020-11-09 10:08:12.339 [[main]-pipeline-manager] javapipeline - Pipeline terminated {"pipeline.id"=\>"main"} Let me know if you need any other information! This error is generated after using --debug. Thank you! ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [November 9, 2020, 6:19pm UTC](https://discuss.elastic.co/t/logstash-error-after-installing-ssl/254807/2 "2020-11-09T18:19:04Z")
> [@Cosmin\_Ciobanu](#): > > Manticore::UnknownException: Host name '0.0.0.0' does not match the certificate subject provided by the peer (CN=elasticsearch) Sound like you are configuring the output to connect to an address that does not match the certificate that you have installed in elasticsearch. They should match. You do have the option to disable this verification, but in that case you might as well turn off TLS, since you do not have any security in you disable it. ---
**Author:** ![Cosmin\_Ciobanu1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cosmin_ciobanu1/32/78785_2.png) [@Cosmin\_Ciobanu1](https://discuss.elastic.co/u/Cosmin_Ciobanu1)\ **Post date:** [November 10, 2020, 7:57pm UTC](https://discuss.elastic.co/t/logstash-error-after-installing-ssl/254807/3 "2020-11-10T19:57:00Z")
I've created all the certificates with certuil tool. And I use the same CA for KIbana-Elasticsearch , Filbeat-Elasticsearch comunication and it works just fine. I don't understand why this error still remains. ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [November 10, 2020, 8:23pm UTC](https://discuss.elastic.co/t/logstash-error-after-installing-ssl/254807/4 "2020-11-10T20:23:39Z")
It is not about the CA, it is about the CN not matching the hostname. ---
**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:** [November 11, 2020, 12:52am UTC](https://discuss.elastic.co/t/logstash-error-after-installing-ssl/254807/5 "2020-11-11T00:52:09Z")
Which mode did you use for `certutil`? Was it `elasticsearch-certutil cert` or `elasticsearch-certutil http` ? My _guess_ is that you used `http`. If so, when you did that, you were asked: > Which hostnames will be used to connect ... and > Which IP addresses will be used to connect ... You didn't enter `0.0.0.0` into that list (nor should you really, since that is not a routable address), but here you have logstash attempting to connect to Elasticsearch on `0.0.0.0` > Host name '0.0.0.0' does not match the certificate subject provided by the peer (CN=elasticsearch) That's the problem. > [@Cosmin\_Ciobanu1](#): > > I use the same CA for KIbana-Elasticsearch , Filbeat-Elasticsearch comunication and it works just fine. My _guess_ is that for Kibana and Filebeat you have put in a real URL with a real hostname or IP, but you've used a different format for Logstash. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 12, 2020, 7:48pm UTC](https://discuss.elastic.co/t/logstash-error-after-installing-ssl/254807/7 "2020-12-12T19:48:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.