# Having an issue with filebeat pushing to Elasticsearch

**URL:** <https://discuss.elastic.co/t/having-an-issue-with-filebeat-pushing-to-elasticsearch/271822>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 30, 2021, 6:05pm UTC](https://discuss.elastic.co/t/having-an-issue-with-filebeat-pushing-to-elasticsearch/271822 "2021-04-30T18:05:38Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 3, 2021, 11:28pm UTC](https://discuss.elastic.co/t/having-an-issue-with-filebeat-pushing-to-elasticsearch/271822/4 "2021-05-03T23:28:42Z")

</div>

Did you fix the rest of the formatting?  
Is your elasticsearch really running on https?  
did you enable security authentication etc. setup certs do all that stuff?

Looks like bad creds... that is the error you get with bad creds...

pretty simple try to curl from filebeat host with the same host and creds that are in the `elasticsearch.output` section filebeat.yml see what you get

First try this is ignores the self signed cert.  
`curl --insecure -u "username:password" https://elastichost:9200`

---

_[View the full topic](https://discuss.elastic.co/t/having-an-issue-with-filebeat-pushing-to-elasticsearch/271822)._