Kibana and elasticsearch unavailable on domain

I have installed Kibana and elasticsearch on Win 10 using the docker-compose but after trying on a Ubuntu server the installation doesn’t seem to be working.
Elastic search is responding normally to curl -XGET https://localhost:9200 -u admin:admin --insecure
and Kibana responds with a 302 on curl 0.0.0.0:5601 -i and they both seem to be up when checking docker-compose ps -a but unavailable outside of the server even if they are pointing to the correct ports?
I have tried various combinations of NETWORK_HOST, HTTP_HOST and SERVER_HOST values in docker-compose.yml for kibana but to no avail. Is it even possible to expose Kibana and elasticsearch without the use of an Nginx proxy?

Hi @nickgregz,

Can you share your compose.yml file? This makes it easier to reproduce the problems you are having.

It was a mistake on my part not opening the ports on AWS EC2 but even after doing so the Kibana is available but elasticsearch isn't, here is my docker-compose.yml:

version: '3'
services:
odfe-node1:
image: amazon/opendistro-for-elasticsearch:1.2.0
container_name: odfe-node1
environment:

  • cluster.name=odfe-cluster
  • node.name=odfe-node1
  • discovery.seed_hosts=odfe-node1,odfe-node2
  • cluster.initial_master_nodes=odfe-node1,odfe-node2
  • bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
  • "ES_JAVA_OPTS=-Xms512m -Xmx512m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
    ulimits:
    memlock:
    soft: -1
    hard: -1
    nofile:
    soft: 65536 # maximum number of open files for the Elasticsearch user, set to at least 65536 on modern systems
    hard: 65536
    volumes:
  • ./config/root-ca.pem:/usr/share/elasticsearch/config/root-ca.pem
  • ./config/esnode.pem:/usr/share/elasticsearch/config/esnode.pem
  • ./config/esnode-key.pem:/usr/share/elasticsearch/config/esnode-key.pem
  • ./config/kirk.pem:/usr/share/elasticsearch/config/kirk.pem
  • ./config/kirk-key.pem:/usr/share/elasticsearch/config/kirk-key.pem
  • odfe-data1:/usr/share/elasticsearch/data
  • ./elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml
  • ./security.config.yml:/usr/share/elasticsearch/plugins/opendistro_security/securityconfig/config.yml
    ports:
  • 9200:9200
  • 9600:9600 # required for Performance Analyzer
    networks:
  • odfe-net
    odfe-node2:
    image: amazon/opendistro-for-elasticsearch:1.2.0
    container_name: odfe-node2
    environment:
  • cluster.name=odfe-cluster
  • node.name=odfe-node2
  • discovery.seed_hosts=odfe-node1,odfe-node2
  • cluster.initial_master_nodes=odfe-node1,odfe-node2
  • bootstrap.memory_lock=true
  • "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    ulimits:
    memlock:
    soft: -1
    hard: -1
    nofile:
    soft: 65536
    hard: 65536
    volumes:
  • ./config/root-ca.pem:/usr/share/elasticsearch/config/root-ca.pem
  • ./config/esnode.pem:/usr/share/elasticsearch/config/esnode.pem
  • ./config/esnode-key.pem:/usr/share/elasticsearch/config/esnode-key.pem
  • ./config/kirk.pem:/usr/share/elasticsearch/config/kirk.pem
  • ./config/kirk-key.pem:/usr/share/elasticsearch/config/kirk-key.pem
  • odfe-data1:/usr/share/elasticsearch/data
  • ./elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml
  • ./security.config.yml:/usr/share/elasticsearch/plugins/opendistro_security/securityconfig/config.yml
    networks:
  • odfe-net
    kibana:
    image: amazon/opendistro-for-elasticsearch-kibana:1.2.0
    container_name: odfe-kibana
    ports:
  • 5601:5601
    expose:
  • "5601"
    environment:
    ELASTICSEARCH_URL: https://odfe-node1:9200
    ELASTICSEARCH_HOSTS: https://odfe-node1:9200
    volumes:
  • ./kibana.yml:/usr/share/kibana/config/kibana.yml
    networks:
  • odfe-net

volumes:
odfe-data1:
odfe-data2:

networks:
odfe-net:

Hi @nickgregz

OpenDistro is not an Elastic product or maintained or supported by us. You can leave the question here open and maybe someone from the community has a similar issue and will be able to help, but we're sorry that we are not always able to help out with third party products. In general I would recommend you to ask that question in the OpenDistro forums or to their support.

Cheers,
Tim