Thanks again Koji for replying and understanding my concern,
I did apply the changes you suggested but still i'm getting same
SSLHandshake error. I believe the Site2Site Remote Listener doesn't run a
server socket with the hostname we specify in *'nifi.remote.input.host'* in
nifi.properties
Hi Nadeem,
> nifi.remote.input.host=
This property is used for how S2S server introduces itself to S2S
clients for further network communication.
For example, let's say if the server has 2 ip addresses, private and
public, and the public ip is bounded to a fqdn. hostnames for the
server would be:
Thank you so much Koji for replying,
This issue of SSL Handshake we see is for a single node cluster instance,
where our NiFi application has been deployed in Kubernetes container, Here
is the below configuration we did for site-to-site in nifi.properties file
for a single cluster node.
# Site
Hi Nadeem,
How many S2S clients are connecting to your NiFi? And how many NiFi
nodes does your remote NiFi have?
I've encountered the same error message when I conducted a test using
hundreds of S2S client connecting to a single NiFi node.
It happened in a situation like followings:
1. A S2S
Hi,
Can someone please help me resolving SSLHandshake issue (Site-to-Site) which
I'm getting in logs. This ERROR doesn't impact us from accessing the NiFi
canvas or any calls we make from Nifi components (like SSL Context Service).
This is something which keeps on throwing every now and then in
