# How to check server error on Nest 6.xx

**URL:** <https://discuss.elastic.co/t/how-to-check-server-error-on-nest-6-xx/142263>\
**Category:** Elasticsearch\
**Created:** [July 31, 2018, 12:54am UTC](https://discuss.elastic.co/t/how-to-check-server-error-on-nest-6-xx/142263 "2018-07-31T00:54:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oion71](https://avatars.discourse-cdn.com/v4/letter/o/eada6e/32.png) [@Oion71](https://discuss.elastic.co/u/Oion71)\
**Post date:** [July 31, 2018, 12:54am UTC](https://discuss.elastic.co/t/how-to-check-server-error-on-nest-6-xx/142263/1 "2018-07-31T00:54:00Z")

</div>

I used to use ElasticsearchClientException.Response.ServerError to check server error details on Nest 5.x. e.g., ex.Response.ServerError.Error.Type.Equals("index\_already\_exists\_exception", StringComparison.OrdinalIgnoreCase). However the property ServerError was removed from IApiCallDetails onNest 6.x. Is there any property to use for this purpose? The only way to check this seems to check the Message property of an exception.

---

<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:** [August 28, 2018, 12:59am UTC](https://discuss.elastic.co/t/how-to-check-server-error-on-nest-6-xx/142263/2 "2018-08-28T00:59:43Z")

</div>

Closed on August 28, 2018, 12:59am UTC

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