I have created a demo server to play around and i am trying to make elasticsearch remotely accessible for some services of mine.
I have set
network.host : 0.0.0.0 -> not working
network.host : xxx.xxx.xxx.xxx -> not working
I can get replies from browser level trying queries etc. bt curl gets access refused.
This leads to the extension i am tryng out(not mine) to say that elastic is unreachable.
Also curl from any other machine other then the local one responds with access refused.
Ip tables are flushed and no rules are being applied atm.
If bootstrap check fails then elastic does not start.
So no. I have even configured optimizations that the elastic docs suggest , except the ones for locking the memory since i run a ton of stuff every now and then on that demo.
Also it's not a resource matter. Machine got a spare 50gigs of ram and 8 cores doing nothing atm.
Running on CentOS 7 and installed via yum f that helps.
Also i've had a similar problem with udp6 before that i never managed to solve.
tcp6 seems that it should be working with both ipv4 and ipv6. This is beyond me though.
Disabling ipv6 seems like a bad solution for 2017.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.