# Problem with twitter-plugin and https-proxies

**URL:** <https://discuss.elastic.co/t/problem-with-twitter-plugin-and-https-proxies/50426>\
**Category:** Logstash\
**Created:** [May 19, 2016, 11:29am UTC](https://discuss.elastic.co/t/problem-with-twitter-plugin-and-https-proxies/50426 "2016-05-19T11:29:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kodo65](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kodo65/32/1185_2.png) [@kodo65](https://discuss.elastic.co/u/kodo65)\
**Post date:** [May 19, 2016, 11:29am UTC](https://discuss.elastic.co/t/problem-with-twitter-plugin-and-https-proxies/50426/1 "2016-05-19T11:29:14Z")

</div>

I have logstash v2.3.2 installed and wanted to try the twitter-plugin again after abandoning it earlier in favor for a custom developed twitterstream-client.

Setting the proxy-relevant settings to:

use\_proxy =\> true  
proxy\_address =\> "xxx.yyy.zzz"  
proxy\_port =\> xxxx

I get loads of the following exceptions when logstash starts:

{:timestamp=\>"2016-05-19T13:13:08.304000+0200", :message=\>"End of file reached", :exception=\>#\<EOFError: End of file reached\>, :backtrace=\>["org/jruby/RubyIO.java:2895:in `readpartial'", "E:/twitter/logstash-2.3.2/vendor/bundle/jruby/1.9/gems/logstash-input-twitter-2.2.2/lib/logstash/inputs/twitter/patches.rb:30:in`stream'", "E:/twitter/logstash-2.3.2/vendor/bundle/jruby/1.9/gems/logstash-input-twitter-2.2.2/lib/logstash/inputs/twitter/patches.rb:58:in `request'", "E:/twitter/logstash-2.3.2/vendor/bundle/jruby/1.9/gems/twitter-5.15.0/lib/twitter/streaming/client.rb:37:in`filter'", "E:/twitter/logstash-2.3.2/vendor/bundle/jruby/1.9/gems/logstash-input-twitter-2.2.2/lib/logstash/inputs/twitter.rb:128:in `run'", "E:/twitter/logstash-2.3.2/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.2-java/lib/logstash/pipeline.rb:342:in`inputworker'", "E:/twitter/logstash-2.3.2/vendor/bundle/jruby/1.9/gems/logstash-core-2.3.2-java/lib/logstash/pipeline.rb:336:in `start\_input'"], :options=\>nil, :level=\>:warn}

Now, if I set use\_proxy =\> false logstash starts but of course I get a connection refused error as the twitter-plugin is unable to connect to my proxy which uses https. I guess the plugin defaults to http.

Is this a known problem and is there a workaround?

---

<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, 4:56am UTC](https://discuss.elastic.co/t/problem-with-twitter-plugin-and-https-proxies/50426/2 "2017-07-06T04:56:58Z")

</div>