# SSL error received even though "ssl" is set to "false"

**URL:** <https://discuss.elastic.co/t/ssl-error-received-even-though-ssl-is-set-to-false/176163>\
**Category:** Logstash\
**Created:** [April 10, 2019, 7:56am UTC](https://discuss.elastic.co/t/ssl-error-received-even-though-ssl-is-set-to-false/176163 "2019-04-10T07:56:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Miao](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@Miao](https://discuss.elastic.co/u/Miao)\
**Post date:** [April 10, 2019, 7:56am UTC](https://discuss.elastic.co/t/ssl-error-received-even-though-ssl-is-set-to-false/176163/1 "2019-04-10T07:56:38Z")

</div>

Here is the `input` segment of my `logstash.conf`:

```
input {
	http {
		host => "127.0.0.1"
		port => 31311 
		ssl => false
	}
}

```

I have an index named `twitter_new`. I want to send a `DELETE` request via cURL to remove the entire index. This is my cURL command:

`C:\Users\Me\Downloads\curl-7.64.1-win64-mingw\bin> .\curl.exe -XDELETE "https://127.0.0.1:9200/twitter_new"`

Here is the response:

`curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number`

How can I fix this?

**N.B.:** The SSL error is only encountered when I send `DELETE` requests -- I can successfully send `PUT` and `POST` requests.

---

<div class="post-metadata">

**Author:** ![A\_B](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/a_b/32/17104_2.png) [@A\_B](https://discuss.elastic.co/u/A_B)\
**Post date:** [April 10, 2019, 8:07am UTC](https://discuss.elastic.co/t/ssl-error-received-even-though-ssl-is-set-to-false/176163/2 "2019-04-10T08:07:13Z")

</div>

If `ssl` is set to `false`, why do you try to use _HTTPS_ with `curl`?

Do you get the same error if you use `curl -k`?

```
-k, --insecure
  (TLS) By default, every SSL connection curl makes is verified to be secure. This option allows curl to proceed and operate even for server connections otherwise considered insecure.
```

---

<div class="post-metadata">

**Author:** ![Miao](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@Miao](https://discuss.elastic.co/u/Miao)\
**Post date:** [April 10, 2019, 11:14am UTC](https://discuss.elastic.co/t/ssl-error-received-even-though-ssl-is-set-to-false/176163/3 "2019-04-10T11:14:24Z")

</div>

Oh man, that was stupid... I somehow failed to notice that I was using `https` instead of `http`.

---

<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:** [April 10, 2019, 11:51am UTC](https://discuss.elastic.co/t/ssl-error-received-even-though-ssl-is-set-to-false/176163/4 "2019-04-10T11:51:04Z")

</div>

So you disable ssl on port 31311, and get SSL errors on port 9200. They would appear to be unrelated.

---

<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:** [May 8, 2019, 11:51am UTC](https://discuss.elastic.co/t/ssl-error-received-even-though-ssl-is-set-to-false/176163/5 "2019-05-08T11:51:06Z")

</div>

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