We have a 3 node ES cluster with kibana and logstash in a docker-compose.
I've also added NGINX to limit access to it just a little bit, and in time I will add user authentication to that.
Now I've added ElasticHQ to the docker-compose.
I've set up NGINX to accept on port 5100, and send requests on to the container elastichq on port 5000 (we have logstash on port 5000).
The container for elasticsearch is called elasticsearch.
It sort of works, but I had to add the internal network to allow access nginx for elasticsearch, which I didn't understand.
Why does it leave the internal docker network, to go to the outside of the nginx, instead of directly to the inside of it, and then with the internal ip?
I'm really confused about this.
General information
Issue Description
We have a 3 node ES cluster with kibana and logstash in a docker-compose. I've also added NGINX to limit access to it just a little bit, and in time I will add user authentication to that. Now I've added ElasticHQ to the docker-compose. I've set up NGINX to accept on port 5100, and send requests on to the container elastichq on port 5000 (we have logstash on port 5000). The container for elasticsearch is called elasticsearch.
It sort of works, but I had to add the internal network to allow access nginx for elasticsearch, which I didn't understand. Why does it leave the internal docker network, to go to the outside of the nginx, instead of directly to the inside of it, and then with the internal ip? I'm really confused about this.