# Locating rogue clients with authentication errors

**URL:** <https://discuss.elastic.co/t/locating-rogue-clients-with-authentication-errors/257102>\
**Category:** Elasticsearch\
**Created:** [November 30, 2020, 4:51pm UTC](https://discuss.elastic.co/t/locating-rogue-clients-with-authentication-errors/257102 "2020-11-30T16:51:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![franco-martin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/franco-martin/32/75862_2.png) [@franco-martin](https://discuss.elastic.co/u/franco-martin)\
**Post date:** [November 30, 2020, 4:51pm UTC](https://discuss.elastic.co/t/locating-rogue-clients-with-authentication-errors/257102/1 "2020-11-30T16:51:07Z")

</div>

Im using filebeat to export elasticsearch logs to well... elasticsearch. I get the authentication errors but not where they come from. I tried changing the log level to TRACE for the rest package but no luck.  
Is there a way to trace where the authentication is coming from?

---

<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:** [December 28, 2020, 4:51pm UTC](https://discuss.elastic.co/t/locating-rogue-clients-with-authentication-errors/257102/2 "2020-12-28T16:51:12Z")

</div>

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