# Unknown xpack transport settings after upgrading to ES 6

**URL:** <https://discuss.elastic.co/t/unknown-xpack-transport-settings-after-upgrading-to-es-6/96952>\
**Category:** Elasticsearch\
**Created:** [August 14, 2017, 11:06am UTC](https://discuss.elastic.co/t/unknown-xpack-transport-settings-after-upgrading-to-es-6/96952 "2017-08-14T11:06:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vb4t](https://avatars.discourse-cdn.com/v4/letter/v/a698b9/32.png) [@vb4t](https://discuss.elastic.co/u/vb4t)\
**Post date:** [August 14, 2017, 11:06am UTC](https://discuss.elastic.co/t/unknown-xpack-transport-settings-after-upgrading-to-es-6/96952/1 "2017-08-14T11:06:09Z")

</div>

I am trying to upgrade one ES node to 6.0.0-beta1 (xpack 6 included). It do not start with following error message:

`java.lang.IllegalArgumentException: unknown setting [transport.profiles.client.xpack.security.ssl.enabled] please check that any required plugins are installed, or check the breaking changes documentation for removed settings`

There is also following WARN:

`[xpack.security.transport.ssl.enabled] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for the next major version.`

Both settings are described in documentation for X-Pack 6. So is it problem with outdated documentation or is it a bug in X-Pack? Which settings to use instead of these two?

---

<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:** [August 15, 2017, 12:07am UTC](https://discuss.elastic.co/t/unknown-xpack-transport-settings-after-upgrading-to-es-6/96952/2 "2017-08-15T00:07:04Z")

</div>

> [@vb4t](#):
>
> So is it problem with outdated documentation

Yes, the documentation for X-Pack security is not yet 100% up-to-date with the features in the beta.

For 6.0 we made TLS (SSL) mandatory for intra-cluster communication. That means that `xpack.security.transport.ssl.enabled` no longer has any effect. It is always enabled if X-Pack security is enabled.

---

<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:** [September 12, 2017, 12:07am UTC](https://discuss.elastic.co/t/unknown-xpack-transport-settings-after-upgrading-to-es-6/96952/3 "2017-09-12T00:07:36Z")

</div>

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