# Logstash http output plugin 6.0 ssl issue

**URL:** <https://discuss.elastic.co/t/logstash-http-output-plugin-6-0-ssl-issue/109317>\
**Category:** Logstash\
**Created:** [November 28, 2017, 6:45am UTC](https://discuss.elastic.co/t/logstash-http-output-plugin-6-0-ssl-issue/109317 "2017-11-28T06:45:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![suresh\_subbaiah](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@suresh\_subbaiah](https://discuss.elastic.co/u/suresh_subbaiah)\
**Post date:** [November 28, 2017, 6:45am UTC](https://discuss.elastic.co/t/logstash-http-output-plugin-6-0-ssl-issue/109317/1 "2017-11-28T06:45:11Z")

</div>

Hi,  
We are migrating from logstash 2.x to logstash 6.0 with http output plugin. Its a secure request we are making from logstash however we are getting the below error with the latest version.

`[2017-11-28T06:35:59,558][ERROR][logstash.outputs.http] [HTTP Output Failure] Could not fetch URL {:url=>"https://xx.xxx.xxx.xxx:5061/evmon/tenant/platform/service/platform/instance/logging-monitoring/host/866cd7dccc6a?prefix=logstash-graphite.", :method=>:post, :body=>"{\"events.count\":\"457728\",\"events.rate_1m\":\"6230.636748769693\",\"events.rate_5m\":\"3668.5510144327163\",\"events.rate_15m\":\"3064.8561366704157\"}", :headers=>{"Content-Type"=>"application/json"}, :message=>"PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target", :class=>"Manticore::ClientProtocolException", :backtrace=>nil, :will_retry=>true}`

logstash 6.0 http output conf

```
output
{
                http
                {
                        content_type => "application/json"
                        format => "json"
                        http_method => "post"
                        url => "https://xx.xxx.xxx.xxx:5061/evmon/tenant/platform/service/platform/instance/logging-monitoring/host/866cd7dccc6a?prefix=logstash-graphite."
                        #verify_ssl => false
                        #ssl_certificate_validation => false
                        truststore => "/usr/share/logstash/pipeline/ssl/cacerts"
                        truststore_password => "changeit"
                        mapping => ["events.count", "%{[events][count]}", "events.rate_1m", "%{[events][rate_1m]}", "events.rate_5m", "%{[events][rate_5m]}", "events.rate_15m", "%{[events][rate_15m]}" ]
                }
}

```

logstash 2.x conf

```
output
    {
                    http
                    {
                            content_type => "application/json"
                            format => "json"
                            http_method => "post"
                            url => "https://xx.xxx.xxx.xxx:5061/evmon/tenant/platform/service/platform/instance/logging-monitoring/host/866cd7dccc6a?prefix=logstash-graphite."
                            verify_ssl => false
                            ssl_certificate_validation => false
                            truststore => "/usr/share/logstash/pipeline/ssl/cacerts"
                            truststore_password => "changeit"
                            mapping => ["events.count", "%{[events][count]}", "events.rate_1m", "%{[events][rate_1m]}", "events.rate_5m", "%{[events][rate_5m]}", "events.rate_15m", "%{[events][rate_15m]}" ]
                    }
    }

```

this is a working configuration, however in latest version verify\_ssl and ssl\_certificate\_validation is removed.

Could you please point what is missing and what needs to be done.  
Note: URL is protected by certificate(ssl ssl\_protocols TLSv1.2;) in Loadbalancer.

---

<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:** [December 26, 2017, 6:46am UTC](https://discuss.elastic.co/t/logstash-http-output-plugin-6-0-ssl-issue/109317/2 "2017-12-26T06:46:01Z")

</div>

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