# Unable to GET endpoint

**URL:** <https://discuss.elastic.co/t/unable-to-get-endpoint/123143>\
**Category:** Elasticsearch\
**Created:** [March 8, 2018, 9:36pm UTC](https://discuss.elastic.co/t/unable-to-get-endpoint/123143 "2018-03-08T21:36:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Darnell\_Martin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darnell_martin/32/59411_2.png) [@Darnell\_Martin](https://discuss.elastic.co/u/Darnell_Martin)\
**Post date:** [March 8, 2018, 9:36pm UTC](https://discuss.elastic.co/t/unable-to-get-endpoint/123143/1 "2018-03-08T21:36:14Z")

</div>

I am having an issue running the command `curl -XGET -k -u username:password https://localhost:9200/_cat/health` on Elasticsearch 6.2.2 with X-Pack installed. It is returning a 500 error whenever the `xpack.security.audit.enabled` option is set to 'true'. However other endpoints such as "[https://localhost:9200/\_cat/nodes](https://localhost:9200/_cat/nodes)" work fine when the option is set to true.

Output from running command:

```auto
{"error":{"root_cause":[{"type":"null_pointer_exception","reason":null}],"type":"null_pointer_exception","reason":null},"status":500}

```

Any help would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [March 8, 2018, 9:49pm UTC](https://discuss.elastic.co/t/unable-to-get-endpoint/123143/2 "2018-03-08T21:49:08Z")

</div>

I moved this to #x-pack.  
Do you have a stacktrace in elasticsearch logs?  
If so could you share it?

---

<div class="post-metadata">

**Author:** ![Darnell\_Martin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darnell_martin/32/59411_2.png) [@Darnell\_Martin](https://discuss.elastic.co/u/Darnell_Martin)\
**Post date:** [March 8, 2018, 10:17pm UTC](https://discuss.elastic.co/t/unable-to-get-endpoint/123143/3 "2018-03-08T22:17:16Z")

</div>

Thanks for your response, I do have a stack trace but it seems that the WARN message is too long to be posted here.

---

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [March 8, 2018, 10:35pm UTC](https://discuss.elastic.co/t/unable-to-get-endpoint/123143/4 "2018-03-08T22:35:05Z")

</div>

I'm afraid that you've run into a known bug in 6.2.  
It will be fixed in the next release.

---

<div class="post-metadata">

**Author:** ![Darnell\_Martin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darnell_martin/32/59411_2.png) [@Darnell\_Martin](https://discuss.elastic.co/u/Darnell_Martin)\
**Post date:** [March 9, 2018, 1:36pm UTC](https://discuss.elastic.co/t/unable-to-get-endpoint/123143/5 "2018-03-09T13:36:58Z")

</div>

Thanks for your time!

---

<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:** [April 6, 2018, 1:37pm UTC](https://discuss.elastic.co/t/unable-to-get-endpoint/123143/6 "2018-04-06T13:37:12Z")

</div>

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