# Elastic is not running on port 9200

**URL:** https://discuss.elastic.co/t/elastic-is-not-running-on-port-9200/193960
**Category:** Elasticsearch
**Created:** [August 6, 2019, 8:04am UTC](https://discuss.elastic.co/t/elastic-is-not-running-on-port-9200/193960 "2019-08-06T08:04:09Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![tomsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomsk/32/22061_2.png) [@tomsk](https://discuss.elastic.co/u/tomsk)
#### Post date: [August 6, 2019, 8:04am UTC](https://discuss.elastic.co/t/elastic-is-not-running-on-port-9200/193960/1 "2019-08-06T08:04:09Z")

</div>

Hello, l started Elasticsearch using `docker-compose.yml`:

```
version: '2'
services:
  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:5.6.16
    container_name: elasticsearch
    restart: unless-stopped
    environment:
      - "network.host=127.0.0.1"
      - "http.port=9200"
      - "cluster.name=elasticsearch"
      - "node.name=\"db-master\""
      - "node.master=true"
      - "node.data=true"
      - "bootstrap.memory_lock=true"
      - "ES_JAVA_OPTS=-Xms1g -Xmx1g"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    mem_limit: 2g
    volumes:
      - esdata:/usr/share/elasticsearch/data
    ports:
      - 9200:9200
    networks:
      - esnet

volumes:
  esdata:
    driver: local

networks:
  esnet:

```

This is output from `docker container ls`:

```
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a2ddd5cee8dc docker.elastic.co/elasticsearch/elasticsearch:5.6.16 "/bin/bash bin/es-do…" 12 hours ago Up 12 hours 0.0.0.0:9200->9200/tcp, 9300/tcp elasticsearch

```

But I cannot access it from console like `curl -XGET 'localhost:9200'`, I get:

`curl: (56) Recv failure: Connection reset by peer`

I would like to know where is a problem.

---

<div class="post-metadata">

### 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: [August 6, 2019, 8:19am UTC](https://discuss.elastic.co/t/elastic-is-not-running-on-port-9200/193960/2 "2019-08-06T08:19:10Z")

</div>

Change network host to 0.0.0.0 as 127.0.0.1 is only available from within the container.

---

<div class="post-metadata">

### Author: ![tomsk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tomsk/32/22061_2.png) [@tomsk](https://discuss.elastic.co/u/tomsk)
#### Post date: [August 6, 2019, 9:09am UTC](https://discuss.elastic.co/t/elastic-is-not-running-on-port-9200/193960/3 "2019-08-06T09:09:14Z")

</div>

But it listens on all addresses, I don't want to be it reachable from internet, because it is going to be running on production server, so I want to bind it to localhost only.

---

<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: [September 3, 2019, 9:09am UTC](https://discuss.elastic.co/t/elastic-is-not-running-on-port-9200/193960/4 "2019-09-03T09:09:20Z")

</div>

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