# Kibana and elasticsearch unavailable on domain **URL:** \ **Category:** Kibana\ **Created:** [October 10, 2019, 2:11pm UTC](https://discuss.elastic.co/t/kibana-and-elasticsearch-unavailable-on-domain/203042 "2019-10-10T14:11:28Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![nickgregz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickgregz/32/54533_2.png) [@nickgregz](https://discuss.elastic.co/u/nickgregz)\ **Post date:** [October 10, 2019, 2:11pm UTC](https://discuss.elastic.co/t/kibana-and-elasticsearch-unavailable-on-domain/203042/1 "2019-10-10T14:11:28Z")
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? ---
**Author:** ![flash1293](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flash1293/32/41227_2.png) [@flash1293](https://discuss.elastic.co/u/flash1293)\ **Post date:** [October 10, 2019, 3:06pm UTC](https://discuss.elastic.co/t/kibana-and-elasticsearch-unavailable-on-domain/203042/2 "2019-10-10T15:06:52Z")
Hi @nickgregz, Can you share your `compose.yml` file? This makes it easier to reproduce the problems you are having. ---
**Author:** ![nickgregz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickgregz/32/54533_2.png) [@nickgregz](https://discuss.elastic.co/u/nickgregz)\ **Post date:** [October 11, 2019, 11:17am UTC](https://discuss.elastic.co/t/kibana-and-elasticsearch-unavailable-on-domain/203042/3 "2019-10-11T11:17:49Z")
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](https://odfe-node1:9200) > ELASTICSEARCH\_HOSTS: [https://odfe-node1:9200](https://odfe-node1:9200) > volumes: > - ./kibana.yml:/usr/share/kibana/config/kibana.yml > networks: > - odfe-net > > volumes: > odfe-data1: > odfe-data2: > > networks: > odfe-net: ---
**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\ **Post date:** [October 11, 2019, 12:21pm UTC](https://discuss.elastic.co/t/kibana-and-elasticsearch-unavailable-on-domain/203042/4 "2019-10-11T12:21:13Z")
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 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 8, 2019, 12:21pm UTC](https://discuss.elastic.co/t/kibana-and-elasticsearch-unavailable-on-domain/203042/5 "2019-11-08T12:21:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.