# Filebeat is not able to connect to logstash

**URL:** <https://discuss.elastic.co/t/filebeat-is-not-able-to-connect-to-logstash/236066>\
**Category:** Logstash\
**Created:** [June 7, 2020, 3:21am UTC](https://discuss.elastic.co/t/filebeat-is-not-able-to-connect-to-logstash/236066 "2020-06-07T03:21:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![NetRajan](https://avatars.discourse-cdn.com/v4/letter/n/a3d4f5/32.png) [@NetRajan](https://discuss.elastic.co/u/NetRajan)\
**Post date:** [June 7, 2020, 3:21am UTC](https://discuss.elastic.co/t/filebeat-is-not-able-to-connect-to-logstash/236066/1 "2020-06-07T03:21:38Z")

</div>

I am using filebeat version 7.6.2  
Trying to connect to logstash and getting following error.

Failed to connect to backoff(async(tcp://dnslogstash.net:5044)): EOF  
logstash is configured with SSL certificate.  
I am able to send message without TLS enabled.

Any suggestion is appreciated.  
This is also frustrating not getting proper message from filebeat.  
Seems not user friendly

---

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [June 8, 2020, 2:59am UTC](https://discuss.elastic.co/t/filebeat-is-not-able-to-connect-to-logstash/236066/2 "2020-06-08T02:59:42Z")

</div>

You're not giving us much to work with, but try the filebeat output option [verification\_mode](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-ssl.html#_verification_mode): none

If that works, you have a certificate issue. If it still doesn't work, post your logstash input and filebeat configs.

---

<div class="post-metadata">

**Author:** ![NetRajan](https://avatars.discourse-cdn.com/v4/letter/n/a3d4f5/32.png) [@NetRajan](https://discuss.elastic.co/u/NetRajan)\
**Post date:** [June 8, 2020, 8:14pm UTC](https://discuss.elastic.co/t/filebeat-is-not-able-to-connect-to-logstash/236066/3 "2020-06-08T20:14:13Z")

</div>

Hi Ren  
Thanks for your input. Appreciate your insight in resolving it. As mentioned this works if SSL is not enabled for logstash. Seems something is not right about our certificate. SSL is very important to us, so I really want to solve it. Thanks in advance

I tried to use verification\_mode:none but did not help as indicated below.

| 2020-06-08T09:03:48.940-0700 | ERROR | pipeline/output.go:100 | Failed to connect to backoff(async(tcp://logstash-xxx.devero.net:5044)): EOF |
| --- | --- | --- | --- |
| 2020-06-08T09:03:48.940-0700 | INFO | pipeline/output.go:93 | Attempting to reconnect to backoff(async(tcp://logstash.xxxnet:5044)) with 4 reconnect attempt(s) |

This is filebeat.yml file

filebeat.inputs:

# Each - is an input. Most options can be set at the input level, so

# you can use different inputs for various configurations.

# Below are the input specific configurations.

- type: log

# Exclude lines. A list of regular expressions to match. It drops the lines that are

# matching any regular expression from the list.

#exclude\_lines: ['^DBG']

# Include lines. A list of regular expressions to match. It exports the lines that are

# matching any regular expression from the list.

#include\_lines: ['^ERR', '^WARN']

# Exclude files. A list of regular expressions to match. Filebeat drops the files that

# are matching any regular expression from the list. By default, no files are dropped.

#exclude\_files: ['.gz$']

# Optional additional fields. These fields can be freely picked

# to add additional information to the crawled log files for filtering

#fields:

# level: debug

# review: 1

### Multiline options

# Multiline can be used for log messages spanning multiple lines. This is common

# for Java Stack Traces or C-Line Continuation

# The regexp Pattern that has to be matched. The example pattern matches all lines starting with [

#multiline.pattern: ^[

# Defines if the pattern set under pattern should be negated or not. Default is false.

#multiline.negate: false

# Match can be set to "after" or "before". It is used to define if lines should be append to a pattern

# that was (not) matched before or after or as long as a pattern is not matched based on negate.

# Note: After is the equivalent to previous and before is the equivalent to to next in Logstash

#multiline.match: after

#============================= Filebeat modules ===============================

filebeat.config.modules:

# Glob pattern for configuration loading

path: ${path.config}/modules.d/\*.yml

# Set to true to enable config reloading

reload.enabled: false

#==================== Elasticsearch template setting ==========================

setup.template.settings:

index.number\_of\_shards: 1

#index.codec: best\_compression

#\_source.enabled: false

#================================ General =====================================

# The name of the shipper that publishes the network data. It can be used to group

# all the transactions sent by a single shipper in the web interface.

#name:

# The tags of the shipper are included in their own field with each

# transaction published.

#tags: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the

# output.

#fields:

# env: staging

#============================== Dashboards =====================================

# These settings control loading the sample dashboards to the Kibana index. Loading

# the dashboards is disabled by default and can be enabled either by setting the

# options here or by using the `setup` command.

#setup.dashboards.enabled: false

# The URL from where to download the dashboards archive. By default this URL

# has a value which is computed based on the Beat name and version. For released

# versions, this URL points to the dashboard archive on the [artifacts.elastic.co](http://artifacts.elastic.co)

# website.

#setup.dashboards.url:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.

# This requires a Kibana endpoint configuration.

setup.kibana:

# Kibana Host

# Scheme and port can be left out and will be set to the default (http and 5601)

# In case you specify and additional path, the scheme is required: [http://localhost:5601/path](http://localhost:5601/path)

# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601

#host: "localhost:5601"

# Kibana Space ID

# ID of the Kibana Space into which the dashboards should be loaded. By default,

#============================= Elastic Cloud ==================================

# These settings simplify using Filebeat with the Elastic Cloud ([https://cloud.elastic.co/](https://cloud.elastic.co/)).

# The cloud.id setting overwrites the `output.elasticsearch.hosts` and

# `setup.kibana.host` options.

# You can find the `cloud.id` in the Elastic Cloud web UI.

#cloud.id:

# The cloud.auth setting overwrites the `output.elasticsearch.username` and

# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.

#cloud.auth:

#================================ 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"

#----------------------------- Logstash output --------------------------------  
output.logstash:

# The Logstash hosts

hosts: ["[logstash.xxx.net:5044](http://logstash.xxx.net:5044)"]

# Optional SSL. By default is off.

# List of root certificates for HTTPS server verifications

ssl.certificate\_authorities: ["/Users/xxxx/filebeat-7.6.2-darwin-x86\_64/logstash.crt"]  
verification\_mode: none

# Certificate for SSL client authentication

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

# Client Certificate Key

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

#================================ Processors =====================================

# Configure processors to enhance or manipulate events generated by the beat.

#================================ Processors =====================================

# Configure processors to enhance or manipulate events generated by the beat.

processors:

- add\_host\_metadata: ~

- add\_cloud\_metadata: ~

- add\_docker\_metadata: ~

- add\_kubernetes\_metadata: ~

#================================ Logging =====================================

# Sets log level. The default log level is info.

# Available log levels are: error, warning, info, debug

#logging.level: debug

# At debug level, you can selectively enable logging only for some components.

# To enable all selectors use ["\*"]. Examples of other selectors are "beat",

# "publish", "service".

#logging.selectors: ["\*"]

#============================== X-Pack Monitoring ===============================

# filebeat can export internal metrics to a central Elasticsearch monitoring

# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The

# reporting is disabled by default.

# Set to true to enable the monitoring reporter.

#monitoring.enabled: false

# Sets the UUID of the Elasticsearch cluster under which monitoring data for this

# Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch

# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.

#monitoring.cluster\_uuid:

# Uncomment to send the metrics to Elasticsearch. Most settings from the

# Elasticsearch output are accepted here as well.

# Note that the settings should point to your Elasticsearch _monitoring_ cluster.

# Any setting that is not set is automatically inherited from the Elasticsearch

# output configuration, so if you have the Elasticsearch output configured such

# that it is pointing to your Elasticsearch monitoring cluster, you can simply

# uncomment the following line.

#monitoring.elasticsearch:

#================================= Migration ==================================

# This allows to enable 6.7 migration aliases

#migration.6\_to\_7.enabled: true

==== Filebeat.yml ends --

Logstash conf file

input {  
beats {  
codec =\> json  
port =\> 5044  
ssl\_certificate =\> "/etc/logstash/ssl/logstash\_filebeats\_self\_signed.crt"  
ssl\_key =\> "/etc/logstash/logstash\_filebeats\_self\_signed.key"  
}  
s3 {  
"type" =\> "mobile"  
"region" =\> "us-west-2"  
"bucket" =\> "xyzw-mobile"  
"prefix" =\> "offline-logs/"  
"codec" =\> "json"  
}  
tcp {  
codec =\> json  
port =\> 10514  
ssl\_enable =\> false  
ssl\_verify =\> false  
type =\> "log4j-json"  
}  
}

filter {  
if [type] == "mobile" {  
date {  
match =\> ["[timestamp]", "UNIX\_MS"]  
target =\> "@timestamp"  
}  
fingerprint {  
key =\> "secret"  
method =\> "SHA256"  
concatenate\_sources =\> "true"  
source =\> ["chunkId", "@timestamp"]  
target =\> "[@metadata][fingerprint]"  
remove\_field=\>["chunkId", "timestamp"]  
}  
}  
else {  
json {  
source =\> "message"  
}  
}  
}  
output {  
if [type] == "mobile" {  
elasticsearch {  
hosts =\> ["search:443"]  
document\_id =\> "%{[@metadata][fingerprint]}"  
document\_type =\> "log4j-json"  
ssl =\> true  
flush\_size =\> 250000  
}  
}  
else {  
if [type] == "log" {  
elasticsearch {  
hosts =\> ["search:443"]  
document\_type =\> "log4j-json"  
ssl =\> true  
flush\_size =\> 250000  
}  
}  
else {  
elasticsearch {  
hosts =\> ["search:443"]  
ssl =\> true  
flush\_size =\> 250000  
}  
}  
}  
}

==== end of logstash.conf ==

---

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [June 9, 2020, 12:25am UTC](https://discuss.elastic.co/t/filebeat-is-not-able-to-connect-to-logstash/236066/4 "2020-06-09T00:25:50Z")

</div>

# Certificate for SSL client authentication

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

# Client Certificate Key

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

Those options are comments, unless they were corrupted when pasted into the forum.

---

<div class="post-metadata">

**Author:** ![NetRajan](https://avatars.discourse-cdn.com/v4/letter/n/a3d4f5/32.png) [@NetRajan](https://discuss.elastic.co/u/NetRajan)\
**Post date:** [June 9, 2020, 1:59pm UTC](https://discuss.elastic.co/t/filebeat-is-not-able-to-connect-to-logstash/236066/5 "2020-06-09T13:59:16Z")

</div>

They are commented. We only do server authentication.  
Hope that is what you are asking  
Please let me know

---

<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:** [July 7, 2020, 1:59pm UTC](https://discuss.elastic.co/t/filebeat-is-not-able-to-connect-to-logstash/236066/6 "2020-07-07T13:59:27Z")

</div>

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