# Elastic Search 2.2 remote access issue

**URL:** <https://discuss.elastic.co/t/elastic-search-2-2-remote-access-issue/81278>\
**Category:** Elasticsearch\
**Created:** [April 5, 2017, 9:07am UTC](https://discuss.elastic.co/t/elastic-search-2-2-remote-access-issue/81278 "2017-04-05T09:07:59Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adminxfactory](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@Adminxfactory](https://discuss.elastic.co/u/Adminxfactory)\
**Post date:** [April 5, 2017, 9:07am UTC](https://discuss.elastic.co/t/elastic-search-2-2-remote-access-issue/81278/1 "2017-04-05T09:07:59Z")

</div>

I am unable to access Elastic search 2.2 installed on my inhouse server with Centos 7.

I am able to access through local host.

Please help.

---

<div class="post-metadata">

**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\
**Post date:** [April 5, 2017, 11:12pm UTC](https://discuss.elastic.co/t/elastic-search-2-2-remote-access-issue/81278/2 "2017-04-05T23:12:42Z")

</div>

By default ES will only bind to localhost, you can change this by setting `network.host` in elasticsearch.yml, for example:

```
network.host: 0.0.0.0

```

Make sure that you have secured your Elasticsearch instance first!

---

<div class="post-metadata">

**Author:** ![Adminxfactory](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@Adminxfactory](https://discuss.elastic.co/u/Adminxfactory)\
**Post date:** [April 6, 2017, 4:27am UTC](https://discuss.elastic.co/t/elastic-search-2-2-remote-access-issue/81278/3 "2017-04-06T04:27:09Z")

</div>

Appreciated you reply

We have already tried this but did not work

elasticsearch.yml

network.host: 192.168.0.1/24

---

<div class="post-metadata">

**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\
**Post date:** [April 6, 2017, 3:10pm UTC](https://discuss.elastic.co/t/elastic-search-2-2-remote-access-issue/81278/4 "2017-04-06T15:10:58Z")

</div>

Muthyam Reddy writes:

> We have already tried this but did not work
> 
> elasticsearch.yml
> 
> network.host: 192.168.0.1/24

That is an illegal value for `network.host`, you would want to set it to  
something like `network.host: 192.168.0.4` (an actual IP, not a CIDR  
mask).

---

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [April 6, 2017, 3:26pm UTC](https://discuss.elastic.co/t/elastic-search-2-2-remote-access-issue/81278/5 "2017-04-06T15:26:58Z")

</div>

Any iptables maybe ?

---

<div class="post-metadata">

**Author:** ![Adminxfactory](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@Adminxfactory](https://discuss.elastic.co/u/Adminxfactory)\
**Post date:** [April 6, 2017, 6:59pm UTC](https://discuss.elastic.co/t/elastic-search-2-2-remote-access-issue/81278/6 "2017-04-06T18:59:45Z")

</div>

We fixed the issue thank you

---

<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:** [May 4, 2017, 6:59pm UTC](https://discuss.elastic.co/t/elastic-search-2-2-remote-access-issue/81278/7 "2017-05-04T18:59:51Z")

</div>

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