# Couldn't push logs to elasticsearch using filebeat

**URL:** <https://discuss.elastic.co/t/couldnt-push-logs-to-elasticsearch-using-filebeat/211165>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 9, 2019, 5:18pm UTC](https://discuss.elastic.co/t/couldnt-push-logs-to-elasticsearch-using-filebeat/211165 "2019-12-09T17:18:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bharath\_k](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bharath_k/32/59050_2.png) [@bharath\_k](https://discuss.elastic.co/u/bharath_k)\
**Post date:** [December 9, 2019, 5:18pm UTC](https://discuss.elastic.co/t/couldnt-push-logs-to-elasticsearch-using-filebeat/211165/1 "2019-12-09T17:18:58Z")

</div>

Hi Folks,

Iam running elasticsearch 6.7 as managed service in cloud. where in i want to push the logs from Kubernetes pods to elasticsearch using filebeat (6.8.5) configuration on https protocol but its giving response code 500 error. Below is the error  
`Preformatted text elasticsearch/elasticsearch.go:252	Error connecting to Elasticsearch at https://xxxxxx:30566: Connection marked as failed because the onConnect callback failed: cannot retrieve the elasticsearch license: error from server, response code: 500`

Please find my filebeat configuration also attaching here. please help me to resolve this issue. Thanks in advance

```
filebeat.inputs:
- type: log
  paths:
    - /var/log/*.*
  close_inactive: 1m
  json.keys_under_root: true
  json.add_error_key: true
  processors:
  - drop_fields:
      fields: ["error"]

output.elasticsearch:
 hosts: ["xxxxxx:30566"]
 username: ${USERNAME}
 password: ${PASSWORD}
 ssl.certificate_authorities:
  - /etc/cert/certificate.pem
 index: "testing"
setup.template:
  name: "test1"
  pattern: "test1in"
  enabled: true
```

---

<div class="post-metadata">

**Author:** ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)\
**Post date:** [December 10, 2019, 9:14am UTC](https://discuss.elastic.co/t/couldnt-push-logs-to-elasticsearch-using-filebeat/211165/2 "2019-12-10T09:14:08Z")

</div>

Hi @bharath_k,

I guess it has to do with the distribution of the managed Elasticsearch. It would be helpful to know what the provider you are running. If the cloud provider uses OSS then you should try with FIlebeat OSS too: [https://www.elastic.co/downloads/past-releases#filebeat-oss](https://www.elastic.co/downloads/past-releases#filebeat-oss)

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:** [January 7, 2020, 9:14am UTC](https://discuss.elastic.co/t/couldnt-push-logs-to-elasticsearch-using-filebeat/211165/3 "2020-01-07T09:14:11Z")

</div>

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