# Logstash HTTP\_Poller tls version

**URL:** <https://discuss.elastic.co/t/logstash-http-poller-tls-version/193875>\
**Category:** Logstash\
**Created:** [August 5, 2019, 7:53pm UTC](https://discuss.elastic.co/t/logstash-http-poller-tls-version/193875 "2019-08-05T19:53:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tn-mikel](https://avatars.discourse-cdn.com/v4/letter/t/4491bb/32.png) [@tn-mikel](https://discuss.elastic.co/u/tn-mikel)\
**Post date:** [August 5, 2019, 7:53pm UTC](https://discuss.elastic.co/t/logstash-http-poller-tls-version/193875/1 "2019-08-05T19:53:41Z")

</div>

Hello, I am trying to use the HTTP\_Poller v5.0.1 to contact the CloudFlare API to pull some traffic and security logs. However, when calling the URI, Cloudflare API complains that the version of TLS I am using is only 1.0. Is there a way to force the poller to use TLS1.2?

## Logstash Config

```auto
input {
  http_poller {
    urls => {
      cf_waf_test => {
        method => get
        url => ####
        headers => {
          "Content-Type" => "application/json"
          "X-Auth-Email" => "####"
          "X-Auth-Key" => "####"
        }
      }
    }
    request_timeout => 60
    schedule => { "every" => "5m" }
    tags => ["Cloudflare-WAF-Logs"]
  }
}

```

## Error Message

Cloudflare does not support deprecated TLS versions for security reasons. Please upgrade your client to TLS 1.2 or greater. See [https://blog.cloudflare.com/deprecating-old-tls-versions-on-cloudflare-dashboard-and-api/](https://blog.cloudflare.com/deprecating-old-tls-versions-on-cloudflare-dashboard-and-api/) for more details.

---

<div class="post-metadata">

**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:** [August 5, 2019, 8:23pm UTC](https://discuss.elastic.co/t/logstash-http-poller-tls-version/193875/2 "2019-08-05T20:23:25Z")

</div>

Which JRE are you using (vendor and version)?

---

<div class="post-metadata">

**Author:** ![tn-mikel](https://avatars.discourse-cdn.com/v4/letter/t/4491bb/32.png) [@tn-mikel](https://discuss.elastic.co/u/tn-mikel)\
**Post date:** [August 5, 2019, 8:40pm UTC](https://discuss.elastic.co/t/logstash-http-poller-tls-version/193875/3 "2019-08-05T20:40:48Z")

</div>

Hey, here is a dump from java -version

```auto
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 8.0.5.10 - pxa6480sr5fp10-20180214_01(SR5 FP10))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180208_37 8436 (JIT enabled, AOT enabled)
OpenJ9 - 39bb844
OMR - c04ccb2
IBM - 2321a81)
JCL - 20180209_01 based on Oracle jdk8u161-b12

```

---

<div class="post-metadata">

**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:** [August 5, 2019, 9:07pm UTC](https://discuss.elastic.co/t/logstash-http-poller-tls-version/193875/4 "2019-08-05T21:07:54Z")

</div>

Elastic do not support any version of J9. That said, I have run with it in the past and had no problems.

Does adding -Dcom.ibm.jsse2.overrideDefaultTLS=true to jvm.options help?

---

<div class="post-metadata">

**Author:** ![tn-mikel](https://avatars.discourse-cdn.com/v4/letter/t/4491bb/32.png) [@tn-mikel](https://discuss.elastic.co/u/tn-mikel)\
**Post date:** [August 6, 2019, 3:09am UTC](https://discuss.elastic.co/t/logstash-http-poller-tls-version/193875/5 "2019-08-06T03:09:44Z")

</div>

Hey, such a simple oversight on my part. I switched to java-1.8.0-openjdk-devel and everything works perfectly now. Thanks for you help!

---

<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:** [September 3, 2019, 3:09am UTC](https://discuss.elastic.co/t/logstash-http-poller-tls-version/193875/6 "2019-09-03T03:09:48Z")

</div>

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