Handling exception: org.logstash.beats.InvalidFrameProtocolException: Invalid version of beats protocol: 71

Hi,
I'm Using Filebeat 8.0/Logstash8.0/Elasticsearch8.0 version in windows 10 environment and i'm trying to send the logs from filebeat-->logstash-->elasticsearch.
post start of filebeat / logstash/elasticsearch, i'm getting the below error in logstash console.

Handling exception: org.logstash.beats.InvalidFrameProtocolException: Invalid version of beats protocol: 71
[2020-06-25T11:43:51,121][WARN ][io.netty.channel.DefaultChannelPipeline][main][80b24821c663bec2fff9240ae2e408e735ec2836d9902e005222cd89c27fbbc4] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.

My Filebeat.yml file

filebeat.inputs:

  • type: log
  • C:\Users\ELK*.log

================================== Outputs ===================================

Configure what output to use when sending the data collected by the beat.

---------------------------- Elasticsearch Output ----------------------------

output.elasticsearch:

Array of hosts to connect to.

hosts: ["localhost:9200"]

Protocol - either http (default) or https.

#protocol: "https"

Authentication credentials - either API key or username/password.

#api_key: "id:api_key"
#username: "elastic"
#password: "changeme"

------------------------------ Logstash Output -------------------------------

#output.logstash:

The Logstash hosts

hosts: "localhost:5044"

Optional SSL. By default is off.

List of root certificates for HTTPS server verifications

#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

Certificate for SSL client authentication

#ssl.certificate: "/etc/pki/client/cert.pem"

Client Certificate Key

#ssl.key: "/etc/pki/client/cert.key"

My Logstash config file

input {
beats {
port => 5044
ssl => false
}
}

output {
elasticsearch {
hosts => "http://localhost:9200"
index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}"
}
}

You have uncommented

output.elasticsearch:

and commented

output.logstash:

so filebeat will be trying to use http instead of lumberjack as the protocol. That's not going to work.

Yes, It's working thanks for highlighting