# Filebeat: fail to execute the HTTP GET request

**URL:** <https://discuss.elastic.co/t/filebeat-fail-to-execute-the-http-get-request/213442>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 31, 2019, 11:38am UTC](https://discuss.elastic.co/t/filebeat-fail-to-execute-the-http-get-request/213442 "2019-12-31T11:38:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robin020](https://avatars.discourse-cdn.com/v4/letter/r/71c47a/32.png) [@Robin020](https://discuss.elastic.co/u/Robin020)\
**Post date:** [December 31, 2019, 11:38am UTC](https://discuss.elastic.co/t/filebeat-fail-to-execute-the-http-get-request/213442/1 "2019-12-31T11:38:52Z")

</div>

Hi,

Filebeat wants to do a http get request to [http://localhost:5601/api/status](http://localhost:5601/api/status) but it fails.  
I am having trouble with configure this on the right way in the filebeat.yml.

For Kibana I created a certificate and used that. See my config:

```
# 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
  # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  host: "localhost:5601"
  protocol: "https"
  username: "user"
  password: "password"
  server.ssl.enabled: true
  server.ssl.certificate: "<path to crt file>"
  server.ssl.key: "path to key file>"

```

Do I miss something?  
Is it possible to disable this check?

---

<div class="post-metadata">

**Author:** ![Alex\_Kristiansen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_kristiansen/32/46086_2.png) [@Alex\_Kristiansen](https://discuss.elastic.co/u/Alex_Kristiansen)\
**Post date:** [January 1, 2020, 5:24pm UTC](https://discuss.elastic.co/t/filebeat-fail-to-execute-the-http-get-request/213442/2 "2020-01-01T17:24:40Z")

</div>

@Robin020,

Can you post the log lines or output where you're seeing any errors?

---

<div class="post-metadata">

**Author:** ![Robin020](https://avatars.discourse-cdn.com/v4/letter/r/71c47a/32.png) [@Robin020](https://discuss.elastic.co/u/Robin020)\
**Post date:** [January 2, 2020, 1:31pm UTC](https://discuss.elastic.co/t/filebeat-fail-to-execute-the-http-get-request/213442/3 "2020-01-02T13:31:17Z")

</div>

Hey Alex,

I have solved that issue by disabling the option"setup.dashboards.enabled:"

Now I am facing another issue:

```
INFO pipeline/output.go:95 Connecting to backoff(async(tcp://127.0.0.1:9300))
INFO pipeline/output.go:105 Connection to backoff(async(tcp://127.0.0.1:9300)) established
ERROR logstash/async.go:256 Failed to publish events caused by: EOF
ERROR logstash/async.go:256 Failed to publish events caused by: client is not connected
ERROR pipeline/output.go:121 Failed to publish events: client is not connected

```

I don't know where to start troubleshooting for these messages.... Can you help?

This is my logstash.conf for filebeat:

```
input {
  beats {
    hosts => "127.0.0.1"
    client_inactivity_timeout => 300
    port => 9300
  }
}

output {
  elasticsearch {
    hosts => ["http://localhost:9200"]
    index => "%{[@metadata][beat]}-%{[@metadata][version]}"
    user => "user"
    password => "password"
  }
  stdout{}
}
```

---

<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:** [January 30, 2020, 1:31pm UTC](https://discuss.elastic.co/t/filebeat-fail-to-execute-the-http-get-request/213442/4 "2020-01-30T13:31:20Z")

</div>

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