# Issue with elasticsearch on remote server

**URL:** <https://discuss.elastic.co/t/issue-with-elasticsearch-on-remote-server/157748>\
**Category:** Elasticsearch\
**Created:** [November 21, 2018, 4:44pm UTC](https://discuss.elastic.co/t/issue-with-elasticsearch-on-remote-server/157748 "2018-11-21T16:44:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Omar\_1CPI2011\_BRAHIM](https://avatars.discourse-cdn.com/v4/letter/o/9de0a6/32.png) [@Omar\_1CPI2011\_BRAHIM](https://discuss.elastic.co/u/Omar_1CPI2011_BRAHIM)\
**Post date:** [November 21, 2018, 4:44pm UTC](https://discuss.elastic.co/t/issue-with-elasticsearch-on-remote-server/157748/1 "2018-11-21T16:44:28Z")

</div>

I have installed elasticsearch on my server having this ip address W.X.Y.Z

I am able to run  
`./elasticsearch-6.3.2/bin/elasticsearch`

The elasticsearch service is accessible on localhost (remote server) but I can't access it from my locale machine with the browser at this address [http://W.X.Y.Z:9200/](http://w.x.y.z:9200/)

Then I tried to change the elasticsearch-6.3.2/config/elasticsearch.yml file by adding the following lines (please see the attached screenshot)

```
network.host: 0.0.0.0
http.port: 9200

```

And at this time, I'm not able to run

`./elasticsearch-6.3.2/bin/elasticsearch`

Error is telling me

```
ERROR: [2] bootstrap checks failed
[1]: max number of threads [3903] for user [developer] is too low, increase to at least [4096]
[2]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
[2018-11-21T17:27:58,309][INFO][o.e.n.Node] [b1qDVeW] stopping ...
[2018-11-21T17:27:58,346][INFO][o.e.n.Node] [b1qDVeW] stopped
[2018-11-21T17:27:58,347][INFO][o.e.n.Node] [b1qDVeW] closing ...
[2018-11-21T17:27:58,377][INFO][o.e.n.Node] [b1qDVeW] closed
[2018-11-21T17:27:58,380][INFO][o.e.x.m.j.p.NativeController] Native controller process has stopped - no new native processes can be started
```

---

<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:** [November 21, 2018, 9:54pm UTC](https://discuss.elastic.co/t/issue-with-elasticsearch-on-remote-server/157748/2 "2018-11-21T21:54:38Z")

</div>

You will need to make sure you have correctly applied all of these - [https://www.elastic.co/guide/en/elasticsearch/reference/6.5/bootstrap-checks.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.5/bootstrap-checks.html)

---

<div class="post-metadata">

**Author:** ![Omar\_1CPI2011\_BRAHIM](https://avatars.discourse-cdn.com/v4/letter/o/9de0a6/32.png) [@Omar\_1CPI2011\_BRAHIM](https://discuss.elastic.co/u/Omar_1CPI2011_BRAHIM)\
**Post date:** [November 22, 2018, 1:20pm UTC](https://discuss.elastic.co/t/issue-with-elasticsearch-on-remote-server/157748/3 "2018-11-22T13:20:41Z")

</div>

Sorry, this issue is reported [here](https://stackoverflow.com/questions/53416545/issue-with-limits-with-elasticsearch) and it is solved

---

<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:** [December 20, 2018, 1:20pm UTC](https://discuss.elastic.co/t/issue-with-elasticsearch-on-remote-server/157748/4 "2018-12-20T13:20:42Z")

</div>

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