ElasticSearch and stunnel

I was able to set up ElasticSearch with stunnel for a single node configuration and it works fantastic. But I am having trouble trying to do this for Zen multicast unicast.

On server 1, I have ...

Stunnel configuration

[es-server-native]
accept = 10.0.0.xx0:9300
connect = 127.0.0.1:9300
cert = stunnel.pem

      

elasticsearch.yml

network.host: 127.0.0.1
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["what do I put here since now the nodes are not accessible externally"]

      

On server 2, I have ...

Stunnel configuration

[es-server-native]
accept = 10.0.0.xx1:9300
connect = 127.0.0.1:9300
cert = stunnel.pem

      

elasticsearch.yml

network.host: 127.0.0.1
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["what do I put here since now the nodes are not accessible externally"]

      

If I try to make the local es machine my client and run ElasticSearch, I get a bind address error and ElasticSearch won't start.

On server 1

[es-client-native]
client = yes
accept = 127.0.0.1:9300
connect = 10.0.0.xx1:9300

      

On server 2

[es-client-native]
client = yes
accept = 127.0.0.1:9300
connect = 10.0.0.xx0:9300

      

Has anyone ever used stunnel to configure ElasticSearch on a cluster using unicast?

+3
elasticsearch stunnel


source to share


No one has answered this question yet

Check out similar questions:

599
Solr vs ElasticSearch
21
Can't connect to ElasticSearch server using Java API
7
Failed to connect to Dockerized elasticsearch via java-client
4
ElasticSearch ... Not so elastic?
3
routines: SSL23_GET_CLIENT_HELLO: unknown protocol (Redis Cluster + Stunnel)
2
Elasticsearch MasterNotDiscoveredException Java Host Client
1
can stunnel / spiped be used to keep Redis Cluster secure?
0
failed to connect to port 9300 via telnet
0
Elasticsearch crashes using network.host config
0
Adding a coordinator or client node to my existing cluster elasticsearch



All Articles
Loading...
X
Show
Funny
Dev
Pics