Port 9300 (TCP) is the standard for Elasticsearch inter-node. Elasticsearch uses 2 ports: 9200 (HTTP REST API) and 9300 (transport for inter-node communication inside the cluster). 9300 binary protocol, not HTTP. Access needed only between ma
Below: what uses this port, security considerations, online check, FAQ.
Free online tool — ping & port checker: instant results, no signup.
Elasticsearch inter-node
Elasticsearch uses 2 ports: 9200 (HTTP REST API) and 9300 (transport for inter-node communication inside the cluster). 9300 binary protocol, not HTTP. Access needed only between master+data nodes.
Never expose 9300 publicly. Bind only to private network + transport.tls.enabled=true. Otherwise a compromised worker can join the cluster.
Enterno.io Ping + Port checker tests TCP reachability of any port from our server in Moscow.
Elasticsearch is designed to function as a distributed search and analytics engine, which necessitates efficient communication between nodes in a cluster. Port 9300 (TCP) is utilized for this inter-node communication via a binary protocol, allowing nodes to share data and coordinate tasks effectively. Unlike the HTTP-based communication on port 9200, which interacts with clients and external applications, port 9300 is strictly for internal use within the cluster.
This port is essential for various operations, including:
Due to its critical role in cluster management, securing port 9300 is vital to prevent unauthorized access and potential data breaches.
When setting up an Elasticsearch cluster, configuring port 9300 correctly is crucial for ensuring smooth inter-node communication. Below are some practical examples of how to configure Elasticsearch to utilize port 9300 effectively:
1. Elasticsearch Configuration File:
In your elasticsearch.yml configuration file, you can specify the transport settings as follows:
transport.host: 0.0.0.0
transport.tcp.port: 9300This setting allows the node to listen on all network interfaces for incoming requests on port 9300.
2. Starting Elasticsearch with Custom Port:
If you wish to start Elasticsearch with a custom transport port, you can do so using the following command:
bin/elasticsearch -E transport.tcp.port=9301This will override the default port and allow you to specify an alternative for inter-node communication.
3. Testing Node Connectivity:
To test if a node is reachable via port 9300, you can use the following command:
nc -zv 9300 If the connection is successful, it indicates that the node is accessible for inter-node communication.
Securing port 9300 is paramount, as it is a potential attack vector for unauthorized access to your Elasticsearch cluster. Here are key security considerations to keep in mind:
elasticsearch.yml file:xpack.security.enabled: true
xpack.security.transport.ssl.enabled: trueBy implementing these security measures, you can significantly mitigate risks associated with exposing port 9300, ensuring the integrity and confidentiality of your Elasticsearch cluster.
No, modern cloud providers (AWS, Google Cloud, Yandex) close all incoming ports by default. You must explicitly allow port 9300 in a Security Group or firewall.
Use Enterno Ping + Port Checker. Or in shell: nc -vz example.com 9300 or telnet example.com 9300.
Depends on the service. Elasticsearch inter-node should never be exposed publicly without authentication + TLS. See our 2026 exposure research.
Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.