# Unable to find apikey warning

**URL:** <https://discuss.elastic.co/t/unable-to-find-apikey-warning/335956>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [June 14, 2023, 8:55am UTC](https://discuss.elastic.co/t/unable-to-find-apikey-warning/335956 "2023-06-14T08:55:11Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Yang\_Wang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yang_wang/32/48857_2.png) [@Yang\_Wang](https://discuss.elastic.co/u/Yang_Wang)\
**Post date:** [June 19, 2023, 3:59am UTC](https://discuss.elastic.co/t/unable-to-find-apikey-warning/335956/4 "2023-06-19T03:59:38Z")

</div>

Please refer to this reply and see if it helps

> [@Authentication using apikey failed](https://discuss.elastic.co/t/authentication-using-apikey-failed/333244/5):
>
> In that case, you can try HttpTracer which will report the remote address of each request. PUT \_cluster/settings { "persistent" : { "logger.org.elasticsearch.http.HttpTracer" : "TRACE" } } The logs will get quite verbose. You should see something like the follows for the failed API key authentication received request from [Netty4HttpChannel{localAddress=/[0:0:0:0:0:0:0:1]:9200, remoteAddress=/[0:0:0:0:0:0:0:1]:53497}]org.elasticsearch.http.HttpHeadersValidationException: org.ela…

---

_[View the full topic](https://discuss.elastic.co/t/unable-to-find-apikey-warning/335956)._