# Invalid Frame Type, received: 69/84

**URL:** <https://discuss.elastic.co/t/invalid-frame-type-received-69-84/130234>\
**Category:** Logstash\
**Created:** [May 2, 2018, 10:38am UTC](https://discuss.elastic.co/t/invalid-frame-type-received-69-84/130234 "2018-05-02T10:38:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lauea](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lauea/32/26743_2.png) [@lauea](https://discuss.elastic.co/u/lauea)\
**Post date:** [May 2, 2018, 10:38am UTC](https://discuss.elastic.co/t/invalid-frame-type-received-69-84/130234/1 "2018-05-02T10:38:15Z")

</div>

Hi Guy,

I always encounter below issue from logstash when shipping log from filebeat to logstash, but if can ship to elasticsearch by filebeat directly.

> Handling exception: org.logstash.beats.BeatsParser$InvalidFrameProtocolException: Invalid Frame Type, received: 69

Below is my version information:

> logstash: 6.1.2  
> filebeat: 6.1.2

Do you have any idea? Thanks.

---

<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:** [May 2, 2018, 12:22pm UTC](https://discuss.elastic.co/t/invalid-frame-type-received-69-84/130234/2 "2018-05-02T12:22:45Z")

</div>

This can happen when Filebeat uses SSL but Logstash doesn't. Without seeing your configuration we can only guess.

---

<div class="post-metadata">

**Author:** ![lauea](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lauea/32/26743_2.png) [@lauea](https://discuss.elastic.co/u/lauea)\
**Post date:** [May 2, 2018, 3:31pm UTC](https://discuss.elastic.co/t/invalid-frame-type-received-69-84/130234/3 "2018-05-02T15:31:33Z")

</div>

@magnusbaeck, all configuration for filebeat/logstash uses default ssl(false). So it should not cause by this. But I am sure it should be logstash issue.

---

<div class="post-metadata">

**Author:** ![lauea](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lauea/32/26743_2.png) [@lauea](https://discuss.elastic.co/u/lauea)\
**Post date:** [May 2, 2018, 3:43pm UTC](https://discuss.elastic.co/t/invalid-frame-type-received-69-84/130234/4 "2018-05-02T15:43:52Z")

</div>

@magnusbaeck, just found the root cause. Found it is so confused for many #, which let me forgot to uncomment below line:

> #output.logstash

God. Anyway, 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:** [May 30, 2018, 3:43pm UTC](https://discuss.elastic.co/t/invalid-frame-type-received-69-84/130234/5 "2018-05-30T15:43:55Z")

</div>

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