# Logstash

**URL:** <https://discuss.elastic.co/t/logstash/33716>\
**Category:** Logstash\
**Created:** [November 4, 2015, 8:42am UTC](https://discuss.elastic.co/t/logstash/33716 "2015-11-04T08:42:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sylv](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sylv](https://discuss.elastic.co/u/sylv)\
**Post date:** [November 4, 2015, 8:42am UTC](https://discuss.elastic.co/t/logstash/33716/1 "2015-11-04T08:42:06Z")

</div>

hello  
I set new versions : elasticsearch kibana and logstach  
i have these errors with my config file txt who was ok with previous versions:

l\logstash\_titulaires\_config\_file.txt  
io/console not supported; tty will not be manipulated  
←[31mUnknown setting 'protocol' for elasticsearch {:level=\>:error}←[0m  
←[31mUnknown setting 'cluster' for elasticsearch {:level=\>:error}←[0m  
←[31mUnknown setting 'bind\_host' for elasticsearch {:level=\>:error}←[0m  
Error: Something is wrong with your configuration.  
You may be interested in the '--configtest' flag which you can  
use to validate logstash's configuration before you choose  
to restart a running system.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 4, 2015, 9:12am UTC](https://discuss.elastic.co/t/logstash/33716/2 "2015-11-04T09:12:43Z")

</div>

Providing your config will help.

Also please use a more descriptive title.

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [November 4, 2015, 3:06pm UTC](https://discuss.elastic.co/t/logstash/33716/3 "2015-11-04T15:06:49Z")

</div>

In Logstash 2.0, the Elasticsearch output uses the http protocol by default, and no longer contains the `node` or `transport` protocols. These errors clearly indicate you were using either the `node` or `transport` protocol to connect to Elasticsearch. **This is not recommended with Elasticsearch 2.0.** I do recommend switching to connect via HTTP. If you have a clear path to port 9200 on the target machine, this should happen automatically if you remove the `protocol`, `cluster`, and `bind_host` options.

If you insist on using either the `node` or `transport` protocol in spite of the official recommendations from both Elasticsearch and Logstash, you must install the `logstash-output-elasticsearch_java` plugin and change your output block to be `elasticsearch_java {}` instead of `elasticsearch {}`. Install this plugin by running `bin/plugin install logstash-output-elasticsearch_java` from your Logstash directory. This method requires internet access.

---

<div class="post-metadata">

**Author:** ![sylv](https://avatars.discourse-cdn.com/v4/letter/s/bb73d2/32.png) [@sylv](https://discuss.elastic.co/u/sylv)\
**Post date:** [November 5, 2015, 11:09am UTC](https://discuss.elastic.co/t/logstash/33716/4 "2015-11-05T11:09:52Z")

</div>

Hello,

yes you were right,  
problems were from there, i removed protocol, cluster modified host  
that's ok

thanks

---

<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:** [July 6, 2017, 5:23am UTC](https://discuss.elastic.co/t/logstash/33716/5 "2017-07-06T05:23:55Z")

</div>