# Logstash input twitter authorized error

**URL:** <https://discuss.elastic.co/t/logstash-input-twitter-authorized-error/41074>\
**Category:** Logstash\
**Created:** [February 5, 2016, 2:47pm UTC](https://discuss.elastic.co/t/logstash-input-twitter-authorized-error/41074 "2016-02-05T14:47:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kamyabali7](https://avatars.discourse-cdn.com/v4/letter/k/b9bd4f/32.png) [@kamyabali7](https://discuss.elastic.co/u/kamyabali7)\
**Post date:** [February 5, 2016, 2:47pm UTC](https://discuss.elastic.co/t/logstash-input-twitter-authorized-error/41074/1 "2016-02-05T14:47:10Z")

</div>

Any one have experience with below error ?  
Please help me

Logstash startup completed

←[33m {:exception=\>Twitter::Error::Unauthorized, :backtrace=\>["C:/logstash-1.5.1  
/vendor/bundle/jruby/1.9/gems/twitter-5.12.0/lib/twitter/streaming/response.rb:2  
1:in on\_headers\_complete'", "org/ruby\_http\_parser/RubyHttpParser.java:370:in\<  
\<'", "C:/logstash-1.5.1/vendor/bundle/jruby/1.9/gems/twitter-5.12.0/lib/twitter/  
streaming/response.rb:16:in \<\<'", "C:/logstash-1.5.1/vendor/bundle/jruby/1.9/ge  
ms/twitter-5.12.0/lib/twitter/streaming/connection.rb:22:instream'", "C:/logst  
ash-1.5.1/vendor/bundle/jruby/1.9/gems/twitter-5.12.0/lib/twitter/streaming/clie  
nt.rb:116:in request'", "C:/logstash-1.5.1/vendor/bundle/jruby/1.9/gems/twitter  
-5.12.0/lib/twitter/streaming/client.rb:36:infilter'", "C:/logstash-1.5.1/vend  
or/bundle/jruby/1.9/gems/logstash-input-twitter-0.1.6/lib/logstash/inputs/twitte  
r.rb:88:in run'", "C:/logstash-1.5.1/vendor/bundle/jruby/1.9/gems/logstash-core  
-1.5.1-java/lib/logstash/pipeline.rb:176:ininputworker'", "C:/logstash-1.5.1/v  
endor/bundle/jruby/1.9/gems/logstash-core-1.5.1-java/lib/logstash/pipeline.rb:17  
0:in `start\_input'"], :level=\>:warn}←[0m  
I'm using the below twitter config:-

input {  
twitter {  
consumer\_key =\> ""  
consumer\_secret =\> ""  
oauth\_token =\> ""  
oauth\_token\_secret =\> ""  
keywords =\> [""]  
full\_tweet =\> true  
}  
}

output {  
stdout { codec =\> dots }  
elasticsearch {  
host =\> "localhost:9200"  
}  
}

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [February 6, 2016, 6:28pm UTC](https://discuss.elastic.co/t/logstash-input-twitter-authorized-error/41074/2 "2016-02-06T18:28:25Z")

</div>

You _do_ have proper values in the `consumer_key`, `consumer_secret`, `oauth_token`, and `oath_token_secret` options, right? I'm also not sure what happens when `keywords` contains just an empty string.

---

<div class="post-metadata">

**Author:** ![Joel\_Backschat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joel_backschat/32/10727_2.png) [@Joel\_Backschat](https://discuss.elastic.co/u/Joel_Backschat)\
**Post date:** [July 5, 2016, 2:04pm UTC](https://discuss.elastic.co/t/logstash-input-twitter-authorized-error/41074/3 "2016-07-05T14:04:46Z")

</div>

Same problem here. I generate my credentials in my twitter dev account, but no sucess. Anyone?

---

<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:49am UTC](https://discuss.elastic.co/t/logstash-input-twitter-authorized-error/41074/4 "2017-07-06T04:49:27Z")

</div>