tribe: t1: cluster.name: Data1 discovery.zen.ping.unicast.hosts: ["x.x.x.x:9300"] xpack.security.transport.ssl.verification_mode: certificate xpack.security.transport.ssl.keystore.path: certs/estribe.p12 xpack.security.transport.ssl.truststore.path: certs/estribe.p12 xpack.security.transport…

As I said in the other thread you should look to use cross-cluster search instead as tribe nodes are being deprecated. Elasticsearch 6.8 is likely to be out of support soon as Elasticsearch 8 is approaching and setting up tribe nodes will as far as I know make it impossible to upgrade without switch…

X-pack security enable for tribe node

Elastic Security

warkolm (Mark Walkom) December 21, 2020, 9:45pm 5

I'll close this in favour of java.io.StreamCorruptedException: invalid internal transport message format, got (16,3,3,0) then.

Topic		Replies	Views
java.io.StreamCorruptedException: invalid internal transport message format, got (16,3,3,0) Elasticsearch	16	3682	December 24, 2020
Nodes disabled from Cluster when XPack SSL is enabled Elasticsearch elastic-stack-security	3	735	September 3, 2020
Shield 2.3.5 specifcally transport SSL/TLS failing Elasticsearch elastic-stack-security	16	2279	August 15, 2016
Xpack security feature showing inconsistent behavior Elasticsearch elastic-stack-security , docker	1	440	November 4, 2019
Can't add a new node to an es cluster with x-pack:enabled Elasticsearch elastic-stack-security	4	962	January 14, 2021

X-pack security enable for tribe node

Related topics