# "Signed fields invalid" for configuring HTTPS transport layer

**URL:** <https://discuss.elastic.co/t/signed-fields-invalid-for-configuring-https-transport-layer/262491>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [January 28, 2021, 11:43am UTC](https://discuss.elastic.co/t/signed-fields-invalid-for-configuring-https-transport-layer/262491 "2021-01-28T11:43:15Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![gvx3](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gvx3/32/82972_2.png) [@gvx3](https://discuss.elastic.co/u/gvx3)\
**Post date:** [January 29, 2021, 6:53am UTC](https://discuss.elastic.co/t/signed-fields-invalid-for-configuring-https-transport-layer/262491/3 "2021-01-29T06:53:01Z")

</div>

yes, I have just separated them and it's fine now, but there's 1 more problem about file read exception. I'm following this [https://discuss.elastic.co/t/trying-to-set-up-tls-on-elastic-cluster/143323/2](https://discuss.elastic.co/t/trying-to-set-up-tls-on-elastic-cluster/143323/2) article, and I am trying to find the configuration path of `es.path.conf` in this helm chart. This path `/usr/share/elasticsearch/config/` maybe not the right folder for the read permission although all files here have 777 permission. I've read the log but I haven't found the path. Do you have any idea ?

---

_[View the full topic](https://discuss.elastic.co/t/signed-fields-invalid-for-configuring-https-transport-layer/262491)._