# @timestamp not match with the log date

**URL:** <https://discuss.elastic.co/t/timestamp-not-match-with-the-log-date/262272>\
**Category:** Logstash\
**Created:** [January 26, 2021, 7:14pm UTC](https://discuss.elastic.co/t/timestamp-not-match-with-the-log-date/262272 "2021-01-26T19:14:42Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [January 27, 2021, 4:46pm UTC](https://discuss.elastic.co/t/timestamp-not-match-with-the-log-date/262272/4 "2021-01-27T16:46:34Z")

</div>

> [@Riyanka](#):
>
> org.logstash.beats.InvalidFrameProtocolException: Invalid version of beats protocol: 69

Generally this means that something that is not speaking the beats protocol is connecting to the input. Amongst the possible causes are:

1. A beat with SSL enabled connecting to a beat input with SSL disabled
2. A beat with SSL disabled connecting to a beat input with SSL enabled
3. A port scanner (on the public internet you can be certain that folks are port scanning you, on a corporate network this may also happen)
4. Someone else trying to use the same port

---

_[View the full topic](https://discuss.elastic.co/t/timestamp-not-match-with-the-log-date/262272)._