# Remote access elasticsearch 9200 fails

**URL:** <https://discuss.elastic.co/t/remote-access-elasticsearch-9200-fails/37969>\
**Category:** Elasticsearch\
**Created:** [December 25, 2015, 9:46am UTC](https://discuss.elastic.co/t/remote-access-elasticsearch-9200-fails/37969 "2015-12-25T09:46:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![djougue\_basso](https://avatars.discourse-cdn.com/v4/letter/d/96bed5/32.png) [@djougue\_basso](https://discuss.elastic.co/u/djougue_basso)\
**Post date:** [December 25, 2015, 9:46am UTC](https://discuss.elastic.co/t/remote-access-elasticsearch-9200-fails/37969/1 "2015-12-25T09:46:53Z")

</div>

Hi guy,  
I have a problem that i am facing but i didn't found solution in the forum and into elasticsearch official documentation. I have successfully installed elasticsearch 1.7.3 in OVH cloud machin and being able to connect via localhost through the curl localhost:9200. But i tried to connect remotely using [http://158.69.78.66:9200/](http://158.69.78.66:9200/) (where 158.69.78.66 is the server address) without success. Please which configuration am i going to more in order to be able to remotely access elasticSearch in my server.

The attached file represent my elasticsearch.yml actual configuration.

Thanks,

---

<div class="post-metadata">

**Author:** ![GlenRSmith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/glenrsmith/32/44925_2.png) [@GlenRSmith](https://discuss.elastic.co/u/GlenRSmith)\
**Post date:** [December 25, 2015, 3:50pm UTC](https://discuss.elastic.co/t/remote-access-elasticsearch-9200-fails/37969/2 "2015-12-25T15:50:01Z")

</div>

You need to configure your server so that port 9200 is open.

---

<div class="post-metadata">

**Author:** ![djougue\_basso](https://avatars.discourse-cdn.com/v4/letter/d/96bed5/32.png) [@djougue\_basso](https://discuss.elastic.co/u/djougue_basso)\
**Post date:** [December 25, 2015, 7:43pm UTC](https://discuss.elastic.co/t/remote-access-elasticsearch-9200-fails/37969/3 "2015-12-25T19:43:53Z")

</div>

Thanks for your responstance. Does it means that elasticSearch doesn't have  
itself restriction against remote access?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [December 25, 2015, 8:19pm UTC](https://discuss.elastic.co/t/remote-access-elasticsearch-9200-fails/37969/4 "2015-12-25T20:19:20Z")

</div>

Have you read [Connectivity issues with a new/upgraded 2.X cluster? Read here first :)](https://discuss.elastic.co/t/connectivity-issues-with-a-new-upgraded-2-x-cluster-read-here-first/35699)?

---

<div class="post-metadata">

**Author:** ![harishkumar.ie](https://avatars.discourse-cdn.com/v4/letter/h/85f322/32.png) [@harishkumar.ie](https://discuss.elastic.co/u/harishkumar.ie)\
**Post date:** [May 29, 2017, 4:10pm UTC](https://discuss.elastic.co/t/remote-access-elasticsearch-9200-fails/37969/5 "2017-05-29T16:10:37Z")

</div>

When elasticsearch is installed and run without any configuration changes by default it binds to localhost only. To access the elasticsearch REST API endpoint remotely the below changes has to be made on the server where elasticsearch has been installed.

**Elasticsearch Configuration Change**  
Update the network.host property in elasticsearch.yml as per the guidelines provided in the [elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html). For example to bind to all IPv4 addresses on the local machine, change as below network.host : 0.0.0.0  
**Firewall Rules Update**  
Update the Linux firewall to allow access to port 9200. Please refer your Linux documentation for adding rules to the firewall.  
For example to allow access to all the servers(public) in CentosOS use the [firewall-cmd](http://www.firewalld.org/documentation/man-pages/firewall-cmd.html)  
$ sudo firewall-cmd --zone=public --permanent --add-port=9200/tcp  
success  
$ sudo firewall-cmd --reload  
success

Note : In production environment public access is discouraged. A restricted access should be preferred.

---

<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:** [July 5, 2017, 9:59pm UTC](https://discuss.elastic.co/t/remote-access-elasticsearch-9200-fails/37969/6 "2017-07-05T21:59:54Z")

</div>


