# 500 Error: Synonym file can't be read

**URL:** <https://discuss.elastic.co/t/500-error-synonym-file-cant-be-read/62345>\
**Category:** Elasticsearch\
**Created:** [October 6, 2016, 7:49am UTC](https://discuss.elastic.co/t/500-error-synonym-file-cant-be-read/62345 "2016-10-06T07:49:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\
**Post date:** [October 6, 2016, 8:12am UTC](https://discuss.elastic.co/t/500-error-synonym-file-cant-be-read/62345/2 "2016-10-06T08:12:33Z")

</div>

`"reason":"access denied`

Since 2.0 (introduction of security manager) it is no longer possible to set custom file path outside CONF\_DIR for \*\_path settings in char or token filters. You must specify either relative path to CONF\_DIR location or absolute path inside CONF\_DIR location.

---

_[View the full topic](https://discuss.elastic.co/t/500-error-synonym-file-cant-be-read/62345)._
