# Elastic search 2.3.2 set Domain name with Https **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-security\ **Created:** [June 25, 2020, 3:16am UTC](https://discuss.elastic.co/t/elastic-search-2-3-2-set-domain-name-with-https/238590 "2020-06-25T03:16:18Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Manikandan\_Selvaraj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/manikandan_selvaraj/32/70351_2.png) [@Manikandan\_Selvaraj](https://discuss.elastic.co/u/Manikandan_Selvaraj)\ **Post date:** [June 25, 2020, 3:16am UTC](https://discuss.elastic.co/t/elastic-search-2-3-2-set-domain-name-with-https/238590/1 "2020-06-25T03:16:18Z")
Hi Team, We are using Elastic search 2.3.2 version. We plan to configure SSL for elastic search URL instead of HTTP to HTTPS as well mention in subDomain also password protect. We have installed Elastic search in Windows machine. Could you please share steps to achieve this in windows machine, Since it's in version 2.3.1 Thanks, Manikandan Selvaraj. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 25, 2020, 4:20am UTC](https://discuss.elastic.co/t/elastic-search-2-3-2-set-domain-name-with-https/238590/2 "2020-06-25T04:20:36Z")
With such an old and unsupported version I suspect the only way to secure it may be via a reverse proxy. I would recommend that you upgrade. ---
**Author:** ![Manikandan\_Selvaraj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/manikandan_selvaraj/32/70351_2.png) [@Manikandan\_Selvaraj](https://discuss.elastic.co/u/Manikandan_Selvaraj)\ **Post date:** [June 25, 2020, 4:30am UTC](https://discuss.elastic.co/t/elastic-search-2-3-2-set-domain-name-with-https/238590/3 "2020-06-25T04:30:46Z")
Hi @Christian_Dahlqvist, UnSupported means, which feature not support for this version - either password protection or Https configuration ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 25, 2020, 4:57am UTC](https://discuss.elastic.co/t/elastic-search-2-3-2-set-domain-name-with-https/238590/4 "2020-06-25T04:57:38Z")
There is no built in security in that version, which is why I suggested a reverse proxy. Elasticsearch 2.x is very old and has been EOL quite a while. ---
**Author:** ![Manikandan\_Selvaraj](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/manikandan_selvaraj/32/70351_2.png) [@Manikandan\_Selvaraj](https://discuss.elastic.co/u/Manikandan_Selvaraj)\ **Post date:** [June 25, 2020, 10:35am UTC](https://discuss.elastic.co/t/elastic-search-2-3-2-set-domain-name-with-https/238590/5 "2020-06-25T10:35:07Z")
Reverse proxy - You said like redirection? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 25, 2020, 10:45am UTC](https://discuss.elastic.co/t/elastic-search-2-3-2-set-domain-name-with-https/238590/6 "2020-06-25T10:45:32Z")
I have seen users use nginx as a reverse proxy and route http traffic through this. That is outside Elasticsearch though. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 23, 2020, 10:45am UTC](https://discuss.elastic.co/t/elastic-search-2-3-2-set-domain-name-with-https/238590/7 "2020-07-23T10:45:39Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.