# Failed to get node info for {#transport#-1}{52.43.xx.xxx}{52.43.xx.xxx:9243}, disconnecting **URL:** \ **Category:** Elasticsearch\ **Created:** [June 22, 2018, 5:09am UTC](https://discuss.elastic.co/t/failed-to-get-node-info-for-transport-1-52-43-xx-xxx-52-43-xx-xxx-9243-disconnecting/136969 "2018-06-22T05:09:31Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![e0813e449f09f8d5fbe7](https://avatars.discourse-cdn.com/v4/letter/e/a88e57/32.png) [@e0813e449f09f8d5fbe7](https://discuss.elastic.co/u/e0813e449f09f8d5fbe7)\ **Post date:** [June 22, 2018, 5:09am UTC](https://discuss.elastic.co/t/failed-to-get-node-info-for-transport-1-52-43-xx-xxx-52-43-xx-xxx-9243-disconnecting/136969/1 "2018-06-22T05:09:31Z")
Trying to connect to cloud elastic search, getting below error. [][generic][T#2]] org.elasticsearch.client.transport : [Jimaine Szardos] failed to get node info for {#transport#-1}{52.43.xx.xxx}{52.43.xx.xxx:9243}, disconnecting... org.elasticsearch.transport.NodeDisconnectedException: [][52.43.xx.xxx:9243][cluster:monitor/nodes/liveness] disconnected This is how I'm connecting @bean public Client client() throws Exception { ``` Settings esSettings = Settings.settingsBuilder() .put("http.enabled", true) .build(); return TransportClient.builder().settings(esSettings).build() .addTransportAddress(new InetSocketTransportAddress(InetAddress.getByName(EsHost), EsPort)); ``` } Any Help? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 22, 2018, 5:52am UTC](https://discuss.elastic.co/t/failed-to-get-node-info-for-transport-1-52-43-xx-xxx-52-43-xx-xxx-9243-disconnecting/136969/2 "2018-06-22T05:52:09Z")
Have you looked at the [Cloud documentation around the transport client](https://www.elastic.co/guide/en/cloud/saas-release-v2/ec-security.html#ec-security-transport) and the [version specific examples](https://github.com/elastic/found-shield-example)? Note that the transport protocol uses port 9343, not 9243. There are also some additional settings required, which are outlined in the docs I linked to. ---
**Author:** ![e0813e449f09f8d5fbe7](https://avatars.discourse-cdn.com/v4/letter/e/a88e57/32.png) [@e0813e449f09f8d5fbe7](https://discuss.elastic.co/u/e0813e449f09f8d5fbe7)\ **Post date:** [June 28, 2018, 9:34am UTC](https://discuss.elastic.co/t/failed-to-get-node-info-for-transport-1-52-43-xx-xxx-52-43-xx-xxx-9243-disconnecting/136969/3 "2018-06-28T09:34:21Z")
``` @Christian_Dahlqvist Thank you for the reply. I have tried to integrate the same way specified in the documentation, even though I'm the error "ShieldPlugin cannot be resolved to a type" .addPlugin(ShieldPlugin.class). I tried to include the dependency in the pom.xml. org.elasticsearch.plugin shield 2.1.0 Showing error missing artifact org.elasticsearch.plugin:shield:jar:2.1.0. Do I missing any thing? Please suggest. ``` ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 28, 2018, 9:45am UTC](https://discuss.elastic.co/t/failed-to-get-node-info-for-transport-1-52-43-xx-xxx-52-43-xx-xxx-9243-disconnecting/136969/4 "2018-06-28T09:45:30Z")
It looks like you are looking ate the wrong version. The Shield plugin is for use with Elasticsearch 2.x. Look at [the documentation](https://www.elastic.co/guide/en/x-pack/6.2/java-clients.html#transport-client) as well as the [example](https://github.com/elastic/found-shield-example/blob/master/src/main/java/org/elasticsearch/cloud/transport/example/TransportExample.java) for the correct version. ---
**Author:** ![e0813e449f09f8d5fbe7](https://avatars.discourse-cdn.com/v4/letter/e/a88e57/32.png) [@e0813e449f09f8d5fbe7](https://discuss.elastic.co/u/e0813e449f09f8d5fbe7)\ **Post date:** [June 28, 2018, 11:21am UTC](https://discuss.elastic.co/t/failed-to-get-node-info-for-transport-1-52-43-xx-xxx-52-43-xx-xxx-9243-disconnecting/136969/5 "2018-06-28T11:21:04Z")
@Christian_Dahlqvist I'm trying to connect to elastic search version 2.4.4. I have cloned the 2.x branch from git and followed the same instructions to run it from my local by provind remote server details, getting below error. mvn compile exec:java -Dhost=[xxxxxxx.us-west-2.aws.found.io](http://xxxxxxx.us-west-2.aws.found.io) -Dshield.user="xxxxxx:xxxxxx" Failed to execute goal on project found-shield-example: Could not resolve dependencies for project no.found.elasticsearch:found-shield-example:jar:2.1.0-SNAPSHOT: Failed to collect dependencies at org.elasticsearch.plugin:shield:jar:2.1.0: Failed to read artifact descriptor for org.elasticsearch.plugin:shield:jar:2.1.0: Could not transfer artifact org.elasticsearch.plugin:shield:pom:2.1.0 from/to elasticsearch-releases ([http://maven.elasticsearch.org/releases](http://maven.elasticsearch.org/releases)): [maven.elasticsearch.org](http://maven.elasticsearch.org): Unknown host [maven.elasticsearch.org](http://maven.elasticsearch.org) -\> ---
**Author:** ![e0813e449f09f8d5fbe7](https://avatars.discourse-cdn.com/v4/letter/e/a88e57/32.png) [@e0813e449f09f8d5fbe7](https://discuss.elastic.co/u/e0813e449f09f8d5fbe7)\ **Post date:** [June 29, 2018, 7:37pm UTC](https://discuss.elastic.co/t/failed-to-get-node-info-for-transport-1-52-43-xx-xxx-52-43-xx-xxx-9243-disconnecting/136969/6 "2018-06-29T19:37:17Z")
@Christian_Dahlqvist Thanks for your help. Finally i got the solution, it seems like version compatible issue with elastic search ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 27, 2018, 7:37pm UTC](https://discuss.elastic.co/t/failed-to-get-node-info-for-transport-1-52-43-xx-xxx-52-43-xx-xxx-9243-disconnecting/136969/7 "2018-07-27T19:37:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.