# Securing Port 9200

**URL:** <https://discuss.elastic.co/t/securing-port-9200/182422>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [May 23, 2019, 11:58am UTC](https://discuss.elastic.co/t/securing-port-9200/182422 "2019-05-23T11:58:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [May 23, 2019, 11:58am UTC](https://discuss.elastic.co/t/securing-port-9200/182422/1 "2019-05-23T11:58:56Z")

</div>

Hi,  
When upgrading to 6.8.0 is it possible to configure port 9200 to accept both http and https traffic? Or is that the default when enabling ssl?

A hard cutover will cause problems with client teams who don't get the message to reconfigure...

Regards,  
D

---

<div class="post-metadata">

**Author:** ![jpcarey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpcarey/32/46668_2.png) [@jpcarey](https://discuss.elastic.co/u/jpcarey)\
**Post date:** [May 23, 2019, 10:24pm UTC](https://discuss.elastic.co/t/securing-port-9200/182422/2 "2019-05-23T22:24:03Z")

</div>

No. You would need to do that with something external like nginx. You can have different http settings for different nodes in the cluster, but seems like a lot of work to go through vs. just enforcing a cutover.

---

<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:** [June 20, 2019, 10:29pm UTC](https://discuss.elastic.co/t/securing-port-9200/182422/3 "2019-06-20T22:29:33Z")

</div>

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