# SSL problem with logstash newrelic output plugin

**URL:** <https://discuss.elastic.co/t/ssl-problem-with-logstash-newrelic-output-plugin/67979>\
**Category:** Logstash\
**Created:** [December 5, 2016, 4:44am UTC](https://discuss.elastic.co/t/ssl-problem-with-logstash-newrelic-output-plugin/67979 "2016-12-05T04:44:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![charekc](https://avatars.discourse-cdn.com/v4/letter/c/5e9695/32.png) [@charekc](https://discuss.elastic.co/u/charekc)\
**Post date:** [December 5, 2016, 4:44am UTC](https://discuss.elastic.co/t/ssl-problem-with-logstash-newrelic-output-plugin/67979/1 "2016-12-05T04:44:37Z")

</div>

Hello  
I am running logstash 5.0.2 and using output plugin new relic 0.9.x  
My output config is like the following

```
newrelic {
account_id => "MyAccountId1111111111"
insert_key => "myInsertKeyXYZ"
event_type => "Myevent"
}	

```

When I sent data, I am getting SSL errors

23:07:11.510 [[main]\>worker6] WARN logstash.outputs.newrelic - Failed to flush outgoing items {:outgoing\_count=\>1, :exception=\>"OpenSSL::SSL::SSLError", :backtrace=\>["org/jruby/ext/openssl/SSLSocket.java:215:in `connect'", "/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:800:in`connect'", "org/jruby/ext/timeout/Timeout.java:98:in `timeout'", "/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:800:in`connect'", "/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:756:in `do_start'", "/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:745:in`start'", "/usr/share/logstash/vendor/jruby/lib/ruby/1.9/net/http.rb:1293:in `request'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-newrelic-0.9.1/lib/logstash/outputs/newrelic.rb:212:in`send\_to\_insights'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-newrelic-0.9.1/lib/logstash/outputs/newrelic.rb:147:in `flush'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/buffer.rb:219:in`buffer\_flush'", "org/jruby/RubyHash.java:1342:in `each'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/buffer.rb:216:in`buffer\_flush'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/buffer.rb:159:in `buffer_receive'", "/usr/share/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-newrelic-0.9.1/lib/logstash/outputs/newrelic.rb:136:in`receive'", "/usr/share/logstash/logstash-core/lib/logstash/outputs/base.rb:92:in `multi_receive'", "org/jruby/RubyArray.java:1613:in`each'", "/usr/share/logstash/logstash-core/lib/logstash/outputs/base.rb:92:in `multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator_strategies/legacy.rb:19:in`multi\_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output\_delegator.rb:42:in `multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:297:in`output\_batch'", "org/jruby/RubyHash.java:1342:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:296:in`output\_batch'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:252:in `worker_loop'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:225:in`start\_workers'"]}

If I use http output to manually sent to NR, eg  
http {  
http\_method =\> "post"  
url =\> "[https://insights-collector.newrelic.com/v1/accounts/MyAccountId1111111111/events](https://insights-collector.newrelic.com/v1/accounts/MyAccountId1111111111/events)"  
headers =\> { "Content-Type" =\> "application/json"  
"X-Insert-Key" =\> "myInsertKeyXYZ"  
}  
This is fine.  
I also had this issue on logstash 2.4 so I tried upgrade to 5x. Suggestions on further debugging or resolutions?

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:** [January 2, 2017, 4:44am UTC](https://discuss.elastic.co/t/ssl-problem-with-logstash-newrelic-output-plugin/67979/2 "2017-01-02T04:44:47Z")

</div>

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