# Logstash 6.6.0 with syslog output 3.0.5 ssl-tcp issue

**URL:** <https://discuss.elastic.co/t/logstash-6-6-0-with-syslog-output-3-0-5-ssl-tcp-issue/226684>\
**Category:** Logstash\
**Created:** [April 6, 2020, 11:04am UTC](https://discuss.elastic.co/t/logstash-6-6-0-with-syslog-output-3-0-5-ssl-tcp-issue/226684 "2020-04-06T11:04:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![J.Timmer](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@J.Timmer](https://discuss.elastic.co/u/J.Timmer)\
**Post date:** [April 6, 2020, 11:04am UTC](https://discuss.elastic.co/t/logstash-6-6-0-with-syslog-output-3-0-5-ssl-tcp-issue/226684/1 "2020-04-06T11:04:53Z")

</div>

Hello all,

I am having trouble getting the syslog output working with the ssl-tcp setting. Once I configure the pipeline to use ssl-tcp I get the following errors:

```auto
    Error registering plugin {:pipeline_id=>"<ID>", :plugin=>"#<LogStash::OutputDelegator:0x5be9ec9a>", :error=>"no implicit conversion of nil into String", :thread=>"#<Thread:0x20df3f03 run>"}

```

No matter the changes I do, when using ssl-tcp as the protocol it is giving me this error. Writing syslog output to file is no problem and see normal syslog data there.  
I have a message field present (read a forum post stating that a message field was missing which resulted in the same message).

In the pipeline i have:

```auto
    ssl_verify => true
    ssl_cert => "c:\elastic\logstash-6.6.0\<server>.crt"
    ssl_cacert => "c:\elastic\logstash-6.6.0\<ca>.pem"
    protocol => "ssl-tcp"

```

Anyone getting same error? Or is my pipeline wrong?

Regards,  
Jeroen

---

<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 4, 2020, 11:05am UTC](https://discuss.elastic.co/t/logstash-6-6-0-with-syslog-output-3-0-5-ssl-tcp-issue/226684/2 "2020-05-04T11:05:12Z")

</div>

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