Handshake failed. unexpected remote node – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

Briefly, this error occurs when the client tries to connect to an unexpected node in the Elasticsearch cluster. This could be due to a misconfigured client or issues with the cluster’s network configuration. You will need to resolve the issue to establish a successful connection.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” handshake failed. unexpected remote node ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node.

Log Context

Log “handshake failed. unexpected remote node”classname  is TransportService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return (newConnection; actualProfile; listener) -> {
 // We don't validate cluster names to allow for CCS connections.
 handshake(newConnection; actualProfile.getHandshakeTimeout().millis(); cn -> true; ActionListener.map(listener; resp -> {
 final DiscoveryNode remote = resp.discoveryNode;
 if (node.equals(remote) == false) {
 throw new ConnectTransportException(node; "handshake failed. unexpected remote node " + remote);
 return null;


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content